| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ with Inlab Balance load balancing software |
« View previous topic :: View next topic » |
| Author |
Message
|
| Joe P |
 Posted: Fri Jul 25, 2008 2:39 am Post subject: MQ with Inlab Balance load balancing software |
 |
|
Newbie
Joined: 25 Jul 2008
Posts: 2
|
Hi,
I'm supporting a configuration where we have an MQ 6.0.2.2 client -> server connection over a WAN, and the TCP connection between the two is forward proxied at the client end using Inlab's Balance load balancing software (v3.11). We use the non-JMS MQ client libraries in Java.
A problem has arisen in that Balance seems to have an issue when posting larger messages. At anything over about 500kB, the client and server both report that the connection is broken mid-transfer, and network snooping suggests that Balance is causing the problem.
So my question is whether anyone has deployed MQ with Balance in a similar way, and if so, whether they saw similar issues with larger messages? We have no issues with Balance proxying other protocols. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jul 25, 2008 8:01 am Post subject: Re: MQ with Inlab Balance load balancing software |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Joe P wrote: |
Hi,
I'm supporting a configuration where we have an MQ 6.0.2.2 client -> server connection over a WAN, and the TCP connection between the two is forward proxied at the client end using Inlab's Balance load balancing software (v3.11). We use the non-JMS MQ client libraries in Java.
A problem has arisen in that Balance seems to have an issue when posting larger messages. At anything over about 500kB, the client and server both report that the connection is broken mid-transfer, and network snooping suggests that Balance is causing the problem.
So my question is whether anyone has deployed MQ with Balance in a similar way, and if so, whether they saw similar issues with larger messages? We have no issues with Balance proxying other protocols. |
Your problem is that your load balancer needs to be session aware.
Your MQ session is open the first time you connect to the qmgr until you disconnect. Completely different from http balancing where each request could be balanced...
Now you can use an MQ channel table to that effect but it will not provide you with load balancing. The channel table should provide you with a failover connection.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 25, 2008 9:32 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If you're willing to upgrade to MQ 7.0, you can get load balancing via the client channel tables and give that load balancer the boot.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Jul 25, 2008 10:28 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| PeterPotkay wrote: |
| If you're willing to upgrade to MQ 7.0, you can get load balancing via the client channel tables and give that load balancer the boot. |
uhm... the way I understood it... it's 'weighted' connecting based on a randomiser, not actually taking into account the 'balance' of the server...
so if you are really 'unlucky' all connections could still end up on the same server... 
(granted... it's beter than todays 'no choice at all' )
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 25, 2008 1:22 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The never got into the internals of this at the conf, unless you had some sidebar discusions?
If you weight 2 channels in the table equally I have to assume you would get a 50/50 distribution of connection attempts between the 2 destination servers, no?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Joe P |
| Posted: Wed Jul 30, 2008 12:52 am Post subject: |
|
|
Newbie
Joined: 25 Jul 2008
Posts: 2
|
Hi, thanks for your comments and apologies for my delay in replying.
I was not sufficiently precise in my description of the scenario. We are not actually load balancing here - there is only one server to which we connect. Thus the load balancing software is only used as a TCP proxy, for security reasons; it terminates the TCP connection from the client and establishes a new one, from a new address and port (a step further than simple NAT). And for no good reason, Balance then drops that connection.
My current thoughts are that it could be a protocol compatibililty problem, though intuitively that seems unlikely. Any relevant experience welcome. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
