Any ideas?
Is there any built-in facility/pattern to record a poisoned message along with
the exception it has caused and the destination it was last delivered to?
Sorry for bumping up the post.
Frank
View the original post :
gaohoward wrote : You can set the log level to TRACE and then you will see
the log record when it happens. Don't know if this is what you wanted.
Not quite. The exception in the log file I want to be recorded with the
message. The default behavior is to put the poisoned message into the DLQ.
Hi,
when a message is sent to the dead letter queue, because delivery failed too
many times, is the exception somewhere recorded that caused the failure?
Kind regards,
Frank
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4226313#4226313
Reply to the post :
alesj wrote :
| Ah, yes.
| I totally forgot about this change. :-(
| - https://jira.jboss.org/jira/browse/JBAS-5803
|
Hi Ales,
could you please update the sourceforge downloads?
I also ran into this problem and only did find this post by luck. I could have
spent days to figure that
eontech wrote :
| 1. Which connection factory to use so that JMS uses Container transaction?
Currently we are using /ConnectionFactory
|
java:/JmsXA
eontech wrote :
| 2. Do we need to open connection every time we send a message or we can
have a connection object initialized in post
From what I have understood from the documentation, you will get a distributed
messaging system as long the JBoss application server underneath is clustered.
So in this setup, you can in-queue a message in one node and out-queue this
message in another node.
But what if the two application
Hi,
is it possible to configure JBoss Messaging in a distributed way without
clustering the application server beneath? I mean, like a message bus?
If so, where can I find more information about this?
(I am referring to the JBM version that is shipped with JBoss AS 5.0)
Kindly appreciate your
