[JBoss-dev] jboss-head status

[Brian Stansberry]

I'm concerned there is going to be a problem with Tomcat components
(connectors, valves, managers, etc) that Tomcat will want to register in
JMX.  You mentioned earlier that "Subsequent use of this mbean as a
jboss mbean service can result in the ServiceController taking ownership
of the mbean"; I'm not quite sure what kinds of use will trigger this.

jboss-development-bounces at lists.jboss.org wrote:
> Yes, this is the current issue I see. My main question at
> this point is why should we have the separate
> MBeanServer.registerMBean/unregisterMBean +
> ServiceControler.lifecycle/remove. It clearly leads to
> duplicate state management. Why not say the only way to
> manage an mbean service is through the ServiceController drop
> all of the MBeanServer.registerMBean/unregisterMBean usage?
> 
> Jason T. Greene wrote:
>> Not sure if this is related, but take a look at [1]. The original
>> ServiceController unregisters on remove.
>> 
>> [1]
>> 
> http://lists.jboss.org/pipermail/jboss-development/2006-August/000776.
>> ht
>> ml
>> 
>> -Jason
>> 
>> 
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development



Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry