Logger Service - Unable to create QueueSession because connection not initialized

Logger Service - Unable to create QueueSession because connection not initialized

  
We are facing a strange issue wherein logger service doesnt seem to start. Service center provides below stack trace:
avax.jms.IllegalStateException: Unable to create QueueSession because connection not initialized
   at outsystems.extensibility.MessageQueueClient.initSession(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.internalRestart(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.internalFullInit(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.getReceiver(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.peekLog(Unknown Source)
   at outsystems.extensibility.MessageQueueClient.peekLog(Unknown Source)
   at outsystems.hubedition.logservice.iiIiIiiiiiiiii.$pyc(Unknown Source)


Checking the logs: LogServer.log has below error:
2016-05-24 19:33:56,783 ERROR [outsystems.hubedition.util.ServerLog] (Bulk General Logger) Error on Message Queue setup: queue/OutSystemsGeneralLog
Exception: javax.jms.JMSException: Failed to create session factory
2016-05-24 19:33:57,141 ERROR [outsystems.hubedition.util.ServerLog] (Legacy Logger) Error on Message Queue setup: queue/OutSystemsLog
Exception: javax.jms.JMSException: Failed to create session factory
2016-05-24 19:33:57,142 ERROR [outsystems.hubedition.util.ServerLog] (Bulk Integration Detail Logger) Error on Message Queue setup: queue/OutSystemsIntDetailLog
Exception: javax.jms.JMSException: Failed to create session factory

Looks like MQ services is not initialiazed, however there is not logs available in jboss-mq -server or console log indicating the error:

However I do see these error in the DeploymentController.log file
2016-05-24 11:00:55,279 ERROR [outsystems.hubedition.util.ServerLog - RMI TCP Connection(13)-192.168.18.31] Error on Message Queue setup: queue/OutSystemsGeneralLog

Any help in identifying the actual root cause?
 

Hi Chetan,

Could you check the status of jboss-mq service?
- # sudo /etc/init.d/jboss-outsystems-mq status

If it is running could you validate your server.log for errors?
# sudo vim /$JBOSS_HOME/standalone/log/server.log


Kind regards,
Ivo Gonçalves