Hi,
I've read the docs, have configured the properties correctly and am able to run an application in console mode and attach with JConsole as expected. Using the same config to run as a service, and JConsole cannot connect.
Is there a registry hack to make the JMX stuff work ? I looked through for 'com.sun.management.jmxremote' but didn't find it....
Help?!
Can you take a look at this Forum posting?
http://sourceforge.net/forum/message.php?msg_id=7109400
I think you can solve this by setting the TMP environment variable:
From the message:
---
I did some tests with this today using version 3.3.3 of the Wrapper.
When running in a console, the JVM is found by VisualVM no problem.
When running as a service by default it will not be. This is because the Service is running as the SYSTEM user and has a different environment.
The solution is to add the following to your wrapper.conf:
set.TMP=C:¥Temp
Then open a console and run:
set TMP=C:¥Temp
Followed by launching the visualvm.exe process from that console.
This way, they will share the TMP environment variable and make the JVM visible for profiling.
Let me know if you have problems getting up and running.
Cheers,
Leif
I know ths issue ist somehow old, however my question. I have proceeded exactly as described in the Forum posting mentioned. This works if your application is running under a local account. In my case, the application runs under a different user which has no rights to log in using RDP. Any ideas on how to solve this...?