Ad Widget

Collapse

unable to monitor WebLogic

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • boniface
    Junior Member
    • Dec 2013
    • 8

    #1

    unable to monitor WebLogic

    Hello,

    Running on a single host WebLogic, Zabbix, Java gateway. Everything is of the latest stable version and supposed to be connecting through 127.0.0.1.

    zabbix_server.conf:
    JavaGateway=127.0.0.1
    JavaGatewayPort=10052
    StartJavaPollers=5

    Additionaly added in server configuration JMX interface on 127.0.0.1:10052.
    I fully restarted the server after configuration, but JMX indicator is still red and zabbix_java.log (attached) contains errors:
    2013-12-16 15:47:02.234 [pool-1-thread-4] WARN com.zabbix.gateway.SocketProcessor - error processing request
    com.zabbix.gateway.ZabbixException: bad protocol header: 4A 52 4D 49 00
    ...
    2013-12-16 15:47:02.237 [pool-1-thread-2] WARN com.zabbix.gateway.SocketProcessor - error processing request
    com.zabbix.gateway.ZabbixException: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]

    btw, I know also there is a bug, which is still unresolved, but not sure this is the real cause.
    Attached Files
  • boniface
    Junior Member
    • Dec 2013
    • 8

    #2
    the solution was found

    Generally, the idea is to access WebLogic runtime mbeans through the JVM's MBean server, not through the WebLogic's native one. How to make so? There is a nice guide here, but it started working fro me just when I added to the args:
    -Djavax.management.builder.initial=weblogic.managem ent.jmx.mbeanserver.WLSMBeanServerBuilder
    -Dcom.sun.management.jmxremote.rmi.port=9999

    Hope this helps.

    Comment

    • Bruno Carvalho
      Member
      • Oct 2014
      • 32

      #3
      See if my article helps you: http://brunocarvalho.net/blog/2016/0...me-com-zabbix/

      Comment

      Working...