Dean Anderson
2007-06-29 19:43:15 UTC
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.
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.
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.
Thanks,
--Dean
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.
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.
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.
Thanks,
--Dean
--
Av8 Internet Prepared to pay a premium for better service?
www.av8.net faster, more reliable, better service
617 344 9000
Av8 Internet Prepared to pay a premium for better service?
www.av8.net faster, more reliable, better service
617 344 9000