Link: Added: This issue depends JBESB-2107

Screenshot

Attachment: Added: Screenshot.png

Screen shot fron JON console

Attachment: Added: Screenshot-1.png

Change byte total metrics to long.

When starting up SOA 4.3.0 CP01 with DB tables created with 4.3.0 GA (using the
default HS DB), I see an exception at start up:

  ERROR [JDBCExceptionReporter] Column count does not match in statement [insert into JMXDATA (id, STATID, SERVER, STATDATE, bytevalue, timevalue, countvalue, textvalue) values (null, ?, ?, ?, ?, ?, ?, ?)]

It looks like we need to:

  1) check the behaviour on supported databases
  2) provide an upgrade script for GA users, if necessary

Here is the old table structure :

CREATE TABLE JMXDATA (
ID INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH 1) NOT NULL PRIMARY KEY,
STATID INTEGER,
SERVER VARCHAR(255),
STATDATE TIMESTAMP,
TIMEVALUE FLOAT,
COUNTVALUE INT,
TEXTVALUE VARCHAR(255),
CONSTRAINT FK_ATTRIBUTE FOREIGN KEY(STATID) REFERENCES JMXATTRIBUTE
);

The change here looks like the addition of the BYTEVALUE column.

I think this means that together with the patched JON plugin, we need to provide upgrade db-scripts for *JON's backends*, right? AFAIUI this data is not stored in the SOA-P's db.

What about history? Will that all be available with the new plugin?

Just to clarify, by history I mean historical data.

Fixed with revision 2691 (4.3 branch of:
  build-tools/builders/eap/resources/management.esb/installed/jbossesbmanagement-service.xml
  build-tools/builders/eap/resources/management.esb/installed/upgrade_database.sql
  build-tools/builders/eap/resources/management.esb/tools/src/main/resources/hsqldb/upgrade_database.sql
  build-tools/builders/eap/resources/management.esb/tools/src/main/resources/jbossesbmanagement-service.xml
  build-tools/builders/eap/resources/management.esb/tools/src/main/resources/mysql/upgrade_database.sql
  build-tools/builders/eap/resources/management.esb/tools/src/main/resources/oracle/upgrade_database.sql
  build-tools/builders/eap/resources/management.esb/tools/src/main/resources/postgresql/upgrade_database.sql

Commit message:
  Add upgrade database scripts and *service.xml files to fix JIRA SOA-944.

and with revision 2693 (4.3 branch) of:
  build-tools/builders/eap/build.xml

Commit message:
  Install upgrade database scripts and *service.xml files to fix JIRA SOA-944.

Changed fixed-in version to CP02 - fix will be verified when a new version of JON is available. 

Looks like we have a new JON version shipped with CR3. So we should be able to test these scripts.

This was resolved in SOA-1227.

Link: Added: This issue is related to SOA-1227

added to 4.3.CP02 release notes as resolved:

JBESB-2107 - 

All the byte total metrics in ServiceMessageCounter are now measured using the data type of Long.  

Attachment: Added: fixed.png

Verified in CR2 + JON-2.2.0.GA

It looks good on the service level (serviceLevel.png) but on the action level (actionLevel.png) negative values are displayed for Overall Bytes.
On the service level this value is displayed in GB, on the action level in MB.

Attachment: Added: serviceLevel.png
Attachment: Added: actionLevel.png

Attachment: Added: cantreproduce.png

I can't reproduce this one (see cantreproduce.png).      From what I can see, the plugin is retrieving the correct values for Overall Bytes, I'm not sure what conditions got the values negative in your case (did you stop the monitored server?)    In any case, since the plugin is getting the right value, I think this is probably a JON/RHQ bug and should be filed over there with steps to reproduce.

Link: Added: This issue related SOA-1482