Win a copy of Head First Android this week in the Android 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:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Health of managed server is NOT REACHABLE

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Team,

I am setting up weblogic 12.2.1.3, for which the architecture i am following is

I have two host2. HOST1 and HOST2. In both host we have common shared mount point, which is /u01. So when i am loggin in both hosts i am able to access shared storage /u01.
In both hosts, HOST1 and HOST2 there is a local mount point in each which is /u02.

I have installed weblogic in shared mount point /u01. After installing weblogic, i created the domain in /u01 shared mount point. I am following per nodemanager per host concept. For which i have created nodemanager.properties file in both hosts /u02 mount point as /u02 is local to both machines. I did nmenroll also to the domain. I did pack and unpack of domain from /u01 shared storage to both hosts /u02 mount point. I started admin server, and able to start WLS_WSM1 from admin console. I am able to start WLS_WSM2 from admin console also, but state of WLS_WSM2 is showing not reachable which i have attached in this forum.

While checking the logs of WLS_WSM2 i found below error. I am unable to rectify that error. Please help me to get this resolved.

<Sep 24, 2018 9:57:14,802 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN.>
<Sep 24, 2018 9:57:14,931 AM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING.>
<Sep 24, 2018 9:57:14,954 AM GST> <Error> <RJVM> <BEA-000580> <Failed to send JVMMessage from: '2758129357046954595S:dbpdcpciapvn574:soadomain:WLS_WSM2' to: '-3438674907617629430S:172.31.205.141:[7001,-1,-1,-1,-1,-1,-1]:soadomain:AdminServer' cmd: 'CMD_IDENTIFY_REQUEST', QOS: '101', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x0', abbrev offset: '171'.
java.io.IOException: Attempt to send message on closed socket
java.io.IOException: Attempt to send message on closed socket
       at weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection.sendMsg(MuxableSocketT3.java:817)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendOutMsg(MsgAbbrevJVMConnection.java:389)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:223)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:173)
       at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1742)
       Truncated. see log file for complete stacktrace


Thanks
wsm-not-reachable.PNG
[Thumbnail for wsm-not-reachable.PNG]
WSM_2 is state not reachable
 
Ranch Hand
Posts: 368
2
Eclipse IDE Firefox Browser Java
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I see both managed servers are in different machines.
They can see each other ? (through the declared ports).

 
chicquie Kumar
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Morris,

Yes i am able to ping both machine from one another. I am able to start the server from admin console also. WLS_WSM1 in machine 1 has port 7010 and WLS_WSM2 in machine 2 has port 7010. As both are in different machine that is why i kept port 7010 in both machine. I extended domain for soa suite in this domain. I am seeing same for WLS_SOA2. It is running as i can see pid from backend but health in console is showing not reacble. What could be the reason behind this.

Thanks
 
chicquie Kumar
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Morris,

When i checked the log of WLS_SOA2 i found one error

####<Sep 24, 2018 8:21:31,170 PM GST> <Error> <RJVM> <10.11.11.11> <WLS_SOA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <f7a02eef-299e-480d-94fa-b2065a7926ab-0000012e> <1537806091170> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000580> <Failed to send JVMMessage from: '1094830830832753378S:dbpdcpciapvn574:soadomain:WLS_SOA2' to: '2909173254129217458S:172.31.205.141:[7001,-1,-1,-1,-1,-1,-1]:soadomain:AdminServer' cmd: 'CMD_IDENTIFY_REQUEST', QOS: '101', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x0', abbrev offset: '171'.
java.io.IOException: Attempt to send message on closed socket
java.io.IOException: Attempt to send message on closed socket
       at weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection.sendMsg(MuxableSocketT3.java:817)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendOutMsg(MsgAbbrevJVMConnection.java:389)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:223)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:173)
       at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1742)
       at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1418)
       at weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:614)
       at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:1168)
       at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:448)
       at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:458)
       at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:128)
       at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:299)
       at weblogic.server.RemoteLifeCycleOperationsImpl_12213_WLStub.getState(Unknown Source)
       at weblogic.server.channels.RemoteChannelServiceImpl.getServerState(RemoteChannelServiceImpl.java:633)
       at weblogic.server.channels.RemoteChannelServiceImpl.access$500(RemoteChannelServiceImpl.java:70)
       at weblogic.server.channels.RemoteChannelServiceImpl$2.run(RemoteChannelServiceImpl.java:275)
       at weblogic.server.channels.RemoteChannelServiceImpl$2.run(RemoteChannelServiceImpl.java:273)
       at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
       at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
       at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:273)
       at weblogic.server.channels.RemoteChannelServiceImpl.access$200(RemoteChannelServiceImpl.java:70)
       at weblogic.server.channels.RemoteChannelServiceImpl$TimerListenerImpl.timerExpired(RemoteChannelServiceImpl.java:176)
       at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:301)
       at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)
       at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
       at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
       at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
       at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
       at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
       at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
