If you look here in 24 hours time you will a couple of fixes that might be the
cause of your problem:
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/Connection.java
Sourceforge's anonymous cvs access is upto 24 hours behind the real thing.
View the original post :
http
"yxyang" wrote :
|
| By the way, what is the exact meaning of "ping timeout"? I think the best solution
is to find out why "ping timeout" happened?
|
|
I added it to the FAQ topic, time for you to re-read "READ THIS FIRST",
particularly the part that begins "If you suspect a hang/dead
Hi, Adrian
The ping timeout happened again after 30 hours' stress testing (routing 120
messages/second).
But this time, i got more information.
In the following, i list the output of log.error(...) and System.out.println(...).
(1) "init() return successfully" is the output of init() method. Once
It is not closed yet, that is the work you are doing.
All that has happened is that the connection has informed of a potential error,
what you do is up to you. Closing and recreating the connection is usually the
solution.
Also from the spec:
| JMSException - if the JMS provider fails to clos
Hi Adrian
I don't think this will be the case. Anyway, i am testing it now. It need more than
one day to get the result.
According to the JMS specification, the exceptions delivered to ExceptionListener are
those which don't have any other place to be reported (such as network problem).
Closi
I'll bet if you debug it, you'll see something like:
thread1 - exceptionListener.onException()
thread1 - thread2.start();
thread2 - connection.close()
thread2 - exceptionListener.onException()
thread2 - thread3.start()
etc.
Try doing oldConnection.setExceptionListener(null) before closing so th
Hi,
I have the same problem.
In my case, a standalone java application listens on a queue, After one days working,
this problem happened. I have an onException implemented in the application and also,
the onException() is called. Within this onException(), i try to close() the
oldconnection fi
I've just started occaisionally experiencing this at a customer site at about
midnight. Thanks for the fix. My question is what are we fixing? Why does the
connection fail? I've got heartbeats going back and forth every 30secs. Shouldn't
this keep it alive? Or is there some other failure
? A receive timeout does not cause the connection to be closed.
It is better for onException() to do the reconnect by closing the connection
and reconnectioning - see the version in JBoss's MDB container.
http://cvs.sourceforge.net/viewcvs.py/jboss/jboss/src/main/org/jboss/ejb/plugins/jms/JMSConta
In the case of receive timeout, the connection is closed. In order to receive the
message again, the connection/session/subsdriber all need to be recreated? So if
there is no message available on the tipic destination, every timeout interval the
connection will be destroyed and rebuild? What'
"richieb" wrote : "lucasfowler" wrote : Thanks for the infos here.
| |
| | We have added an exceptionListener and that seems to have done the trick.
|
| And what does your listener do?
|
| ...richie
OK, we are running in a servlet so we can't start another thread. So we
set up t
I have two subscribers, one MBean and one MDBean that in 1 min apart, the exceptoin
was thrown as in the following:
07:57:05,473 WARN [Connection] Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable:
(java.io.IOException:
ping timeout.)
at org.jboss.
Hi Guys,
I am also experiencing this 'problem' with 3.2.3 and a Queue, however the bug appears
to be harmless. Can the ExceptionHandler just ignore the Exception, or should it
perform some cleanup ?
Thanks and regards,
Andrew
View the original post :
http://www.jboss.org/index.html?module=bb&
I encountered the same problem, but wasn't able to see the ExceptionListener's
onException gets call when it happened. This was what I did:
1) in my MDBean to implement ExceptionListener
2) provide onException method
3) in the connection to setExceptionListener(this);
I must have missed somethi
Thanks for the infos here.
We have added an exceptionListener and that seems to have done the trick.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827597#3827597";>View
the original post
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827597>Reply
to the post
-
I'm running into the same issue.
In other threads, it looks like the suggestion was to re-initialize the connection
when you receive an exception to try to recover.
In my case, I have I have a temporary queue set up to receive a response from some
message (that is, the reply-to field in some mes
I am currently experiencing the same issue that lucas has, but I don't understand what
you're saying should be done. Are you suggesting we create an exception listener?
What would it listen for and what would it do when it gets a message?
http://www.jboss.org/index.html?module=bb&op=viewtopic&
javax.jms.Connection.setExceptionListener()
Regards,
Adrian
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825613#3825613";>View
the original post
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825613>Reply
to the post
--
18 matches
Mail list logo
