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 4 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 from particular mc2-worker instance you have to execute GET request by:

http://host:port/eagle/v2/jms/log (execute on particular mc2-worker instance)

or you can get all logs from all active mc2-workers in cluster by:

http://host:port/eagle/v2/jms/logs (execute on any mc2-lb instance)

We support JSON format of log-info.


See how to get mc2 port: 

Calculate MC2 Endpoints Port Numbers


Example JMS Logs from worker:

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'"
    } ]
  }
}

Example JMS Logs from All mc2-workers:

Aggregated REST JMS Logs
[
	{
		"HOST": "inno-jenever01.eagleinvsys.com",
		"PID": "17262",
		"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'"
					}
				],
				"SINGLE_CONSUMER": [
					{
						"LEVEL": "INFO",
						"MSG": "Started Sequential-Reading JMS-Consumer Stream [!vp_test_jms_consumer_2] on this mc2-worker instance at [2019-Jun-06 01:50:59]"
					}
				]
			}
		}
	},
	{
		"HOST": "inno-jenever01.eagleinvsys.com",
		"PID": "17292",
		"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