on 07-17-2008 4:26 PM
Hi Experts,
We are facing a major performance problem in the production environment. We have more than 300 users in the production. when I was checking JCO connections status through sm04 transaction, we see most of the connections stay open more than one day. After reaching the maximum, we are forced to restart the server. Then only the JCO connections are closed. We have SSO enabled for all the model data JCO connections.
(The unclosed JCO's are webservice JCO's and metadata JCO's. Because in the visual admin I have used another user name to find the exact place of leakage prone JCO connections. There is no problem with model data JCO's. We are facing the problem with metadata JCO's and webservice JCo's)
I have also used webservice for my projects.I have used a BAPI in the webservice. For handling the webservice, we are using the JRE factory.
The parameters that I have used in the JCO and JRE's are following:
-
Visual admin parameters for JRE factory:
-
Connection Lifetime : 30 ( I assumed this 30 as seconds)
Cleanup Thread : 30 ( I assumed this 30 as seconds)
Maximum Connections : -1
Maximum Time to Wait for Connection: -1
Parameters that I have used in the portals for the meta data JCO's:
-
Maximal Pool Size : 1
Maximum Connections : 5
Connection Timeout : 60,000 ( msec)
Maximum Waiting Time : 10,000 ( msec)
Could you please help me to overcome this problem?
Kind Regards,
Hariprasath.R
Hi,
You can close the JCO session by adding this code :
M_MODEL model = (M_MODEL)WDModelFactory.getModelInstance(M_MODEL.class);
model.disconnectIfAlive();
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please have a look at this article and make sure that you follows
Regards
Ayyapparaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.