This is probably not relavent, but I thought I'd throw it in.
I had a similar problem, and it turned out to be that somehow my MBean ended
up being put into jboss-auto.jcml twice without me knowing it. What was
happening was two of my MBeans were trying to start at the same time, and
the second instance was getting the "NameAlreadyBoundExceptions"s. I just
deleted the jboss-auto.jcml. I was never able to reproduce the
circumstances causing the double entries, but I've seen it at least twice.
Probably not your problem, but FYI...
Jim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Frederick N.
> Brier
> Sent: Sunday, July 29, 2001 8:07 AM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] MBean NameAlreadyBoundException
>
>
> The second time a server comes up the console is showing
> NameAlreadyBoundException(s) when an MBean name in its JNDI bind()
> call. Now unbind() is called within the stopService() method, but my log
> message never shows that the stopService() method is ever called. The
> MBean extends org.jboss.util.ServiceMBeanSupport. Now I could catch the
> NameAlreadyBoundException and try to rebind() it, but that seems like a
> hack or a preventative measure. What do I need to do to get the
> stopService method to be called?
>
> Lastly, is there an easy way to clear all the names out of the JBoss JNDI
> namespace, such as editing a flat text file, or deleting a binary file
> sitting in a JBoss directory?
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
