[ZBX-14615] JMX errors with non-network errors Created: 2018 Jul 17  Updated: 2024 Apr 10  Resolved: 2018 Oct 08

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Java gateway (J), Server (S)
Affects Version/s: 3.4.11, 4.0.0alpha8
Fix Version/s: 4.0.1rc1, 4.2.0alpha1, 4.2 (plan)

Type: Problem report Priority: Major
Reporter: Alexey Pustovalov Assignee: Vladislavs Sokurenko
Resolution: Fixed Votes: 0
Labels: jmx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File snmp_availability.png    
Issue Links:
Duplicate
Team: Team A
Sprint: Sprint 38, Sprint 39, Sprint 40, Sprint 41, Sprint 42, Sprint 43, Sprint 44
Story Points: 0.2

 Description   

Sometimes Zabbix Java Gateway can not process items due to username/login issues, such issues should not affect to JMX availability at all, because it is not network related issue, it is item misconfiguration. For example, in the frontend, error can be seen for the host jmx status : "java.lang.IllegalArgumentException: invalid username and password nullness combination".

 Comments   
Comment by Vjaceslavs Bogdanovs [ 2018 Jul 23 ]

(1) [D] Changes made in this development will affect existing Zabbix setup so we should add a note stating that:
From now on Zabbix Java gateway availability status will not change to red each time any of the items become not supported. JMX availability badge will only become red on network errors - when Java gateway is not available or when there are some communication problems between Zabbix server and Zabbix Java gateway.

martins-v Added to the upgrade notes. RESOLVED

mindbound The documentation of the changes is looking good. CLOSED.

Comment by Arets Paeglis (Inactive) [ 2018 Aug 08 ]

Available in 4.0.0alpha10 (trunk) r83301.

Comment by Vladislavs Sokurenko [ 2018 Sep 05 ]

Fixed in development branch:
svn://svn.zabbix.com/branches/dev/ZBX-14585-2

This is related to ZBX-14585, so it's better to fix together.
Now should be consistent with how SNMP works:

Comment by Vladislavs Sokurenko [ 2018 Oct 03 ]

Fixed in:

  • pre-4.0.1rc1 r85393
  • pre-4.2.0alpha1 (trunk) r85394
Generated at Thu Apr 25 23:27:11 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.