Ad Widget

Collapse

Tomcat will not start with the parameters jmxremote

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • denisss
    Member
    • May 2011
    • 36

    #1

    Tomcat will not start with the parameters jmxremote

    Hi,

    This is a moment I'm fighting with Zapcat for Tomcat (and Glassfish). Deploying WAR file is correct, the import of the host through the interface zapcat too, but my Tomcat will not start with the parameters jmxremote:

    Dcom.sun.management.jmxremote.port=8086
    -Dcom.sun.management.jmxremote.authenticate=true
    -Dcom.sun.management.jmxremote.password.file=C:\JDK 1.6\jre\lib\management\jmxremote.password.template
    -Dcom.sun.management.jmxremote.access.file=C:\JDK1. 6\jre\lib\management\jmxremote.access
    -Dcom.sun.management.jmxremote.ssl=false

    Without these parameters, Tomcat starts and works correctly. With, it does not start and give me the following errors in the logs:

    [2011-06-07 2:25:49 p.m.] [415 javajni.c] [error] Failed CreateJavaVM
    [2011-06-07 2:25:49 p.m.] [770 prunsrv.c] [error] Failed initializing java D: \ Tomcat \ bin \ bootstrap.jar
    [2011-06-07 2:25:49 p.m.] [982 prunsrv.c] [error] ServiceStart returned 2

    Please, if you have any idea, tell me because then I really do not know.
    Thanks
  • denisss
    Member
    • May 2011
    • 36

    #2
    There may be concepts that I do not understand (I'm newbie with Zabbix and Tomcat). To simplify, I will not use security:

    -Dcom.sun.management.jmxremote.port=8086
    -Dcom.sun.management.jmxremote.authenticate=false
    -Dcom.sun.management.jmxremote.ssl=false

    So I use port 8086 for up to MBeans (and this port is the port used for the admin) but it is perhaps not the port to be used. My Zapcat agent communicates over port 10052 is this the same? should I put jmxremote.port=10052? Or should I put an unused port (eg 8090)? I get mixed ... If anyone can help me understand?

    Thanks

    Comment

    • denisss
      Member
      • May 2011
      • 36

      #3
      Zapcat himself a JMX agent? Should we just turn jmxremote locally?

      -Dcom.sun.management.jmxremote

      Apparently not, always the same mistakes ...

      Comment

      • denisss
        Member
        • May 2011
        • 36

        #4
        Zapcat is there a JMX agent? JMXremote must run locally? with the command:

        -Dcom.sun.management.jmxremote

        Or should we specify a listener (the 10052?)? with the command:

        -Dcom.sun.management.jmxremote.port=10052
        -Dcom.sun.management.jmxremote.authenticate=false
        -Dcom.sun.management.jmxremote.ssl=false

        These orders must be placed in the Java tab of the Tomcat console? like this:

        Click image for larger version

Name:	tomcat_console.jpg
Views:	1
Size:	54.1 KB
ID:	309568

        Or so it must be specified somewhere else too?

        Sorry, i'm a newbie with Tomcat (and Zabbix)... But I really need help

        Comment

        • denisss
          Member
          • May 2011
          • 36

          #5
          for precise, my JVM is a JRockit

          Comment

          • denisss
            Member
            • May 2011
            • 36

            #6
            I found where was the problem. These commands are made to work with Sun's JVM, or I use Oracle's JRockit

            I found why, but I have not find how to resolve my problem ... What commands should I use for a JRockit with Tomcat?

            Comment

            Working...