Siebel Exception: Unable to open a connection to Siebel(SBL-JCA-00125) Solution

本文记录了在将ResourceAdapter部署到WebLogic Server (WLS) 时遇到的一个异常情况,该异常导致WLS无法正常打开Siebel连接。文中详细展示了异常堆栈跟踪,并给出了可能的解决方案,包括检查Siebel Server Manager中的连接配置。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

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.<init>(SiebelConnection.java:130) <br> at com.siebel.integration.jca.cci.notx.SiebelNoTxConnection.<init>(SiebelNoTxConnection.java:29) <br> at com.siebel.integration.jca.spi.notx.SiebelNoTxManagedConnectionFactory.createManagedConnection(SiebelNoTxManagedConnectionFactory.java:153) <br> at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802) <br> at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91) <br> at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180) <br> at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1104) <br> at weblogic.common.resourcepool.ResourcePoolImpl.setInitialCapacity(ResourcePoolImpl.java:866) <br> at weblogic.connector.deploy.RAOutboundDeployer.updateInitialCapacity(RAOutboundDeployer.java:147) <br> at weblogic.connector.outbound.RAOutboundManager.activatePool(RAOutboundManager.java:1014) <br> at weblogic.connector.outbound.RAOutboundManager.activate(RAOutboundManager.java:178) <br> at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:428) <br> at weblogic.connector.deploy.ConnectorModule.activate(ConnectorModule.java:301) <br> at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) <br> at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415) <br> at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) <br> at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75) <br> at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67) <br> at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) <br> at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) <br> at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) <br> at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:39) <br> at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) <br> at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) <br> at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) <br> at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) <br> at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) <br> at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) <br> at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) <br> at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) <br> at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) <br> at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) <br> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) <br> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) <br> at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) <br> at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) <br> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) <br> at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) <br>[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 <br>[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 <br>[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 <br>[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 <br>[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 <br>[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 <br>[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) <br>Caused by: <com.siebel.om.conmgr.conmgrexception><br><error><errorcode>8716488</errorcode><errmsg>Could not open a session in 4 attempts. {1}(SBL-JCA-00200)</errmsg></error><br></com.siebel.om.conmgr.conmgrexception></init></init>

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 yexianyi@hotmail.com

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值