I'm highly confused by trying to guess what you might be doing. What
configuration are you running? What do you mean by "the second time a
server comes up?" Are you running any non-jboss mbean servers or jndis?
My impression was that jboss jndi was 100% non persistent, when you stop
your jboss instance everything goes away, and this is what I observe.
Have you written your own mbean? How do you deploy it?
What exactly is your configuration, what you are doing, and the result you
don't like?
david jencks
On 2001.07.29 11:07:17 -0400 Frederick N. Brier wrote:
> 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
