Created attachment 1139480 [details] exception Description of problem: This is just random exception found in server.log -> no clear repro steps. Any advice when this can happen will help to find repro steps. Log is attached. Version-Release number of selected component (if applicable): JON 3.3.5 with eap plugin pack update04-DR01
After taking a peek on the code, it seems that it could happen when trying to add a MeasurementDataTrait that has null on its 'value' attribute. Do you know if is it possible to happen? If that's the case, it will skip the whole batch of trait data on this NPE.
It seems that it can be null [1][2]. Made a PR, Test if value is not null before using it. https://github.com/rhq-project/rhq/pull/263 [1] gaYak: Yea, I think traits can have null if it's not available on the destination [2] https://github.com/josejulio/rhq/blob/db260b10b1918b73dc0de213f6cbd000fb4f1dac/modules/plugins/wfly-10/src/main/java/org/rhq/modules/plugins/wildfly10/BaseServerComponent.java#L1006-L1011
commit 471fe45983d3be68aa0e618c486ecc352fc27476 Merge: c7014c2 bc3d7ec Author: Michael Burman <yak> Date: Fri Jun 3 15:29:06 2016 +0300 Merge pull request #263 from josejulio/bugs/1320478 Bug 1320478 - NPE in server.log Error persisting trait data commit bc3d7ecad06d18655c2fd9e4827c9bb3c0195c4d Author: Josejulio Martínez <jmartine> Date: Wed Jun 1 15:25:19 2016 -0500 Bug 1320478 - NPE in server.log Error persisting trait data Test if value is not null before using it.
Moving to ON_QA as available to test with the following build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=502442 Note: jon-server-patch-3.3.0.GA.zip maps to JON 3.3.6(jon-server-3.3.0.GA-update-06.zip)
verified in JON 3.3.6 ER01 performed added a MeasurementDataTrait that has null on its 'value' attribute but did not find NPE in server.log
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-1519.html