Injection an java agent into Zimbra - JVM Option -agentpath

Hello,

I'm trying to inject an Java Agent (dynatrace.com) into the mailboxd service of zimbra 6.0 for monitoring and performance analysis.
To do so I've modified the mailboxd_java_options via zmlocalconfig and added the correct option -agentpath:<options>.
However as soon as this option is there the mailboxd refuses to start.

Now I've searched if i find some detailed logging of the JVM startup, but I can't find it. I came to a point where 'zmjava' is called by 'zmmailboxdctl start' and that's where it ends.

To go on here I'd need to get the info the injected agent spits out during JVM startup. Can anyone provide hints how I could get this info? I think it should be somewhere in jetty startup logs/output.

Cheers,
Reinhard

Quote:

---

Originally Posted by RedChili

Hello,

I'm trying to inject an Java Agent (dynatrace.com) into the mailboxd service of zimbra 6.0 for monitoring and performance analysis.
To do so I've modified the mailboxd_java_options via zmlocalconfig and added the correct option -agentpath:<options>.
However as soon as this option is there the mailboxd refuses to start.

Now I've searched if i find some detailed logging of the JVM startup, but I can't find it. I came to a point where 'zmjava' is called by 'zmmailboxdctl start' and that's where it ends.

To go on here I'd need to get the info the injected agent spits out during JVM startup. Can anyone provide hints how I could get this info? I think it should be somewhere in jetty startup logs/output.

Cheers,
Reinhard

---

Has a solution been found to this? I'm having the same issue.

Thanks,
Steve

No I gave up after some time. I tuned a couple of other settings in zimbra and finally ended up having a satisfying performance.
It would still be cool to have that information though....

BUMP, this thread. I too have the need to insert a java agent for the JVM for monitoring purposes.

I have tried a similar approach to the OP with no success. The JVM execution is wrapped in a binary executable that doesn't seem to like -javaagent parameter.

Once I can download the source (no luck so far) I might hack the executable myself. But this is a short-term solution to unblock my demo. I need something that I can use with customer deployments.

Is this a bug? Is this a feature request?

This feature is disallowed by default. So, it is a design decision.

Hello,

I have the same need, ans the same problem with "javaagent" option.
So, if it is a design decision, what is the workaround ? How is it possible to monitore mailbox java code, in order to analyse performance problems ?

Thanks
Marine