Thanks for the link PeterJ.
We're running Red Hat Enterprise Linux ES release 4 (Nahant Update 4) for our OS.
As a test, I tried to lookup a different service, such as JNDIView. When I call lookup() it hangs indefinitely, so the program never returns from the lookup() method at all. I tried the telnet localhost 1099 numerous times, and have even used the IP returned from the telnet command (as discussed in the link PeterJ sent) and still no luck. When I go into the JMX Console, it does say that DataManagerService is running and I can invoke methods from the JMX Console (as well as the JNDIView MBean).
I'm very new to JBoss and MBeans, unfortunately, and our server administrator is also new to it. Any ideas?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988998#3988998
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988998
First of all make sure that you can get the "injboss" tutorial example running, so that you know how to set up loadtime weaving for an instance you manage yourself.
The jar to use for the -javaagent when running with jboss is pluggable-instrumentor.jar
not jboss-aop-jdk50.jar
:
| set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -javaagent:C:\myjboss\bin\pluggable-instrumentor.jar
|
I am not sure what JBoss IDE or jbosservice use run.bat or if they invoke the jboss Main class themselves. So if modifying the run.bat does not work for you, try to set the -javaagent switch when creating your service:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988994#3988994
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988994