| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Server sends RST - client server connection |
« View previous topic :: View next topic » |
| Author |
Message
|
| elikatz |
 Posted: Tue Feb 24, 2009 4:38 pm Post subject: Server sends RST - client server connection |
 |
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
Hi all,
I have an issue with external client (I don't have access to his code) connecting to our MQ server.
Here are the details:
MQ version 5.3 CSD 11 install on windows 2003 server cluster.
The client connects to server connection channel with the defaults (I didn't change anything).
The disconnections are inconsistent but the scenario is similar, we did TCPDUMP from both ends and got these results:
From client side ->
Send SYN (16384)
Send SYN (5840)
Get SYN, ACK (16384)
Send ACK (5840)
Send INITAIL_DATA (MQ)
Get RST
From sever side ->
Get SYN (16384)
Get SYN (5840)
Send ACK, SYN (16384)
Get ACK (5840)
Send RST
Get PSH, ACK (5840) with data -> [Packet size limited during capture: JXTA truncated]
Send RST
On the sever side we see no error at all!
One more thing -> on client side there is no disconnect interval, on sever side the HeartBeat interval set to 300.
I hope it's not too much information but I'm struggling with this issue for a long time..
Thanks in advance,
Eli |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Tue Feb 24, 2009 5:57 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Run MQ trace on the server side and ask the external client to do so too. As soon as you get an unexpected disconnection, stop the trace. The trace will show more of what is going on.
_________________
Glenn |
|
| Back to top |
|
|
| elikatz |
| Posted: Tue Feb 24, 2009 7:37 pm Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
Hi, thanks for the fast response.
The problem with trace on window server is that it can't be done on channel level but on queue manager level.
This MQ server is vey busy so there is a lot of traffic and trace files will be huge. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Feb 25, 2009 3:57 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| elikatz wrote: |
Hi, thanks for the fast response.
The problem with trace on window server is that it can't be done on channel level but on queue manager level.
This MQ server is vey busy so there is a lot of traffic and trace files will be huge. |
Yep, so only run trace as long as you need to capture the event. Disk space is cheap... Just watch the disk usage while the trace is running. If looks like its going to fill the disk, stop the trace.
There may be some impact to application response times, but generally this is minimal, they may not even notice anything unusual.
_________________
Glenn |
|
| Back to top |
|
|
| elikatz |
| Posted: Thu Feb 26, 2009 4:19 pm Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
My main issue with this is the disconnection are not consistent at all and since this is production server I can't just run the trace, the disk will die...
It's windows server so it's very hard to deal with this trace.
I'm still trying figure what can cause this issue. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 26, 2009 4:30 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
Let me summarize: you are running an out-of-support version of MQ, you apparently have very limited disk space, and you cannot do any tracing.
| Quote: |
| I'm still trying figure what can cause this issue. |
I'd suggest starting with the low-hanging fruit: get more disk space, then do a trace.
Since you (or your management) have ruled out any rational methodology for doing problem-determination, I'm not optimistic that you can actually figure out what the underlying problem is.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Feb 26, 2009 7:24 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Inconsistent disconnections could be due to a network or TCP/IP stack problem, causing dropped packets or dropped sessions. Get the networking folk involved. It could be a dodgy switch or router. Is the windows server 100% cpu bound, disk i/o bound, network bound or memory bound?
_________________
Glenn |
|
| 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
|
|
|
|
