My servers are on the App Servers list, but show no transactions at all. Also, we are using Mule to send/receive the JMS messages, could this be the issue? Maybe since it is not standard JMS calls the flow is not being detected properly? Attaching log files from the Java Agents. The flow is basically.
SPS -> ActiveMQ (JMS) -> MDE
2 logs per as they are clustered servers in each Tier (i.e. SPS and ME are separate JVMs on servers esbstg03 and esbstg04, and ActiveMQ is clustered on msgstg01 and msgstg02 and is the only JVM running on each server).
Hi Marshall,
We understood your concern it would have been great if you have provided the BT/Api details that is expected to do exit calls and serve at upstream and downstream tier logs, to assist you in quick way we request you to raise help ticket at help.appdynamics.com Or email to help@appdynamics.com with agent logs in debug mode (refer screenshots below to collect logs in debug mode) so that team will get into Gotomeeting based on api/bt details and debug logs analysis.
If gotomeeting / screenshare web call is not an option, we request you to provide the details requested above.
We do not locate any backend rule on TcpBufferedInput
We understood that you want to see MQ as backend but please be sure that if backend is resolved to an existing tier and we might not see backends resolved in flow view and we can only see them in Actions -> Configure backends resolved to this tier option on Active MQ.
Regards,
Arun
Hi,
We could see in saas UI BTs discovered fine on tier "Invoice_SPS" tier and we could see JMS Active MQ backend calls from "Invoice_SPS" tier are resolved to "Activem MQ" tier as referred in screenshots below, If you are referring to missing correleation between "Invoice_SPS" -> Active MQ -> Micros_Data_Exchange tier, please confirm which BT from Invoice_SPS tier is expected to make calls as we see few BTs are falling in Other traffic for which flow will not add to app flow view.
Also we see calls are also made from MDE tier to Active MQ as referred in below screenshots, please provide requested BT details and the api(class/method) that is expected to invoked calls to MDE and served at MDE to assist you further:
Regards,
Arun
Problem was that it did not automatically detect my JMS queues. I had to setup the detection of org.apache.activemq.transport.tcp.TcpBufferedInputStream and still not detecting the output JMS messages to ActiveMQ. I expected to see a blue pipe on my flow showing the ActiveMQ queues detected as they were being used, never did see it.
Thanks,
Marshall
Hi Marshall,
We understood your concern it would have been great if you have provided the BT/Api details that is expected to do exit calls and serve at upstream and downstream tier logs, to assist you in quick way we request you to raise help ticket at help.appdynamics.com Or email to help@appdynamics.com with agent logs in debug mode (refer screenshots below to collect logs in debug mode) so that team will get into Gotomeeting based on api/bt details and debug logs analysis.
If gotomeeting / screenshare web call is not an option, we request you to provide the details requested above.
We do not locate any backend rule on TcpBufferedInput
We understood that you want to see MQ as backend but please be sure that if backend is resolved to an existing tier and we might not see backends resolved in flow view and we can only see them in Actions -> Configure backends resolved to this tier option on Active MQ.
Regards,
Arun