Hi,
Someone posted a message on the old 
spydermq list that looks like it belongs 
on this list. I am putting the original 
message and my response below. If 
someone finds something wrong with the 
facts in my response please correct me. 
Thanks,
Joel

***********
***********Mary wrote:
***********
Hi Joel,
I have rc1 of JBoss 3.0.0 and have been 
testing your interface for
topic creation/deletion both 
programmaticaly and from the JMX web
interface.

What I'm seeing is that topics are 
getting created successfully, and
I can delete them successfully. If I try 
to create a topic again
after having destroyed it however, I get 
this exception:

javax.jms.JMSException: This destination 
has allready been added to
the server!
        at 
org.jboss.mq.server.JMSServer.addDestination
(JMSServer.java:830)
         at 
org.jboss.mq.server.TopicManager.startService
(TopicManager.java:56)
         at 
org.jboss.system.ServiceMBeanSupport.start
(ServiceMBeanSupport.java:162)
         at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
         at 
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
         at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
         at 
java.lang.reflect.Method.invoke(Method.java:324)
         at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke
(ReflectedMBeanDispatcher.java:284)
...

If I do a JNDI lookup of the topic, it 
doesn't exist, and the server
log file says it was successfully 
destroyed, so I think this is a
bug.
I really need this feature so I will try 
to see if I can find
anything debugging in to it. Please let 
me know if you've encountered
this or fixed it. And thanks by the way 
for contributing this feature
to JBoss for us all!

Thanks,
Mary


********************
********************        My reply:
********************
Hi Mary,
Its been a Looooong time since I added 
the add/destroy queue/topic methods to 
the JMSServer class in the jbossmq 
module. I just checked out the most 
recent version from cvs, and everything 
I added is gone. This is a fast moving 
code-base!  I believe they moved all the 
functionality of those methods into the 
org.jboss.mq.server.DestinationManager 
class. From what I can see, it *should* 
be working. The stopService method is 
what I believe gets invoked 
automagically when you call 
destroyTopic/destroyQueue on the 
JMSServer MBean. This in turn invokes 
closeDestination() on the JMSServer 
class, and this method removes the 
topic/queue from the internal 
destinations HashMap. Unfortunately, it 
looks like somehow that destination 
isn't really being removed from the 
HashMap.

I don't have time to debug this right 
now, but I did, these are probably the 
steps I would follow:
1. Using debug logging or a debugger, 
trace the chain of invokers involved in 
a destroyTopic/queue call. From a quick 
glance, I think it goes something like 
(all classes in the org.jboss.mq.server 
package):
JBossMQService.destroyDestination() 
-->DestinationManager.stopService() 
-->JMSServer.closeDestination()

At the end of that chain, the 
topic/queue should be gone from jndi, 
and removed from the destinations 
HashMap in JMSServer. Maybe the end of 
the closeDestination() method in 
JMSServer would be a good time to 
iterate thru the hashmap and print out 
the names of the destinations it 
contains to be sure that is the case. If 
you find this isn't the case, and you 
can't find the cause, It would be a good 
time to post a bug report from jboss's 
sourceforge project page: 
(http://sourceforge.net/projects/jboss/ )

I will post this message to jboss-dev 
(which is where you should post/follow 
bugs. Spydermq on yahoo groups is pretty 
much a dead list) and someone there may 
have more info on this. If I get time 
this weekend or later next week I may be 
able to delve a little deeper into this 
as well. Good luck,
Joel


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to