Hi everyone,
I have JBoss 3.2.3 in production over two servers. I've been having intermittent
cache invalidation problems ever since we deployed. An example is an update to an
entity bean in Server A is occasionally not reflected in Server B.
The situation improved when we optimized the appli
Excellent. I see now why the ManagedConnections do not get flushed from the pool on a
ConnectionError.
Thanks all again.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840381#3840381
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&
Thanks Ulf for the tip. It wasn't directly applicable as I am using JMS which doesn't
have any relations to jdbc and ExceptionSorter. However, it pointed me in the right
direction.
I've solved this problem using the following approach:
1. The problem is that the JmsManagedConnection does not
I'm using JMS with HAIL and XA on JBoss 3.2.3, which seems uncommon from the posts I
see. I have a clustered configuration (2 servers), and need to send JMS Messages
transactionally with the container-managed transactions. I need to send the JMS
Message to the singleton JMS Server (which in 3.