Issue:
When you deploy your Resource Adapter to WLS, your WLS might be kept throwing following exception.
Exception:
New trace 2010-05-21 13:28:01.453
[SIEBEL INFO] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:01.546] [SiebelConnection(24179038)] Opening a new connection to Siebel ...
java.lang.Throwable
at com.siebel.integration.util.SiebelTrace$Representation.trace(SiebelTrace.java:39)
at com.siebel.integration.util.SiebelTrace.trace(SiebelTrace.java:160)
at com.siebel.integration.jca.cci.SiebelConnection.trace(SiebelConnection.java:746)
at com.siebel.integration.jca.cci.SiebelConnection.initialize(SiebelConnection.java:605)
at com.siebel.integration.jca.cci.SiebelConnection. (SiebelConnection.java:130)
at com.siebel.integration.jca.cci.notx.SiebelNoTxConnection. (SiebelNoTxConnection.java:29)
at com.siebel.integration.jca.spi.notx.SiebelNoTxManagedConnectionFactory.createManagedConnection(SiebelNoTxManagedConnectionFactory.java:153)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1104)
at weblogic.common.resourcepool.ResourcePoolImpl.setInitialCapacity(ResourcePoolImpl.java:866)
at weblogic.connector.deploy.RAOutboundDeployer.updateInitialCapacity(RAOutboundDeployer.java:147)
at weblogic.connector.outbound.RAOutboundManager.activatePool(RAOutboundManager.java:1014)
at weblogic.connector.outbound.RAOutboundManager.activate(RAOutboundManager.java:178)
at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:428)
at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:301)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[SIEBEL DETAIL] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:01.828] [] creating socket for listening thread: host=sdc78335svqe.corp.siebel.com port=3320
[SIEBEL DETAIL] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:02.062] [] about to read to bytes: len=168
[SIEBEL DETAIL] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:02.312] [] creating socket for listening thread: host=sdc78335svqe.corp.siebel.com port=3320
[SIEBEL DETAIL] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:02.562] [] about to read to bytes: len=168
[SIEBEL DETAIL] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:02.812] [] creating socket for listening thread: host=sdc78335svqe.corp.siebel.com port=3320
[SIEBEL DETAIL] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:03.062] [] about to read to bytes: len=168
[SIEBEL FATAL] Thread[[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] [2010-05-21 13:28:03.078] [SiebelConnection(24179038)] Error in initialize(): Unable to open a connection to Siebel(SBL-JCA-00125)
Caused by:
8716488 Could not open a session in 4 attempts. {1}(SBL-JCA-00200)
Solution:
Please go to Siebel Server Manager Command Line and type “List comp for EAIMgrObj_enu” to check if all the connections have been run out. If so, please kill some of them or extend Max connection number.
Any question, please contact to [email protected]