[jboss-jira] [JBoss JIRA] (JGRP-1550) 2.6.22.Final not running on 1.6 JVM

MIchael Yates (JIRA) jira-events at lists.jboss.org
Wed Dec 5 19:56:21 EST 2012


    [ https://issues.jboss.org/browse/JGRP-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739813#comment-12739813 ] 

MIchael Yates commented on JGRP-1550:
-------------------------------------

I am not sure if it helps track down what went wrong but there are a few other anomalies with this release as well. 
- no release notes available here: https://issues.jboss.org/secure/ConfigureReleaseNote.jspa?projectId=10053
- 21 is labelled 2.6.21.FINAL whilst 22 is labelled 2.6.22.Final. Note the difference in capitalisation. 

Certainly I am not saying that these things are the cause. Just noticing that there seem to be other differences in this 2.6.22 release vs the 2.6.21 release.

I am yet to try your suggestion of building my own version of the jar - but feel fairly comfortable it will be a suitable workaround for our situation.

                
> 2.6.22.Final not running on 1.6 JVM
> -----------------------------------
>
>                 Key: JGRP-1550
>                 URL: https://issues.jboss.org/browse/JGRP-1550
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6.21
>         Environment: JVM 1.6
>            Reporter: MIchael Yates
>            Assignee: Bela Ban
>             Fix For: 3.3
>
>
> 2.6.22 has been built using JDK 7
> #A dump from a 2.6.21 class
> hexdump -n20 ./org/jgroups/MembershipListener.class 
> 0000000 ca fe ba be 00 00 00 32 00 0d 07 00 0b 07 00 0c
> #A dump from a 2.6.22 class
> hexdump -n20 ./org/jgroups/MembershipListener.class 
> 0000000 ca fe ba be 00 00 00 33 00 0d 07 00 0b 07 00 0c
> Note the 8th octet has changed form 32 to 33. ie from JVM6 to JVM7
> I suspect this is an oversight when 2.6.22 was built. Maybe -source and -target parameters forgotten on the build?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list