[jboss-jira] [JBoss JIRA] Reopened: (JBAS-8368) HAPartition MBean reports wrong JGroupsVersion
Jason Greene (JIRA)
jira-events at lists.jboss.org
Thu Apr 21 14:26:55 EDT 2011
[ https://issues.jboss.org/browse/JBAS-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Greene reopened JBAS-8368:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.
> HAPartition MBean reports wrong JGroupsVersion
> ----------------------------------------------
>
> Key: JBAS-8368
> URL: https://issues.jboss.org/browse/JBAS-8368
> Project: Legacy JBoss Application Server 6
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-5.1.0.GA
> Environment: JBossAS 5.1.0.GA, JAVA 1.6.0_17, Sun Solaris
> Reporter: martin walla
> Fix For: No Release
>
>
> On JMX Console the MBean jboss:service=HAPartition,Partition=.... has an attribute JGroupsVersion.
> This displays 2.6.10.GA( $Id: Version.java,v 1.59.2.18 2009/04/28 14:25:33 vlada Exp $)
> I have updated the JGroups version by removing the jgroups.jar and adding the jgroups-2.6.15.GA.jar.
> After the startup the HAPartition MBean still reports 2.6.10.GA
> IMHO the problem is that the class org.jboss.ha.framework.server.ClusterPartition uses the class org.jgroups.Version to get the attributes "description" and the "cvs" info in the method getJGroupsVersion().
> But the strings in the class org.jgroups.Version are static final and therefore the value is added to the bytecode of the class org.jboss.ha.framework.server.ClusterPartition at compile time. A change of the jgoups version didn't change that.
> So org.jboss.ha.framework.server.ClusterPartition reports the JGroupsVersion against it was compiled and that which it is available.
> A use of the Method org.jgroups.Version.printDescription() instead should fix the problem IMHO.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list