I think your problem is the JBoss implementation of JMX. According to JSR160, specifying persistPolicy=OnUpdate for an attribute should result in persisting every time the attribute is updated (from JSR160 1.4): persistPolicy – Defines the default persistence policy for attributes in this MBean that do not define their own persistPolicy. Takes on one of the … Read more
There are a few thing that might go wrong, so I will tell you what helped in my case (analogous to yours, I was using JDK 1.6.0_13). The problem lies in JARs mismatch. First of all make sure JBoss is using JDK 1.6 check your JAVA_HOME env. variable. Secondly make sure your classes are compiled … Read more
To say that any tool or framework is just ‘better’ is ridiculous. It always depends on the situation, architecture, etc. You don’t necessarily want to use a hammer to drive a screw. I wrote JBoss in Action, so I obviously like the JBoss technology, but I’ll be the first to say that JBoss can be … Read more
Looks like a bug that occurs with certain specific combinations of JRE and OS versions (see https://jira.jboss.org/jira/browse/JBAS-6981). Basically, the JBoss config is relying on reflection to return constructors in a certain order, and in some cases this order is different, causing the exception. Did you change your JRE version when you reinstalled, say from 1.6.0_17 … Read more