-
1. Re: JBoss 4.0.3 SP1: org.jboss.test.compatibility.test.Seria
ryan.campbell Feb 17, 2006 12:19 PM (in response to prakah)It looks like there was an interface change between 4.0.1 and 4.0.3SP1 but I'm not sure why this wasn't picked up by our run of the compatibility tests before release, or even subsequent runs such as this one.
Of course, our runs are on the sun jvm, and i guess you are running on the HP-UX jvm? -
2. Re: JBoss 4.0.3 SP1: org.jboss.test.compatibility.test.Seria
prakah Feb 28, 2006 2:07 AM (in response to prakah)Hello,
Yes, i am using the HP-UX JVM.
Some more inputs regarding this error.
I tried the same test in linux machine with the SUN JVM and the test case passes. When i debugged the reason for the success of the test case in linux, the two classes which i mentioned in the previous post were not considered for compatibility test. Following steps has been done to accomblish this one.
1. Add the following line to <JBOSS_SRC_HOME>/varia/src/main/org/jboss/tools/SerialVersionUID.java to print the serialVersionUID's for the all the classes.
79 System.out.println("serialVersion====="+classSerialVersion+"======classname====="+classname);
2. Export the classpath
$ export CLASSPATH=<JBOSS_SRC_HOME>/varia/output:<JBOSS_SRC_HOME>/third-party/junit/lib/junit.jar:<JBOSS_SRC_HOME>/testsuite/output/classes
3. Run the program
$ export JAVA_OPTS="-Xms512m -Xmx512m -XX:MaxPermSize=512m"
$ cd <JBOSS_SRC_HOME>/testsuite/output
$ java -Djbosstest.dist=<JBOSS_SRC_HOME>/build/output/jboss-4.0.3sp1 org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase > output.txt
This will generate the output.txt file with the serialVersionUID and classname.
Following is the snippet of the output from linux and HP-UX.
Linux
####
serialVersion======0======classname=======org.jboss.monitor.alarm.Alarm
serialVersion======0======classname=======org.jboss.monitor.alarm.AlarmHelper
serialVersion======0======classname=======org.jboss.monitor.alarm.AlarmKey
serialVersion======0======classname=======org.jboss.monitor.alarm.AlarmManager$1
serialVersion======0======classname=======org.jboss.monitor.alarm.AlarmManager$Severity
serialVersion======0======classname=======org.jboss.monitor.alarm.AlarmManager
serialVersion======0======classname=======org.jboss.monitor.alarm.AlarmTable$1
serialVersion======0======classname=======org.jboss.monitor.alarm.AlarmTable
serialVersion======0======classname=======org.jboss.monitor.alarm.MBeanImplAccess
HP-UX
#####
serialVersion=====0======classname=====org.jboss.monitor.alarm.Alarm
serialVersion=====0======classname=====org.jboss.monitor.alarm.AlarmHelper
serialVersion=====0======classname=====org.jboss.monitor.alarm.AlarmKey
serialVersion=====0======classname=====org.jboss.monitor.alarm.AlarmManager$1
serialVersion=====0======classname=====org.jboss.monitor.alarm.AlarmManager$Severity
serialVersion=====0======classname=====org.jboss.monitor.alarm.AlarmManager
serialVersion=====-7041616127511632675======classname=====org.jboss.monitor.alarm.AlarmNotification
serialVersion=====0======classname=====org.jboss.monitor.alarm.AlarmTable$1
serialVersion=====0======classname=====org.jboss.monitor.alarm.AlarmTable
serialVersion=====-2307598716282112101======classname=====org.jboss.monitor.alarm.AlarmTableNotification
This comforms that, in linux the error coming classes are not taken into account for the compatibility test. I can't understand, why these happens. But, i think this why you haven't received the errors while testing.
Please suggest, any way to solve this error.
--Prakash.A -
3. Re: JBoss 4.0.3 SP1: org.jboss.test.compatibility.test.Seria
ryan.campbell Mar 8, 2006 9:12 PM (in response to prakah)Ok, Prakash we may have a problem with our SerialVersionUID code. Can you create a JIRA for this at http://jira.jboss.com ? And post the JIRA id here. Thanks.
-
4. Re: JBoss 4.0.3 SP1: org.jboss.test.compatibility.test.Seria
prakah Mar 20, 2006 12:40 AM (in response to prakah)Hello,
Bug has been failed against the JBoss AS test suite and the Bug id is http://jira.jboss.com/jira/browse/JBAS-2965
--prakash.a