[JBoss Messaging Users] - JBoss Messaging 1.4.4.GA + JBoss AS 4.2.3.GA Compatibility
by jbo_jboss
I am seeking clarification that JBoss Messaging 1.4.4.GA and JBoss AS 4.2.3.GA are fully compatible and that client failover is fully operational with this combination.
I have a two node JBoss AS 4.2.3.GA cluster configured in accordance with the instructions in the JBoss Messaging 1.4.4.GA user guide. I also have an external Tomcat web server acting as a JMS client, also configured in accordance with the JBoss Messaging 1.4.4.GA user guide and using a copy of the jbossall-client.jar with the remoting classes stripped out to resolve the classpath ordering conflict that might otherwise occur.
The ConnectionFactory on the server that the client connects to is configured with both SupportsFailover and SupportsLoadBalancing set to true.
I believe I have everything configured correctly however I am not getting reliable failover behaviour.
So in the first instance I would be interested if anyone can confirm that they have this combination of versions working including transparent client failover. If so, we could then compare exact details to see what I might be getting wrong.
Thanks, James.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256407#4256407
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256407
16 years, 7 months
[JBoss Cache Users] - Re: JBoss 4.2.2 with TreeCache 1.4.1.SP5: nodes, attributes
by the_olo
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] Adding element /org/jbpm/graph/exe/ProcessInstance/org.jbpm.graph.exe.ProcessInstance#15967 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:04,686 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15969 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:04,686 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15971 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:04,686 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15972 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:04,686 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15973 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:04,686 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15974 for a node that doesn't exist yet. Process as an add.
|
node 2 (acceptor):
| 2009-09-22 15:56:03,536 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/ProcessInstance/org.jbpm.graph.exe.ProcessInstance#15967 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:03,536 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15969 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:03,536 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15971 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:03,536 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15972 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:03,536 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15973 for a node that doesn't exist yet. Process as an add.
| 2009-09-22 15:56:03,536 DEBUG [org.jboss.cache.eviction.BaseEvictionAlgorithm] Adding element /org/jbpm/graph/exe/Token/org.jbpm.graph.exe.Token#15974 for a node that doesn't exist yet. Process as an add.
|
The problem is that on node 2, the number of cache contents does not go up like it does on node 1. Cache contents on node 2 remain the same after the operation.
If I execute the same operation on node 2, then the execution goes as slow as on node 1 before it had populated its cache. Node 2's cache contents go up then, and reach the same level as on node 1.
So it looks like the caches of both nodes operate independently, regardless of what the logs say.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256404#4256404
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256404
16 years, 7 months