Stand alone JCo connection pool error

[Former Member]

I'm trying to connect to a 4.6c system using connection pooling. I can get a direct connection. But for this particular application, we want to use a connection pool. We've never used that method before so we don't have anyone familiar with the following error:

[code]08/10/2005 04:53:14 PM HTTP JVM: java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader)

08/10/2005 04:53:14 PM HTTP JVM: at java.security.AccessControlContext.checkPermission(AccessControlContext.java:286)

08/10/2005 04:53:14 PM HTTP JVM: at java.security.AccessController.checkPermission(AccessController.java:413)

08/10/2005 04:53:14 PM HTTP JVM: at java.lang.SecurityManager.checkPermission(SecurityManager.java:565)

08/10/2005 04:53:14 PM HTTP JVM: at java.lang.Thread.setContextClassLoader(Thread.java:1169)

08/10/2005 04:53:14 PM HTTP JVM: at com.sap.mw.jco.JCO$PoolManager.startTimeoutChecker(JCO.java:5143)

08/10/2005 04:53:14 PM HTTP JVM: at com.sap.mw.jco.JCO$PoolManager.<init>(JCO.java:5131)

08/10/2005 04:53:14 PM HTTP JVM: at com.sap.mw.jco.JCO$PoolManager.createPoolManager(JCO.java:5167)

08/10/2005 04:53:14 PM HTTP JVM: at com.sap.mw.jco.JCO$PoolManager.singleton(JCO.java:5160)

08/10/2005 04:53:14 PM HTTP JVM: at com.sap.mw.jco.JCO.getClientPoolManager(JCO.java:7287)

08/10/2005 04:53:14 PM HTTP JVM: at JavaAgent.NotesMain(JavaAgent.java:31)

08/10/2005 04:53:14 PM HTTP JVM: at lotus.domino.AgentBase.runNotes(Unknown Source)

08/10/2005 04:53:14 PM HTTP JVM: at lotus.domino.NotesThread.run(NotesThread.java:215)[/code]

The line where the error occurs is:

[code]JCO.Pool l_pool = JCO.getClientPoolManager().getPool(pool_name);[/code]

where pool_name is a static string with the value "ESS_POOL"

The web server is Notes/Domino but my instinct tells me that is irrelevant to this error. I'm guessing that the error is being caused by a system or auth setting on SAP that we don't know about.

Any help would be appreciated.

[richard_birenheide · Accepted solution]

Very likely the settings of your server in the jre policy file java.policy in lib/security. If the policy is switched on when starting the vm the permissions from that file are used. Read the jdk documentation for security. Most servers run with restricted security permissions including changing the class loader which is a potential security risk. Therefore you have to change the server settings accordingly.

[Former Member · Accepted solution]

Thanks Richard,

I've forwarded your suggestion to our Domino administrators. I'll post something when they respond.

- George