PeopleSoft EnterpriseOne WmART-Unable to configure connectio

We have installed PeopleSoft EnterpriseOne adapter on windows and we get the following error on a regular basis.

Did anyone see this error occuring with the PeopleSoft EnterpriseOne adapter.

Stack trace is as follows. When this happens the only way to resolve is a restart of the server.

Any Ideas or suggestions???

Error encountered
[ART.118.5042] Adapter Runtime (Connection): Unable to enable connection resource connection:ERP8EventConnection.
[ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager.
unable to create new native thread
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start(Native Method)
at com.jdedwards.system.connector.Connector.(Unknown Source)
at com.psft.xpi.adapter.erp.classloader.ERP8ConnectorAbstracter.createJavaConnectorInstance(ERP8ConnectorAbstracter.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.psft.xpi.adapter.erp.connection.ConnectionFactory.executeConnectionMethod(ConnectionFactory.java:139)
at com.psft.xpi.adapter.erp.connection.ERP8AbstractConnectionFactory.initializeConnector(ERP8AbstractConnectionFactory.java:172)
at com.psft.xpi.adapter.erp.connection.ERP8EventConnectionFactory.addConnection(ERP8EventConnectionFactory.java:171)
at com.psft.xpi.adapter.erp.connection.ERP8Connection.initializeConnection(ERP8Connection.java:73)
at com.wm.adk.connection.WmManagedConnectionFactory.createManagedConnection(WmManagedConnectionFactory.java:143)
at com.wm.app.b2b.server.jca.WmConnectionPool$ConnectionEntry.(WmConnectionPool.java:903)
at com.wm.app.b2b.server.jca.WmConnectionPool.init(WmConnectionPool.java:257)
at com.wm.app.b2b.server.jca.WmConnectionPool.(WmConnectionPool.java:172)
at com.wm.app.b2b.server.jca.WmConnectionManager.setConfiguration(WmConnectionManager.java:197)
at com.wm.pkg.art.j2eecaBridge.WmConnectionManagerPropertiesBridge.setManagerProperties(WmConnectionManagerPropertiesBridge.java:121)
at com.wm.pkg.art.ns.ConnectionDataNodeManager.createConnectionManager(ConnectionDataNodeManager.java:798)
at com.wm.pkg.art.ns.ConnectionDataNode.enable(ConnectionDataNode.java:593)
at com.wm.pkg.art.ns.ConnectionDataNodeManager.setConnectionState(ConnectionDataNodeManager.java:1043)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:344)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:119)
at com.wm.app.b2b.server.ns.Namespace.invoke(Namespace.java:522)
at com.wm.util.template.Reporter.invoke(Reporter.java:963)
at com.wm.util.template.InvokeToken.eval(InvokeToken.java:75)
at com.wm.util.template.TemplateToken.evalChild(TemplateToken.java:214)
at com.wm.util.template.SwitchToken.evalChild(SwitchToken.java:90)
at com.wm.util.template.TemplateToken.eval(TemplateToken.java:180)
at com.wm.util.template.SwitchToken.eval(SwitchToken.java:58)
at com.wm.util.template.TemplateToken.evalChild(TemplateToken.java:214)
at com.wm.util.template.IfVarToken.evalChild(IfVarToken.java:239)
at com.wm.util.template.TemplateToken.eval(TemplateToken.java:180)
at com.wm.util.template.IfVarToken.eval(IfVarToken.java:219)
at com.wm.util.template.TemplateToken.evalChild(TemplateToken.java:214)
at com.wm.util.template.TemplateToken.eval(TemplateToken.java:180)
at com.wm.util.template.Reporter.reportNoReset(Reporter.java:1299)
at com.wm.util.template.Reporter.reportToOutput(Reporter.java:1274)
at com.wm.util.template.Reporter.reportIData(Reporter.java:1163)
at com.wm.app.b2b.server.HTTPDocHandler._process(HTTPDocHandler.java:490)
at com.wm.app.b2b.server.HTTPDocHandler.process(HTTPDocHandler.java:112)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:216)
at com.wm.util.pool.PooledThread.run(PooledThread.java:105)
at java.lang.Thread.run(Thread.java:534)

Moset probably this message means some required parameter is missing or wrong in the configuration. Check all parameters are supplied correct. IF all supplied then server will try to give some valid message. I have seen this for JDBC adapter due to wrong driver classes.

Check # of server threads allowed on your IS server and increase it. Also increase your IS JVM memory values in server.sh or server.bat file.

On OneWorld server, check if OW server threads are also adequate enough.

Thanks
Eric

I dont have a screens in front of me, but check the following on the ERP8EventConnection configuration screen and tune it accordingly. This may help.

  1. Maximum number of connections (if its too high …lower it down)
  2. Pool increment size (keep 1 and not 5 or 10…etc)
  3. Minimum Connection ( 1 or 0)
  4. JDE Debug logging levels (Keep them as low as possible. Keeps I/O activities to minimum)
  5. I guess there are some timeout values too, Based on the time required to complete flow services, give the realistic timeout values Session, Request timeouts etc
  6. Check for Blockout time and Expire Timeouts.

One possibility of above happening is there may be too many requests to be handled and the previous requests are not completed (or threads not freed up). So check the flows too (and frequency).

Above were few things I could think of. Check for above in QA and test.

Thanks
Chetan