BTW, some instances of this exception are accompanied by message delivery
failures:
2009-10-06 12:42:20,704 WARN [org.jboss.jms.client.container.ClientConsumer]
Timed out waiting for last delivery 1 got 0
| 2009-10-06 12:42:20,709 ERROR
[org.jboss.jms.client.container.ClosedInterceptor]
Clo
Hi!
After migrating from JBoss MQ to JBoss Messaging (which also required deploying
the relevant queues manually), our installation of jBPM-BPEL has started
throwing the following exception in the logs:
2009-10-01 12:51:46,648 ERROR
[org.jboss.jms.client.container.ClosedInterceptor]
ClosedIn
Could you share what was the problem and how did yo fix it?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257887#4257887
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257887
___
OK, I've found the solution to my problem.
First, it wasn't in the configuration of the TreeCache itself, but of the
Hibernate Cache provider.
It turns out that this behaviour is by design the default in the Hibernate
JBoss Cache provider (hibernate-jbc-cacheprovider-1.0.1.GA.jar).
See:
http:
What's very curious is the fact that logs on both cluster nodes indicate that
the elements are added to the cache. E.g., after the BPEL process is executed
and transaction gets committed:
node 1 (initiator):
| 2009-09-22 15:56:04,686 DEBUG
[org.jboss.cache.eviction.BaseEvictionAlgorithm] Ad
BTW, anticipating th question: I can see that indeed the cache cluster gets
formed, I can see the IP addresses of all the members in the "Members"
attribute of the TreeCache MBean, the list of node IP addresses and their ports
is identical on all cluster members.
Only one of all the cluster nod
Hi!
I have a clustered TreeCache set up on the standard JBoss 4.2.2 GA release (for
caching jBPM-BPEL data).
It seems that the contents of the cache are properly replicated only during the
initial state transfer - when a node joins the cluster, the logs show:
2009-09-18 13:44:41,932 INFO [org
