I am trying to monitor webMethods with CA APM to identify/troubleshoot the problems. It helps customers to solve the problem in few seconds. When I am receiving JMS message from webMethods as below
public class MFSMsgListener implements MessageListener {
@Override
public void onMessage(Message arg0) {
// TODO Auto-generated method stub
System.out.println("\\nReceived message:\\n" + arg0);
}
}
JMSType: null
JMSDestination: null
both of above are null from mebthods from com.webMethods.rtl.event.RemoteDeliverer.onMessage class. But as per the java (jms) specification they shouldn’t be null.
You are using JMS webMethods Libraries to receive JMS message to other application …
so , here ,hope you have imported all required wM JMS libraries files to respective target application(i.e CA APM).
And, to cross verify whether wM is successfully sending mess or not you can subscribe same message in wM and check. If it successful in wM then their might some problem in your program.
You are using JMS webMethods Libraries to receive JMS message to other application …
so , here ,hope you have imported all required wM JMS libraries files to respective target application(i.e CA APM).
Imported all required wM JMS libraries. Target application is a simple main program as below
public class MFSMsgListener implements MessageListener { @Override
public void onMessage(Message arg0) {
System.out.println(“\nReceived message:\n” + arg0);
}
}
Above message response JMSType: null
JMSDestination: null are null.
CA APM used to monitor the webMethods to identify the problems(it instruments java class files), it is not target application.
And, to cross verify whether wM is successfully sending mess or not you can subscribe same message in wM and check. If it successful in wM then their might some problem in your program.
Their is no program error, webMethods is not setting correct jms headers. Can you please run sample client program with MessageListener as explained above.