Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problems configuring DT Agent on Mule ESB - Mulesoft

Dynatrace Pro
Dynatrace Pro

I've already looked into a few postings about Mule ESB instrumentation (How to configure dynatrace agent in Mule ESB) , but I'm still having issues getting my agent running and connecting. I've installed the 64 bit Java Agent (and confirmed Java is 64 on this windows server), and in the wrapper.conf, utilized this as the argument:"D:\NetApps\dynaTrace\dynaTraceAgent6.0.0\agent\lib64\dtagent.dll =name=MULEESBAPPINTG, server="

We've checked that we can telnet from the agent to the collector on 9998 and still no connection to Dynatrace after restarting the Mule service. (I've double checked my agent mapping.

There is nothing in the agent logs, but I do get this in the collector logs:

2014-11-25 16:08:32 WARNING [AgentListener] Connection of Agent '(no agent)' refused: Ignoring connection that did not start with a dynaTrace agent handshake request (from /
2014-11-25 16:19:49 SEVERE [AgentListener] Error setting up an agent connection from '(unknown)' at '': : com.dynatrace.diagnostics.collector.agentcenter.AgentListener$ConnectionHandler run:508
at com.dynatrace.diagnostics.collector.agentcenter.AgentListener$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

These timings to not match up with our agent restarts and might be due to something other than our agent. (Agent - Collector Handshake. "Collector declined service"

Has anyone else run into these problems with Mule ESB? I believe I'm having problems with getting my java agent up and running. What's a good way to diagnose this and ensure it is running?



I suspect that the syntax is wrong. There are two space characters in the value of "" (after dtagent.dll and before server=).



Dynatrace Pro
Dynatrace Pro

We were able to resolve this issue. We still used the same configuration above (without spaces).  The only difference was that we started the instance using the mule script instead of the windows service. This allowed the agent to start up and connect.