Ad Widget

Collapse

Upgrade to zabbix 3.4 broke Jolokia JMX

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • kevinwalter
    Junior Member
    • May 2017
    • 5
    #1

    Upgrade to zabbix 3.4 broke Jolokia JMX

    Hi,

    After the upgrade to Zabbix 3.4 my Jolokia monitoring is broken.

    I was still using this version of the Zabbix Java Gateway: https://bitbucket.org/ryanrupp/zabbi...eway/wiki/Home

    "2018-01-24 10:29:38.327 [pool-1-thread-85] WARN com.zabbix.gateway.SocketProcessor - error processing request: JSONObject["conn"] not found."

    Can anyone see what I'm doing wrong?

    Kind Regards,

    Kevin
    Tags: None
    • Atsushi
      Senior Member
      • Aug 2013
      • 2028
      #2
      You can change JMX endpoints from Zabbix 3.4.
      Therefore, communication between the Zabbix server and JavaGateway may have changed.

        Comment

        • kevinwalter
          Junior Member
          • May 2017
          • 5
          #3
          Originally posted by Atsushi
          You can change JMX endpoints from Zabbix 3.4.
          Therefore, communication between the Zabbix server and JavaGateway may have changed.
          Hi Atsushi,

          Okay, is it possible to change that parameter back to the old parameter?
          And what was the old parameter? :-)

            Comment

            Previous template Next
            Working...