Support #5969

[SCP ID :##2973##] : ESB Development Issue.

Added by Zahir Abd Latif over 8 years ago. Updated over 8 years ago.

Status:Closed - End of life cycleStart date:February 15, 2016
Priority:HighDue date:
Assignee:Zahir Abd Latif% Done:

100%

Category:MY RIBSpent time:-
Target version:-

Description

Hi,
Kindly attend below request:

Dear Penril support;
Please check on ESB services in development environenment as we were having problem to restart the service.
After ./start2 command is issued the following error appeared.

<Feb 15, 2016 11:07:04 AM MYT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<MigratableServerService>: Starting migratable service
<MigratableServerService>: Initializing migratable service: false
<Feb 15, 2016 11:07:16 AM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Feb 15, 2016 11:07:16 AM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Feb 15, 2016 11:11:02 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "ImalDS": JZ006: Caught IOException: java
.net.ConnectException: Connection timed out>
<Feb 15, 2016 11:11:03 AM MYT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ImalDS' due to error weblogic.application.ModuleExcepti
on: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:268)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
Truncated. see log file for complete stacktrace
weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: JZ006: Caught IOExcept
ion: java.net.ConnectException: Connection timed out
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:237)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:982)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:206)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1177)
Truncated. see log file for complete stacktrace

<Feb 15, 2016 11:14:48 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "JDBC": JZ006: Caught IOException: java.n
et.ConnectException: Connection timed out>
<Feb 15, 2016 11:14:49 AM MYT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JDBC' due to error weblogic.application.ModuleException
: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:268)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
Truncated. see log file for complete stacktrace
weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: JZ006: Caught IOExcept
ion: java.net.ConnectException: Connection timed out
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:237)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:982)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:206)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1177)
Truncated. see log file for complete stacktrace

<Feb 15, 2016 11:18:34 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "PhoenixDS": JZ006: Caught IOException: j
ava.net.ConnectException: Connection timed out>
<Feb 15, 2016 11:22:19 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "PhoenixDS": JZ006: Caught IOException: j
ava.net.ConnectException: Connection timed out>
<Feb 15, 2016 11:26:05 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "PhoenixDS": JZ006: Caught IOException: j
ava.net.ConnectException: Connection timed out>
<Feb 15, 2016 11:29:51 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "PhoenixDS": JZ006: Caught IOException: j
ava.net.ConnectException: Connection timed out>
<Feb 15, 2016 11:33:37 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "PhoenixDS": JZ006: Caught IOException: j
ava.net.ConnectException: Connection timed out>
<Feb 15, 2016 11:37:22 AM MYT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "PhoenixDS": JZ006: Caught IOException: j
ava.net.ConnectException: Connection timed out>

Please help to rectify this issue ASAP since users need to do urgent testing. Thank you for your cooperation.

History

#1 Updated by Zahir Abd Latif over 8 years ago

  • Status changed from New - Begin Life Cycle to Closed - End of life cycle
  • Assignee changed from Hafizudin MD to Zahir Abd Latif
  • % Done changed from 0 to 100

Update from Norashikin, Feb 15, 2016 05:17 PM:-

Dear Hazri / Penril Support;
Please close this case as we find out that Sybase server in development was down, after sys admin has bring up the server and database was restart,
we managed to restart the ESB service.

Issue closed in SCP.

Also available in: Atom PDF