JConsole with JBoss 4.2.3 on Java 6

You must set the following when starting JBoss or you will get .ClassNotFoundException when trying to connect JConsole to the JBoss process see forum entry.

Edit the JBoss startup script

Add to run JConsole without JBoss MBeans

JAVA_OPTS="-Dcom.sun.management.jmxremote $JAVA_OPTS"

Add to run JConsole with only JBoss MBeans

JAVA_OPTS="-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
-Djboss.platform.mbeanserver
-Dcom.sun.management.jmxremote $JAVA_OPTS"

JBossMBeansInJConsole


# Enable the jconsole agent locally
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"
# Tell JBossAS to use the platform MBean server
JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
# Make the platform MBean server able to work with JBossAS MBeans
JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"


Can get JBoss MBeans through Jboss web consoles.

http://localhost:8080/jmx-console/
OR
http://localhost:8080/web-console/ under System : JMX MBeans

Also be sure the hostname in /etc/hosts is mapped to an interface ip address, see previous entry.

Comments

Rajesh Roy said…
Thanks a lot. Your instruction has resolved my claa not found exception problem.
September 14, 2011 at 5:49 PM
roja said…
The 'show MBeans' option resulted with a CNF. But this worked, from a comment on the page you referenced...thanks ! (I am running JBoss 4.2.2 and took a chance)

Krzysiek Kalisiak Dec 23, 2008 6:43 AM

I run 5.0 with -Djboss.platform.mbeanserver only and now it works fine
April 7, 2015 at 12:54 PM
Post a Comment

Popular posts from this blog

Sites, Newsletters, and Blogs

BLOGS Java.net Weblogs Martin Fowler's blog Paul Graham Ruminations of a Programmer Form Follows Function Newsletters Core Java Tech Tips Enterprise Java Tech Tips JavaSpecialists.EU TheServerSide.com Sites Java.net Today Hot Java Sites CSS Zen Garden Evernote Hacker News Pragmatic Programmer
Read more

Oracle JDBC ReadTimeout QueryTimeout

If a query exceeds the oracle.jdbc.ReadTimeout without receiving any data, an exception is thrown and the connection is terminated by the Oracle driver on the client. Unfortunately the session will still be queued on the database and continue to wait for locks, hold any current locks, and complete any DML/PL*SQL procedures that are pending on the server-side of the orphaned connection. If an application, on a another connection, due to ReadTimeout exception, retries DML/PL*SQL  which requires locks, those queries will queue behind the initial DML/PL*SQL. This will increase the workload exacerbating the situation. On applications with retries, this can be observed by querying the v$session table  or gv$session on RAC and noting new sessions started periodically based on the ReadTimeout interval. The sessions may often have the same SQL_ID and/or SQL_HASH_VALUE. If stmt.setQueryTimeout(Seconds) is issued and the statement exceeds the timeout, it will attempt to cancel the associated
Read more