ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Configuration of 2 MQ clients at a single SERVCONN channel

Post new topic  Reply to topic
 Configuration of 2 MQ clients at a single SERVCONN channel « View previous topic :: View next topic » 
Author Message
syed.basha
PostPosted: Wed Jul 06, 2016 1:32 am    Post subject: Configuration of 2 MQ clients at a single SERVCONN channel Reply with quote

Newbie

Joined: 06 Jul 2016
Posts: 3

Good Day!

I am facing an issue after the configuration of the 2 MQ client which use the same SERVCONN channel to communicate to a single remote Queue manager. Please find below for the more details regarding the issue,

1. Application is working fine when it is continuously active. (ie), the transactions to and fro between the MQ client and MQ server is active. But, after some particular interval of idle time of the application, we are facing challenge in doing the transactions. We had to kill the threads and again start the threads in order to perform the transaction.

I could see the following error messages in the qmgr error logs,

"AMQ9999: Channel 'CHANEL_1' to host 'AppServer' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(4764) for channel 'CHANEL_1'
ended abnormally. The host name is 'AppServer'; in some
cases the host name cannot be determined and so is shown as '????'."


Please help in troubleshooting the above. The expectation is that the channel should be always active and the application needs to have maximum availability..

Thanks in advance!
Back to top
View user's profile Send private message
exerk
PostPosted: Wed Jul 06, 2016 2:17 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Is there a firewall killing the connection after a certain length of time?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
hughson
PostPosted: Wed Jul 06, 2016 3:10 pm    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand

syed.basha wrote:
The expectation is that the channel should be always active and the application needs to have maximum availability.

The most important thing to understand first about a SVRCONN channel is that it is only active when the application that uses it is connected. If the application disconnects, then the SVRCONN channel will end. I don't think that is your problem today, but it is an important point to remember.

Now to your error situation. You have provided us with a snippet from your queue manager error log, thus:

syed.basha wrote:
AMQ9999: Channel 'CHANEL_1' to host 'AppServer' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(4764) for channel 'CHANEL_1'
ended abnormally. The host name is 'AppServer'; in some
cases the host name cannot be determined and so is shown as '????'.

This is not the whole error message. Just after your snippet there is the following:
Rest of message AMQ9999 wrote:
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure.

You see the thing about message AMQ9999 is that it is always accompanied by another message just before it which gives the detailed reason why the channel ended abnormally. Please can you take a look and supply that error message for us to see, and thus help you. There are many reasons why a SVRCONN channel might end abnormally, and without seeing the error message, we would just be guessing, and that doesn't help you.

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
syed.basha
PostPosted: Mon Jul 11, 2016 6:35 am    Post subject: Reply with quote

Newbie

Joined: 06 Jul 2016
Posts: 3

Thanks for your inputs Morag.

Please refer below for complete MQ server logs,


