Re: Bug in openjms 0.7.7 beta 1

Dean Anderson wrote:
> First, thanks for beta 1 release.
>
> I noticed while looking through the code that there can be only one
> exception listener. The spec allows multiple listeners to be registered. 
> This is an easy fix.
>   
Not sure what you mean. There can be one exception listener per 
javax.jms.Connection instance.

> I noticed this while thinking about handling the case of a cached
> connection in a web-app, and restarting the connection (after a jms
> server restart), losing (cached) sessions, etc.
>
> I started thinking about that because I was thinking of using a
> temporary queue in a reply-to in a web-app, and the temporary topic only
> lasts as long as the connection and session, so 1) connections and
> sessions have to be cached. 2) one needs to handle the case of a jms
> server restart.
>   
You can also attempt to re-establish the connection if the 
publish/subscribe fails.
When caching sessions, you just need to ensure that you synchronize 
access so only one thread
as session at a time.
> I think a container tomcat maybe shouldn't register an exception
> handler, either, though I might be able to make it work anyway...  Does
> anyone have any experiences they'd like to share?  EJB is not a happy
> choice.
>
>
> BTW, I also noticed that tcps connections don't work with an external
> jndi rmi registry, unless you hard code a property for the new trust
> store.  Seems like something for SSL in the client doesn't get
> initialized properly when using an external jndi provider.  Server works 
> fine.
>   
Haven't tried. Typically you wouldn't use an rmi registry and tcps, as 
the rmi registry is not secure.
You are better off using the embedded JNDI provider.
> Thanks,
>
> 		--Dean
>   
-Tim

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/