The changes you made resolved the problem I was seeing -- failing
org.jboss.test.cluster.defaultcfg.test.HASingletonElectionPolicyUnitTestCase. I also see
the HASingletonController for the HASingletonDeploymentScanner bean now properly starts
the singleton (although the scanner doesn't work correctly -- unrelated issue).
I saw a couple regressions from this:
1) HAPartitionStateTransferTestCase has some failures. This is because the test fixture
overrides ServiceMBeanSupport.start() and caches a ref to any exception thrown. Your
addition of @Start public void pojoStart() means an exception thrown in startService() no
longer propagates through start(). I changed the fixture to override startService()
instead of start() (which is more correct anyway) and the test works fine.
2) PartitionRestartUnitTestCase now fails. I don't see anything wrong with the way
ServiceMBeanSupport is working in this test; its a UnifiedInvoker/Remoting issue. See
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136822. It's not
clear to me why this test started failing now, other than that perhaps ServiceMBeanSupport
wasn't working properly before and was masking the remoting issue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155822#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...