Log Service problem after upgraded to P10

Log Service problem after upgraded to P10

  

Hi All,

We have problem on our on premise environment after upgrade to P10, our environment connect to internet with proxy. All of ports and service is not problem can validate via telnet and service status, but from /opt/outsystems/platform/logs/LogServer.log, below explain some errors.

2017-01-24 11:12:51,777 ERROR [outsystems.hubedition.util.ServerLog] (Bulk Screen Logger)
Error on using Message Queue queue/OutSystemsScreenLog (RemoveLog):
Exception: javax.jms.IllegalStateException: HQ119019: Session is closed
   at org.hornetq.core.client.impl.ClientSessionImpl.checkClosed(ClientSessionImpl.java:2088)
   at org.hornetq.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:544)
   at org.hornetq.core.client.impl.DelegatingSession.commit(DelegatingSession.java:156)
   at org.hornetq.jms.client.HornetQSession.commit(HornetQSession.java:229)
   at outsystems.extensibility.MessageQueueClient.removeLogs(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.peekLog(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.peekLog(Unknown Source)
   at outsystems.hubedition.logservice.iIiiIiiIiIiI.$dkd(Unknown Source)
   at outsystems.hubedition.logservice.iiIiIiiiiiiI.$nod(Unknown Source)
   at outsystems.hubedition.logservice.iiIiIiiiiiiI$$Lambda$20/819419009.executeImplLambda(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.execute(Unknown Source)
   at outsystems.hubedition.servercommon.SandboxUtils.executeForAllSandboxes(Unknown Source)
   at outsystems.hubedition.logservice.iiIiIiiiiiiI.$ajd(Unknown Source)
   at outsystems.hubedition.logservice.IIIiIiiiIiii.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.executeImplLambda(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.execute(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.run(Unknown Source)
   at java.lang.Thread.run(Thread.java:745)
2017-01-24 11:12:51,777 ERROR [outsystems.hubedition.util.ServerLog] (Bulk Web Reference Logger)
Error on using Message Queue queue/OutSystemsWebReferenceLog (RemoveLog):
Exception: javax.jms.IllegalStateException: HQ119019: Session is closed
   at org.hornetq.core.client.impl.ClientSessionImpl.checkClosed(ClientSessionImpl.java:2088)
   at org.hornetq.core.client.impl.ClientSessionImpl.commit(ClientSessionImpl.java:544)
   at org.hornetq.core.client.impl.DelegatingSession.commit(DelegatingSession.java:156)
   at org.hornetq.jms.client.HornetQSession.commit(HornetQSession.java:229)
   at outsystems.extensibility.MessageQueueClient.removeLogs(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.peekLog(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.peekLog(Unknown Source)
   at outsystems.hubedition.logservice.iIiiIiiIiIiI.$dkd(Unknown Source)
   at outsystems.hubedition.logservice.iiIiIiiiiiiI.$nod(Unknown Source)
   at outsystems.hubedition.logservice.iiIiIiiiiiiI$$Lambda$20/819419009.executeImplLambda(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.execute(Unknown Source)
   at outsystems.hubedition.servercommon.SandboxUtils.executeForAllSandboxes(Unknown Source)
   at outsystems.hubedition.logservice.iiIiIiiiiiiI.$ajd(Unknown Source)
   at outsystems.hubedition.logservice.IIIiIiiiIiii.executeImpl(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0.executeImplLambda(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.execute(Unknown Source)
   at outsystems.hubedition.util.delegates.Action$Action0_Lambda.run(Unknown Source)
   at java.lang.Thread.run(Thread.java:745)

Any idea for it ?

Thank You

Hi Sanledi Buli, 

the Logserver only communicates with the mq server that is on the same host, so all communications are bound to localhost.

There's a separate service with hornetq running, called jboss-outsystems-mq (or wildfly-outsystems-mq, depending on application server flavour).

Those logs can appear between restarts of that service, since the connection will be lost. 

Regards,

Solution

Hi All,

The problem currently done. its happen because our jboss installation path is custom and when we upgraded it into P10, we was missed updated for mq config.

Solution