#Serveur WLS_FORM Cesse de répondre #1
AdminServer.log00007:####<Feb 7, 2018, 3:03:19,768 PM EST> <Info> <Server> <ohm.inrs.ca> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <545c673b-e869-4a97-b480-361a7a6c243e-00001836> <1518033799768> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > < BEA-002634> <The server "WLS_FORMS" disconnected from this server.>
AdminServer.log00007:####<Feb 7, 2018, 3:03:19,768 PM EST> <Info> <Server> <ohm.inrs.ca> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <545c673b-e869-4a97-b480-361a7a6c243e-00001836> <1518033799768> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > < BEA-002634> <The server "WLS_FORMS" disconnected from this server.>
AdminServer.log00007:####<Feb 7, 2018, 3:15:55,660 PM EST> <Info> <Server> <ohm.inrs.ca> <AdminServer> <[STANDBY] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <545c673b-e869-4a97-b480-361a7a6c243e-0000183c> <1518034555660> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > < BEA-002634> <The server "WLS_REPORTS" disconnected from this server.>
AdminServer.log00007:####<Feb 7, 2018, 3:16:00,899 PM EST> <Info> <Server> <ohm.inrs.ca> <AdminServer> <[STANDBY] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <545c673b-e869-4a97-b480-361a7a6c243e-0000183c> <1518034560899> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > < BEA-002634> <The server "WLS_REPORTS" disconnected from this server.>
##################### Solution
Issue:
frequent error entries under weblogic server logs pointing to JVM-JVM communication break
<<WLS Kernel>> <> <> <1427126477418> <BEA-002634> <The server “AdminServer” disconnected from this server.>
when you see these messages – there can be a scenario where it causes JVM-JVM communication break i.e between AdminServer <–> Managed Server Instance status communication (health check)
Managed Server instance gets into UnKnown State and Monitoring agent(third party app) can alert us saying managed server instance is down
steps to verify:
verify AdminServer Listen address is not blank and specified to listen on Hostname
verify Managed Server Listen address has been pointing to particular hostname
resolution:
Update Listen Address for AdminServer to point to specific Hostname
Environment — Servers — <Server_name> (eg:AdminServer) — Configuration (General tab)
update Listen address to point to Hostname.
requires a restart of AdminServer, suggested to restart managed server instances aswell.
monitor logs for error entry.