[JBoss Tools (users)] - Re: ganymede and jboss tool 3 problem with seam projet
by meissa
Max,
It makes a BIG difference when you say that you can't reproduce what i've described while using seam 2.0
In fact we were not completely synchronized (please be patient i'll explain all).
I've been searching and deeply testing these last three days and I'm happy because all my troubles are gone :-))
To be short:
Everything works fine with JBT 3 RC1, Seam 2.0, and eclipse Ganymede with WTP 3.0.3
Everything also works fine with JBT 3 RC1, Seam 2.1.1 GA (yes, the last one), eclipse Ganymede with WTP 3.0.3
Here are the two combinations that works perfectly with Seam project.
While you were testing seam 2.0 with ganymede and WTP 3.0.3 I was using seam 2.1.RC1. That's the reason why we were not able to produce the same results.
I think that these two working combinations should be described somewhere to prevent users from loosing times doing what I did ...
In any case, I'm thanking you for the time you spent for solving this problem.
Meissa
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198710#4198710
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198710
15 years, 5 months
[JBoss Messaging] - Cluster messaging distribution
by rana24
I have gone through most of the past post on the same topic still there is one unanswered question.
We have a clustered set up for JBM-1.4.0 SP3 with JAS-4.2.1 , two instance A n B are part of the cluster.
We have a test client which inside a for loop does follwing.
| QueueConnectionFactory qcf = (QueueConnectionFactory) cntxt
| .lookup("/ClusteredConnectionFactory");
|
| Queue queue = (Queue) cntxt.lookup("queue/RequestQueue");
| QueueConnection qc = qcf.createQueueConnection();
| QueueSession qs = qc.createQueueSession(false,
| Session.AUTO_ACKNOWLEDGE);
| QueueSender queueSender = qs.createSender(queue);
| ObjectMessage msg = qs.createObjectMessage(batchId);
| queueSender.send(msg);
|
Here we are using HA-JNDI for lookup.
We are using default ClusterredConnectionFactory which has ,
| <attribute name="SupportsFailover">true</attribute>
| <attribute name="SupportsLoadBalancing">true</attribute>
| <attribute name="LoadBalancingFactory">org.jboss.jms.client.plugin.RoundRobinLoadBalancingFactory</attribute>
|
For RequestQueue is set to Cluster TRUE in destination-service.xml.
As per our expectation messages should be distributed in round robin fashion , We have around 80% results when it is not distributed in round robbin fashion.
Is there any other attribute which controls distribution ?
For some cases it goes to one server only.
Our client runs on different server so A and B both are remote server for client.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198705#4198705
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4198705
15 years, 5 months