| Author |
Message
|
| tcsops |
 Posted: Tue Mar 18, 2008 1:32 pm Post subject: how to resolve cksum issue in mqseries |
 |
|
Newbie
Joined: 18 Mar 2008
Posts: 2
|
Dear Sir,
We are connecting our server ie., shscps02-fe.64326 > 57.60.46.7.ibm-mqseries via MQ series with port 1414.
While we enable the TCP dump we are seeing that cksum is saying that it is incorrect we are suspecting that due to this we are not able to receive any response from our client.
Please let us know if cksum is something going wrong here. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Mar 18, 2008 2:17 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| How are you connecting to this server? |
|
| Back to top |
|
|
| tcsops |
| Posted: Tue Mar 18, 2008 6:08 pm Post subject: how to resolve cksum issue in mqseries |
|
|
Newbie
Joined: 18 Mar 2008
Posts: 2
|
Both the Queue Managers are in cluster.
we are connecting to it by cluster. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 19, 2008 1:18 am Post subject: Re: how to resolve cksum issue in mqseries |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tcsops wrote: |
| we are connecting to it by cluster. |
You can't connect an application "by cluster" - you connect to a queue manager (which may participate in a cluster) either by binding or clienting. From the limited symptoms you describe I suspect the latter, and the queue manager's membership in a cluster is a red herring to your problem.
What MQ reason codes are you getting? Are you indeed using a client & if so how is the client configured? What version of WMQ are you using? On what platform?
Help us to help you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 19, 2008 3:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you are trying to solve an MQ problem using TCP dumps, you are trying too hard and doing the wrong thing.
If you aren't getting a reply message, it's almost certainly because you didn't do the right thing when sending the request message.
If you are getting an MQ error on the client - you wouldn't be using port 1414 if you weren't making a client connection - then you should use that to figure out what's going on.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
