cancel
Showing results for 
Search instead for 
Did you mean: 

couldn't create jco client connection for logical system

Former Member
0 Kudos

Dear Experts,

we are facing a strange issue in our custom webdynpro java application, few of our portal users are getting the "couldn't create jco client connection for logical system" for Model Data JCO Destination. below are details

1. portal version 7.02 SP14 (we have recently updated to SP14 from SP02-- is this is causing the issue ?)

     1.1. updated the NWDI track with SP14 SCA files as well as added latest WD Runtime SCA file deployed the applications to Production also.

2. above said exception is inconsistent and happening for only few users

3. ping and test of jco destinations are successfull in content administration as well as in SLD, destinations were added in the SLD system.

4. cleared the JCO ARFC meta data cache in webdynpro console

5. jco destinations are configured using uid/pwd, configured user is not locked active and tested in the backend by logging in with the same user.

6. restarted the portal server

even though, we are getting the above said exception for few of portal users randomly.

Please help me on this ASAP, as i am not getting any further help on this.

Thanks,

Ram.

Accepted Solutions (0)

Answers (1)

Answers (1)

junwu
Active Contributor
0 Kudos

increase the number of your connection

Former Member
0 Kudos

Hi Jun,

we have already increased the number of connections.

Regards,

Ram.

junwu
Active Contributor
0 Kudos

what's the number now? how many user you have?

maybe reduce the idle time meanwhile.

Former Member
0 Kudos

Hello,

MaxPoolSize: 10

Max Connections: 200

Connection Timeout(msec): 10,000

Max Waiting time: 30,000

Regards,

Ram.

vijay_kumar49
Active Contributor
0 Kudos

Hello Ram,

Check the JCo Pool Configuration settings of your JCO Destination. This message normally comes when the maximum connections has been reached. Increase the "Maximum Connections" to some number depending on the usage. A good habit is to disconnect the jco connection after executing the same in your webdynpro code if you don't want it to be synchronous.

<ModelName>.modelInstance().disconnectIfAlive()

Hope this helps.

Regards

Vijay