Re: Bug in openjms 0.7.7 beta 1

Dean Anderson <[email protected]> Mon, 2 Jul 2007 16:28:54 -0400 (EDT)
Newsgroups gmane.comp.java.openjms.devel
Message-ID <[email protected]>
On Mon, 2 Jul 2007, Tim Anderson wrote:

> 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.

Hmm. Maybe I misunderstood. I'm going off the old Oreilly Java Message
Service book, which says page 123:

"It is the responsibility of the JMS provider to call the onException() 
method of all registered ExceptionListeners after making reasonable 
attempts to reestablish the connection automatically"

I take the plural and 'all' to mean that more than one thing (presumably
each sesssion) can register an ExceptionListener on a connection.
OpenJMS only allows one exceptionListener.


> 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.

Ok.  Thanks.

Is it safe to assume that in a web container, only one thread at a time
works on a given web request?  So, if I put the JMS session object in
the web-container session store, is it safe to assume there is only one
thread that handles each web request for a given (web)session?  Sorry if
this is web-specific, but any experiences with this is appreciated.

> > 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.

Oops. Good point on the RMI registry--Must make a note of that. However,
the initialization part should _still_ work.  Something else might need
initialization...

Thanks!

		--Dean




-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 344 9000   



-------------------------------------------------------------------------
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/