servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant McDonald (JIRA)" <>
Subject [jira] Commented: (SM-883) MBean registration in Websphere returns different objectName
Date Fri, 06 Apr 2007 06:25:35 GMT


Grant McDonald commented on SM-883:


When supplying patches can you please supply them in unified diff format from the root of
the trunk (preferably using svn diff and aggregated to one patch file) since this makes them
much easier to apply in addition to being able to easily see the changes.



> MBean registration in Websphere returns different objectName
> ------------------------------------------------------------
>                 Key: SM-883
>                 URL:
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-core
>    Affects Versions: 3.0.1, 3.1
>         Environment: Windows XP SP1, Ubuntu Linux, Java 1.5
>            Reporter: Grant McDonald
>         Assigned To: Grant McDonald
>             Fix For: 3.2, incubation
>         Attachments:,
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
> Description courtesy of David Potter:
> When running serviceMix V3.0 on WebSphere 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:
> 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
> , 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).
> Solution Ideas:
> 1) 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.
> 2) After a bean is registered, update its name (or the complete bean) with the
> name of the bean returned by the register operation. (this is preferred)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message