Description of problem: In the ByteMan logging of JBoss ON server there are some BaseLineMean values which are set to Nan. Main reason for it seems that, in the class "org.rhq.core.domain.measurement.MeasurementBaseline" all values are defined with "nullable = false" Because of these Nan there are multiple WARN messages in the JBossON server logs. Version-Release number of selected component (if applicable): 3.3.4 How reproducible: Configure Oracle database with JBossON. Configure ByteMan Logging as per Article https://access.redhat.com/solutions/1469933. Steps to Reproduce: 1. 2. 3. Actual results: Nan values are tried to be inserted in the database. Expected results: NaN values shuold not be inserted in Oracle. Additional info:
Moving to ON_QA as available for test with the latest build: JON 3.3.8 CR01 artifacts are available for test from here: http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/114/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of jon-server-3.3.0.GA-update-08.zip. https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=537179
Moving to ON_QA as available for testing with the following build: http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/117/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *Note: jon-server-patch-3.3.0.GA.zip maps to CR02 build of jon-server-3.3.0.GA-update-08.zip.
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/RHEA-2017-0285.html