This week's book giveaway is in the JDBC and Relational Databases forum.
We're giving away four copies of Murach's MySQL and have Joel Murach on-line!
See this thread for details.
Win a copy of Murach's MySQL this week in the JDBC and Relational Databases forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Can't start the web server,java processes die after few minute,any thoughs.

 
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Error in the PIA_stderr.log file
***************************************************************************

The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.DeploymentException: [Deployer:149204]The deployment framework was unable to register with the Data Replication Service.
RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out; No available router to destination
at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
'
Reason: [Deployer:149601]The deployment framework was unable to resume accepting requests.[Deployer:149204]The deployment framework was unable to register with the Data Replication Service.
RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out; No available router to destination
at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)

***************************************************************************


Error messages in the PIA_stdout.log file

<Oct 14, 2008 3:07:42 PM EDT> <Notice> <WebLogicServer> <BEA-000356> <Starting WebLogic Independent Managed Server "PIA" for domain "STAGE">
<Oct 14, 2008 3:09:10 PM EDT> <Warning> <DRS> <BEA-002527> <The get deltas from version 0 to version timed out.>
<Oct 14, 2008 3:13:16 PM EDT> <Error> <Deployer> <BEA-149204> <The deployment framework was unable to register with the Data Replication Service.
RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out; No available router to destination
at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Oct 14, 2008 3:13:16 PM EDT> <Error> <Deployer> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
<Oct 14, 2008 3:13:16 PM EDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.[Deployer:149204]The deployment framework was unable to register with the Data Replication Service.
RegisterException due to underlying exception java.rmi.RemoteException: Failed to get message receiver on t3://localhost:7001; nested exception is:
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection timed out; No available router to destination
at weblogic.drs.internal.DataReplicationService.registerSlave(DataReplicationService.java:285)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:377)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)



***********************
The status of PIA server is running in the running-managed-servers.xml file
*********************
</listen-port>
<is-listen-port-secure>
false
</is-listen-port-secure>
<server-name>
PIA
</server-name>
<state>
running
</state>
</managed-server>
</running-managed-servers>
reply
    Bookmark Topic Watch Topic
  • New Topic