On 2001.11.26 22:50:55 -0500 David Budworth wrote:
> Hi all,
> 
> There are two things bugging me right now in JMS, and I just wanted to
> know if anyone is working on them, or if they need to be fixed at all.
> 
> The first one, is pretty obviously a 'needs-to-be-done'.  You can't
> current undeploy a queue/topic.
> 
> In my sar, I define the JMS queues that the services use, and when I
> undeploy the .sar, the log says "queue stop not yet implemented".
> 
> The problem this causes is that once you delete the SAR, the queue name
> disappears from the 8082 UI, but, if you attempt to re-deploy the SAR,
> or just create the queue via the 8082 UI, you'll get a an error stating
> the topic/queue already exists.
> 
> So it seems that on undeploy, the internal stuctures of JBossMQ gets
> fux0r3d (in script-kiddie speak).
> 
> I'd be happy to work on this (since I need it).  I just didn't know if
> anyone else was already doing it.  Nor do I really know where to start
> on it.
> 

I'm not the most expert... but I think the queue stop method needs to
arrange with the JMSService to stop accepting messages and possibly with
the persistence manager to make sure everything is stably saved that should
be.  Make sure all open transactions are ended before shutting down!
> 
> 
> The second one is just something that bothers me, which is if you
> specify a queue name like:
> mycompany/queuea
> 
> You will get a name not bound exception on "mycompany".  For EJBs this
> works correctly, where the subcontexts are created on the fly as need
> be.  But for JMS it doesn't.
> 
> I'd also like to add this, since I don't like having the JMS
> topics/queues in a flat namespace.
> 
> I'm not sure if this is by spec though.  Are you not allowed to create a
> heirarchy for the queue/topic names?  If I create transient topics, I
> can do it if I pre-create the subcontexts.  So I know it 'works', I'm
> just not sure it's legal.
> 
> Also, is there some helper code somewhere in jboss to create a JNDI tree
> already?  Or does everyone just roll there own with tokenizers or
> something?

I feel like I've seen 10 or twenty implementations of this, but its
probably just 3 or 4;-)  They are often in Deployers.  Could we put one
version in either DeployerMBeanSupport or ServiceMBeanSupport?

David Jencks
> 
> -David
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to