Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

In May release we implemented REST JMS Logging feature to check all errors & warnings being occurred during JMS configuration.

Current status

REST JMS Logging monitoring feature is under beta-testing. Be aware, it can be changed later.


To get JMS Log info you have to execute GET request by:

http://host:port/eagle/v2/jms/log

We support JSON format of log-info.


See how to get mc2 port: 

Calculating MC2 Endpoints Port Numbers


Example:

REST JMS Log
{
  "JMS" : {
    "CONFIG" : [ {
      "LEVEL" : "ERROR",
      "MSG" : "Exception occurred while creation of [wmq-my.jndi.wmq.connection] bean instance: com.ibm.mq.jms.MQConnectionFactory"
    }, {
      "LEVEL" : "ERROR",
      "MSG" : "Exception occurred while creation of [wmqssl-wmq.ssl.connection] bean instance: com.ibm.mq.jms.MQConnectionFactory"
    } ],
    "STREAMS" : [ {
      "LEVEL" : "WARN",
      "MSG" : "Could not find definition for connection 'myactivemq2.connection' of 'mc2_jms_out' stream. Check the connection configuration files in tpe/dynamic/mc2/eaglejms/connections"
    }, {
      "LEVEL" : "WARN",
      "MSG" : "Passwords for KeyStore & TrustStore were NOT provided! SSL Connection name: 'eglwwvm22.amq.ssl.connection'"
    } ]
  }
}
  • No labels