Re: Bug in openjms 0.7.7 beta 1
Tim Anderson <[email protected]> Tue, 03 Jul 2007 09:54:56 +1000
| Newsgroups | gmane.comp.java.openjms.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============0983440569==
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dean Anderson wrote:
<blockquote
cite="midPine.LNX.4.44.0707021555270.11071-100000-Ug9HEdaa1HzbsVrRdE8xf16hYfS7NtTn@public.gmane.org"
type="cite">
<pre wrap="">On Mon, 2 Jul 2007, Tim Anderson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dean Anderson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">Not sure what you mean. There can be one exception listener per
javax.jms.Connection instance.
</pre>
</blockquote>
<pre wrap=""><!---->
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.
</pre>
</blockquote>
No. The Connection interface takes a single exception listener via the <br>
setExceptionListener(ExceptionListener listener) method. You're book is
just saying<br>
that each Connection instance needs to notify its associated listener
when the connection is lost.<br>
<blockquote
cite="midPine.LNX.4.44.0707021555270.11071-100000-Ug9HEdaa1HzbsVrRdE8xf16hYfS7NtTn@public.gmane.org"
type="cite">
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
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.
</pre>
</blockquote>
A client can submit simultaneous requests so you still need to
synchronize.<br>
<blockquote
cite="midPine.LNX.4.44.0707021555270.11071-100000-Ug9HEdaa1HzbsVrRdE8xf16hYfS7NtTn@public.gmane.org"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
</blockquote>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
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
</pre>
</blockquote>
Not sure what you mean. When using the RMI registry, you need to
connect to it using the rmi protocol.<br>
If the tcps connector is also configured, ConnectionFactory instances
bound in the registry will connect<br>
to the server via tcps; you need to configure the tcps properties as
per <a class="moz-txt-link-freetext" href="http://openjms.sourceforge.net/usersguide/tcps.html">http://openjms.sourceforge.net/usersguide/tcps.html</a><br>
<br>
-Tim<br>
<br>
</body>
</html>
--===============0983440569==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-------------------------------------------------------------------------
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/
--===============0983440569==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
openjms-developer mailing list
openjms-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openjms-developer
--===============0983440569==--