[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1958) Fix the clusteredsession test failure against AS trunk

[jaikiran pai (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12495969#action_12495969 ] 

jaikiran pai commented on EJBTHREE-1958:
----------------------------------------

I guessed that removing the property was the fix, but wasn't sure. So thanks for confirming :)

> Fix the clusteredsession test failure against AS trunk
> ------------------------------------------------------
>
>                 Key: EJBTHREE-1958
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1958
>             Project: EJB 3.0
>          Issue Type: Task
>          Components: testsuite
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> JBAS-7209 removed the nodeAddress property from the org.jboss.ha.framework.server.ClusterPartition MC bean. The EJB3 testsuite (clusteredsession testcases) has testlocal-jboss-beans.xml which has references to this property. As a result, this file fails to deploy against AS trunk with the following exception:
> Caused by: java.lang.IllegalArgumentException: No such property nodeAddress for bean org.jboss.ha.framework.server.ClusterPartition available [allowSynchronousMembershipNotifications, haPartitionDependencyCreator, JGroupsVersion, threadPool, nodeName, state, currentView, bindIntoJndi, serviceName, stateString, clusterNodes, stateTransferTimeout, distributedStateService, clusterNode, name, currentViewId, distributedReplicantManager, methodCallTimeout, partitionName, distributedReplicantManagerImpl, class, kernelControllerContext, log, channelStackName, DRMServiceNames, channelFactory, cacheHandler, distributedStateImpl, currentNodeCoordinator, cacheConfigName, notificationInfo, server]
> 	at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:147)
> The test config needs to be fixed.
> P.S: The fix to that test config should be done in such a way that the test remains compatible against EAP-5 
>  
>  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira