The 'bytesSent' metrics on web subsystem connectors is defined in the code to be ModelType.INT, but the data it received from the JBossWeb is a long. For some (presumably historical) reason, it sets the value on the ModelNode as: "" + info.getBytesSent() which results in the String form of a long value, and when it later gets parsed back to an int, that will fail if the long value was greater than Integer.MAX_VALUE. The two solutions to this are to either change the type of the metric attribute from INT to LONG (and some of the other metrics as well), or alternatively coerce the long value to an int before using it. Would changing a runtime attribute from int to long be a breaking change? If so, the latter would be the only option. This problem does not exist upstream in WildFly, since the Undertow subsystem uses long metrics where appropriate.
To reproduce: 1) Send 4gb or more over a single connector 2) Query the 'bytesSent' metric of 'jboss.as:connector=AJP,subsystem=web' over JMX
I am checking the fix for this issue with EAP 6.4.6.CP.CR2 Now the behaviour doesn't throw exception when accessing the metric when there would be number greater than Integer.MAX_VALUE, instead it can return negative number => incorrect number from the metric point of view. In previous version of EAP (withouth the fix) in case of jboss-cli there is returned String representation of that value which is correct even for values greater than Integer.MAX_VALUE. In case of using JMX (jconsole), I was getting value unavailable. From my PoV it is worse to give incorrect value than parsing value bigger than int causing parsing error (such error I would say is OK). Note it is possible from the management model to retrieve the value and convert it to long even though the ModelType is declared as Integer (with EAP 6.4.5.CP it gives correct number, with EAP 6.4.6.CP.CR2 it gives incorrect value, even negative one)
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.