• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Tim Cooke
  • Junilu Lacar
  • Rob Spoor
  • Devaka Cooray
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Tim Holloway
  • Jj Roberts
  • Al Hobbs
  • Piet Souris

Activating JMX for tomcat 5.5.9 on As/400 iseries

Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I'm trying to get JMX active for my Tomcat server but do not succeed. In Netstat i do not see the port I defined for JMX. Since iseries is a bit of an outsider there is not much in the way of dicumentation i can find for, especially regarding the syntax of the java options.

This is what i have tried:

CATALINA_OPTS="$CATALINA_OPTS "-Dcom.sun.management.jmxremote
CATALINA_OPTS="$CATALINA_OPTS "-Dcom.sun.management.jmxremote.port=48009
CATALINA_OPTS="$CATALINA_OPTS "-Dcom.sun.management.jmxremote.ssl=false
CATALINA_OPTS="$CATALINA_OPTS "-Dcom.sun.management.jmxremote.authenticate=false

And this:
CATALINA_OPTS="$CATALINA_OPTS "-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=48009 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false

Whatever I do, Tomcat starts, but not JMX

Does anyone know the correct syntax for these parameters in a iseries envrionment?

is the first Dcom.sun.management.jmxremote parameter necessary? Some sites omit it

Is there maybe a way to see why jmx does not start? I have tried everything both with jdk 1.4 as well as jdk 1.5

JavaMonitor Support
Posts: 251
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Tom,

That is precisely why I created Java-monitor. (http://java-monitor.com) It removes the need to deal with enabling JMX, getting it to work on a specific port range (you know JMX uses RMI, which uses dynamic port allocation, yes?) and the subsequent firewall nastiness.

Java-monitor builds on JMX, but connects to the mbean server directly and then uses web services to collect the samples. No firewall changes needed, no configuration.

Kees Jan
    Bookmark Topic Watch Topic
  • New Topic