Sorry if I shooÂd a hamster out of the hen house but it would be nice if Jboss
didnÂt print stack trace's to the log file unless there is actually a problem. I
would much rather have the code changed to:
public void asynchFailure(String error, Throwable e)
{
if (trace)
log
For whatever it is worth I have tracked down with exception to the following code (I
think).
org.jboss.mq.il.uil2.SocketManager.java
private void handleStop(String error, Throwable e)
{
.
.
.
replyAll(e);
if (handler != null)
{
The exception I get on the server log is the following.
2004-07-06 10:27:59,743 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2004-07-06 10:27:59,743 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
Exiting on IOE
java.net.SocketException: Socket closed
at java.net.
The problem went away when I recompiled the server and client of my application with
the 3.2.4 jar's. But I still get a SocketException on the server when I execute
queueConnection.close() on the client.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840507
After tracing through the code it looks like the subscriber is not being removed from
the queue before the system tries to delete the queue.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839981#3839981
Reply to the post :
http://www.jboss.org/index.html?m
So. I have searched the list and cannot find any resolution to this problem even
though there are a few messages about it. I had the problem in the 3.0.x days but my
code has been working for awhile but now with 3.2.4 this problem has reared its ugly
head again.
So does anybody know how to use