6/29/2016 19:49:39 - Process(4252.3) User(MUSR_MQADMIN) Program(amqzmur0.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ6287: WebSphere MQ V7.5.0.3 (p750-003-140123).

EXPLANATION:
WebSphere MQ system information:
Host Info :- Windows Server 2008 R2 Server Enterprise Edition, Build
7601: SP1 (MQ Windows 32-bit)
Installation :- C:\Program Files (x86)\IBM\WebSphere MQ (Installation1)
Version :- 7.5.0.3 (p750-003-140123)
ACTION:
None.
-------------------------------------------------------------------------------
6/29/2016 19:49:39 - Process(4624.291) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(4764) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/29/2016 20:10:27 - Process(4624.267) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9208: Error on receive from host pathfin01 (172.17.137.121).

EXPLANATION:
An error occurred receiving data from pathfin01 (172.17.137.121) over
TCP/IP. This may be due to a communications failure.
ACTION:
The return code from the TCP/IP recv() call was 10054 (X'2746'). Record these
values and tell the systems administrator.
----- amqccita.c : 3874 -------------------------------------------------------
6/29/2016 20:10:27 - Process(4624.267) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host 'pathfin01 (172.17.137.121)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(5748) for channel 'CHANEL_1'
ended abnormally. The host name is 'pathfin01 (172.17.137.121)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/29/2016 20:14:40 - Process(4624.261) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9208: Error on receive from host pathfin02 (172.17.137.122).

EXPLANATION:
An error occurred receiving data from pathfin02 (172.17.137.122) over
TCP/IP. This may be due to a communications failure.
ACTION:
The return code from the TCP/IP recv() call was 10054 (X'2746'). Record these
values and tell the systems administrator.
----- amqccita.c : 3874 -------------------------------------------------------
6/29/2016 20:14:40 - Process(4624.261) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host 'pathfin02 (172.17.137.122)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(5348) for channel 'CHANEL_1'
ended abnormally. The host name is 'pathfin02 (172.17.137.122)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/29/2016 20:35:44 - Process(4624.294) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/29/2016 20:35:44 - Process(4624.294) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(6276) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/30/2016 15:23:12 - Process(4624.320) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/30/2016 15:23:12 - Process(4624.320) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(6172) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/30/2016 15:28:12 - Process(4624.324) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/30/2016 15:28:12 - Process(4624.324) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(5944) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/30/2016 19:36:43 - Process(4624.317) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/30/2016 19:36:43 - Process(4624.317) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(6488) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/30/2016 19:58:44 - Process(4624.367) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/30/2016 19:58:44 - Process(4624.367) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(6884) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/30/2016 20:08:31 - Process(4624.406) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/30/2016 20:08:31 - Process(4624.406) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(7092) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/30/2016 21:48:49 - Process(4624.326) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/30/2016 21:48:49 - Process(4624.326) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(3184) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.
----- amqrmrsa.c : 898 --------------------------------------------------------
6/30/2016 21:48:49 - Process(4624.322) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.
----- amqccita.c : 3911 -------------------------------------------------------
6/30/2016 21:48:49 - Process(4624.322) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9999: Channel 'CHANEL_1' to host '172.17.137.112 (172.17.137.112)' ended
abnormally.

EXPLANATION:
The channel program running under process ID 4624(6336) for channel 'CHANEL_1'
ended abnormally. The host name is '172.17.137.112 (172.17.137.112)'; in some
cases the host name cannot be determined and so is shown as '????'.
ACTION:
Look at previous error messages for the channel program in the error logs to
determine the cause of the failure. Note that this message can be excluded
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
found in the System Administration Guide.


It seem to be TCP connection drop out. Kindly suggest.

Thanks in advance[/quote][/list]
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Mon Jul 11, 2016 8:04 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1231
Location: Gold Coast of Florida, USA

exerk wrote:
Is there a firewall killing the connection after a certain length of time?

Talk to your firewall people.
Back to top
View user's profile Send private message AIM Address
Vitor
PostPosted: Mon Jul 11, 2016 9:08 am    Post subject: Re: Configuration of 2 MQ clients at a single SERVCONN chann Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

syed.basha wrote:
The expectation is that the channel should be always active


False expectation.

syed.basha wrote:
the application needs to have maximum availability..


Why isn't the application trying to recover from the connection issue, as all well-behaved and properly designed client applications should? Especially as v7.5 has features to assist with this.

Aside from that, I agree with my worthy associates. Talk to your network people about what's closing the inactive link and why.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Mon Jul 11, 2016 10:54 am    Post subject: Re: Configuration of 2 MQ clients at a single SERVCONN chann Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.

syed.basha wrote:
The expectation is that the channel should be always active ...

A SVRCONN channel instance is only active when an application is connected.
_________________
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
View user's profile Send private message
hughson
PostPosted: Mon Jul 11, 2016 3:52 pm    Post subject: Reply with quote

Padawan

Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand

So you appear to have two slightly different reported errors:-

syed.basha wrote:
6/29/2016 20:10:27 - Process(4624.267) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9208: Error on receive from host pathfin01 (172.17.137.121).

EXPLANATION:
An error occurred receiving data from pathfin01 (172.17.137.121) over
TCP/IP. This may be due to a communications failure.
ACTION:
The return code from the TCP/IP recv() call was 10054 (X'2746'). Record these
values and tell the systems administrator.


This one is reporting a break in connectivity with a Windows TCP/IP return code of 10054 (X'2746') WSAECONNRESET

Windows Sockets Error Codes wrote:
Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.


syed.basha wrote:
6/29/2016 20:35:44 - Process(4624.294) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(WEBMQ01) Installation(Installation1)
VRMF(7.5.0.3) QMgr(PFP01)

AMQ9209: Connection to host '172.17.137.112 (172.17.137.112)' for channel
'CHANEL_1' closed.

EXPLANATION:
An error occurred receiving data from '172.17.137.112 (172.17.137.112)' over
TCP/IP. The connection to the remote host has unexpectedly terminated.

The channel name is 'CHANEL_1'; in some cases it cannot be determined and so is
shown as '????'.
ACTION:
Tell the systems administrator.


syed.basha wrote:
It seem to be TCP connection drop out. Kindly suggest.
Both these errors are reporting to you that the other end (that is the client end of the connection) has been unexpectedly closed. This can be something as simple as a <Ctrl>-<C> of the client application, or as has been suggested a firewall closing an inactive socket.

How long had the client application been running before this was seen. What is seen at client end?

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software
Back to top
View user's profile Send private message Visit poster's website
syed.basha
PostPosted: Tue Jul 12, 2016 1:37 am    Post subject: Reply with quote

Newbie

Joined: 06 Jul 2016
Posts: 3

Please find below an update on the issue,

Quote:

I had tested the application such that I am continuously performing the transactions through the application. It is approximately 1 hour after the application establishes the connection and is running, we are facing this connection drop out issue. Thus, It gives me an impression that connections are getting dropped after 1 hour even if they are active.

This issue is occurring even if only one client is active at a time. I have re-tested the



Environment related details of Application:

1. The MQ client is running in HP UX machine.
2. MQ server is configured as a MSCS cluster service(Active-Passive) and the MQ client will be connecting to the server through Cluster IP address. MQ server is running at Windows Machine.
3. The user request will through a web application which would put the messages in the MQ server queues and the MQ client listening to the queues will process the request in the HP UX machine and send back the response to the web application.

Issue description:

1. the Connection between the client and the server is getting killed exactly after 1 hour, even if the connections are active continuously.




[/list]
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Jul 12, 2016 3:40 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

syed.basha wrote:
the Connection between the client and the server is getting killed exactly after 1 hour, even if the connections are active continuously.

That's almost always an indicator of a firewall dropping connections it thinks are "too old".
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jul 12, 2016 5:15 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mqjeff wrote:
syed.basha wrote:
the Connection between the client and the server is getting killed exactly after 1 hour, even if the connections are active continuously.

That's almost always an indicator of a firewall dropping connections it thinks are "too old".




Speak to your network people.

Also speak to the application people. As I indicated above, a well behaved client application should always try to reconnect in the face of network issues (obviously it should give up at some point, but it should try to recover from transient errors). Even if you resolve what it deliberately closing the connection in this case, it's highly likely that at some future point you'll hit some kind of network issue that interferes with connectivity because sooner or later on every site there's a network issue that interferes with connectivity and the application should be coded to deal with that.

You may also find it's faster and easier to change the application to deal with this than get the network people to change their rules on "old" connections.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Configuration of 2 MQ clients at a single SERVCONN channel
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.