[esb-issues] [JBoss JIRA] Commented: (JBESB-1456) Load balancing over JMS - interresting behaviour

[Kevin Conner (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1456?page=comments#action_12394163 ] 
            
Kevin Conner commented on JBESB-1456:
-------------------------------------

This is not a bug but a request to extend the documentation covering load balancing and clustered JMS queues.

The issue is that the setup described in the original report used a clustered queue to cover the services on both nodes
and therefore no (ESB) load balancing was performed over the registered ESB services.  As this was a single (logical)
queue the load balancing was handled by the JMS layer.


> Load balancing over JMS - interresting behaviour
> ------------------------------------------------
>
>                 Key: JBESB-1456
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1456
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: 4.2.1
>         Environment: SOA-P 4.2.0 beta 1
>            Reporter: Martin Vecera
>            Priority: Minor
>
> During failover testing I found out very interresting behaviour...
> I had two nodes (JBossESB servers) in a cluster.
> I deployed identical service to both of them. Each service had:
> 1) clustered gateway queue served by 2 threads
> 2) clustered queue for ESB aware messages served by 2 threads.
> I send several messages to the first node and expected them to be load balanced among the nodes. This didn't happend.
> I figured out that the load balancing came in to the play twice:
> 1) while sending the message to GW
> 2) while sending the message from GW to ESB-aware queue
> Because there were more than one thread for each queue the loadbalancing went in the way where some messages were really sent to the GW on the second node but then they returned back to the first one.
> This is definitely configuration failure (the queue for ESB aware messages mustn't be clustered) but we should document this I think.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira