I will code a 'fix' (still not sure if this is a bug or not) and post it for you to look at.
David gnodet wrote: > > Never heard of the problems, but your solution sounds good, though > I'm not keen on using queryNames instead of isRegistered. I guess > if we rely on the return value from the register call to work around > the problem, as we should have access to the actual name used. > > On 3/5/07, David Potter <[EMAIL PROTECTED]> wrote: >> >> When running serviceMix V3.0 on WebSphere 6.1.0.0 I get the following >> error >> after stopping and starting serviceMix from the WebSphere console. >> >> ERROR - ContextLoader - Context initialization failed >> org.springframework.beans.factory.BeanCreationException: Error creating >> bean >> with name 'jbi' defined in ServletContext resource >> [/WEB-INF/servicemix.xml]: Invocation of init method failed; >> nested exception is >> javax.jbi.JBIException: javax.management.InstanceAlreadyExistsException: >> org.apache.servicemix:Name=ManagementContext,cell=SD1464Node01Cell,Type=SystemService,ContainerName=ServiceMix,node=SD1464Node01,process=server1 >> >> I have traced the error to the fact that when you register an mbean IBM >> adds >> additional information to the bean. So when serviceMix regesters the bean >> org.apache.servicemix:Name=ManagementContext,Type=SystemService,ContainerName=ServiceMix >> IBM, in the method >> com.ibm.ws.management.PlatformMBeanServer.registerMBean(PlatformMBeanServer.java:469) >> , adds the attributes cell=SD1464Node01Cell, >> node=SD1464Node01,process=server1 >> >> These means that when we try to unregister the bean on application >> shutdown >> we cannot find it (as we look the been up by name). >> >> Ideas for solutions: >> In AsyncBaseLifeCycle.doInit() use queryNames() instead of >> isRegistered(). >> Care would need to be taken in unregistering the bean is case the bean is >> not ours. >> After a bean is registered, update its name (or the complete bean) with >> the >> name of the bean returned by the register operation. >> >> I have not look at these options in detail yet or the impact of >> clustering >> on this process. I will be doing this soon. Any comment on this? Has any >> one >> else found similar problems? >> >> Thanks >> David >> >> -- >> View this message in context: >> http://www.nabble.com/Error-running-ServiceMix-in-WebSphere-6.1-tf3344839s12049.html#a9302477 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Error-running-ServiceMix-in-WebSphere-6.1-tf3344839s12049.html#a9328355 Sent from the ServiceMix - User mailing list archive at Nabble.com.