>
####<Sep 24, 2018 8:21:41,192 PM GST> <Error> <RJVM> <10.11.11.11> <WLS_SOA2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <f7a02eef-299e-480d-94fa-b2065a7926ab-00000132> <1537806101192> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000580> <Failed to send JVMMessage from: '1094830830832753378S:dbpdcpciapvn574:soadomain:WLS_SOA2' to: '2909173254129217458S:172.31.205.141:[7001,-1,-1,-1,-1,-1,-1]:soadomain:AdminServer' cmd: 'CMD_IDENTIFY_REQUEST', QOS: '101', responseId: '-1', invokableId: '-1', flags: 'JVMIDs Sent, TX Context Not Sent, 0x0', abbrev offset: '171'.
java.io.IOException: Attempt to send message on closed socket
java.io.IOException: Attempt to send message on closed socket
       at weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection.sendMsg(MuxableSocketT3.java:817)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendOutMsg(MsgAbbrevJVMConnection.java:389)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:223)
       at weblogic.rjvm.MsgAbbrevJVMConnection.sendMsg(MsgAbbrevJVMConnection.java:173)
       at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1742)
       at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1418)
       at weblogic.rjvm.ConnectionManager.sendMsg(ConnectionManager.java:614)
       at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:1168)
       at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:448)
       at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:458)
       at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:128)
       at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:299)
       at weblogic.server.RemoteLifeCycleOperationsImpl_12213_WLStub.getState(Unknown Source)
       at weblogic.server.channels.RemoteChannelServiceImpl.getServerState(RemoteChannelServiceImpl.java:633)
       at weblogic.server.channels.RemoteChannelServiceImpl.access$500(RemoteChannelServiceImpl.java:70)
       at weblogic.server.channels.RemoteChannelServiceImpl$2.run(RemoteChannelServiceImpl.java:275)
       at weblogic.server.channels.RemoteChannelServiceImpl$2.run(RemoteChannelServiceImpl.java:273)
       at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
       at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
       at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:273)
       at weblogic.server.channels.RemoteChannelServiceImpl.access$200(RemoteChannelServiceImpl.java:70)
       at weblogic.server.channels.RemoteChannelServiceImpl$TimerListenerImpl.timerExpired(RemoteChannelServiceImpl.java:176)
       at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:301)
       at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)
       at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
       at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
       at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
       at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
       at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
       at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
(ExecuteThread.java:355)
>


Thanks
 
German Gonzalez-Morris
Ranch Hand
Posts: 368
2
Eclipse IDE Firefox Browser Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

chicquie Kumar wrote:Hi Morris,

Yes i am able to ping both machine from one another. I am able to start the server from admin console also. WLS_WSM1 in machine 1 has port 7010 and WLS_WSM2 in machine 2 has port 7010. As both are in different machine that is why i kept port 7010 in both machine. I extended domain for soa suite in this domain. I am seeing same for WLS_SOA2. It is running as i can see pid from backend but health in console is showing not reacble. What could be the reason behind this.

Thanks



but can you reach port 7010 ?
(ping doesn't check ports, please try with telnet).

I ask that for the verbatim message:



 
chicquie Kumar
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Morris,

This issue is resolved. I had mentioned the listen address in WLS_SOA2 and WLS_WSM2 as hostname and in nodemanager i had given listen address as ip of hostname. So it was giving error.

I am still confused, though my issue is resolved but my confusion is still there. In WLS_SOA1 and WLS_WSM1 in server i have given hostname, and Nodemanager i have given ip of hostname but there it started up without any issue.

Please suggest.. But now i am able to see status of WLS_SOA2 and WLS_WSM2 as running.

Thanks
 
chicquie Kumar
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Morris, i had checked with telnet for port 7010 and it was working for me. Now server is up and running just i changed the listen address from hostname (dspdrfghvsn) to IP of hostname (10.11.11.11), because in nodemanager machine2 listnen address i have given as hostname ip.

Thanks
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic