| Author |
Message
|
| harish225 |
 Posted: Fri Nov 18, 2016 7:39 pm Post subject: IBM MQ |
 |
|
Newbie
Joined: 18 Nov 2016
Posts: 8
|
HI,
I am faceing an issue with one of the client application. There is a connection drop between the application and QMGR.
In qmgr error logs we are getting AMQ9209 errors.
At application side we are getting mqrc 2009 error.
If application team restart their application. They are able to connect again.
After a few hour's again their is a connection drop between application and server. This is happening atleast 4 -5 time in a day.
Kindly Help me on this |
|
| Back to top |
|
 |
| tczielke |
| Posted: Sat Nov 19, 2016 5:52 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
A 2009 is a broken connection. I would recommend asking the application team what are their application requirements for handling a broken connection. If their application is not supporting this, they are probably missing an important requirement (handling broken connections), and they should open a defect against their application to correct this.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| harish225 |
| Posted: Mon Nov 21, 2016 10:18 pm Post subject: AMQ9209 |
|
|
Newbie
Joined: 18 Nov 2016
Posts: 8
|
we take configuration backup from a qmgr running in windows.
It is running in v7.0.1.13
We restored that qmgr configuration to AIX, In AIX it is running in v8.0.0.4.
Same application used to connect windows qmgr. Now they shifted or pointed their connection to aix qmgr.
Does it cause any connectivity issues?
Do i want to recreate SVRCONN and listener object's?
But SDR and RCVR is running properly, no connectivity issues with them.
Client application C++ application.
At client side MQ version is v7.0.0.0 |
|
| Back to top |
|
|
| harish225 |
| Posted: Mon Nov 21, 2016 10:59 pm Post subject: |
|
|
Newbie
Joined: 18 Nov 2016
Posts: 8
|
| tczielke wrote: |
| A 2009 is a broken connection. I would recommend asking the application team what are their application requirements for handling a broken connection. If their application is not supporting this, they are probably missing an important requirement (handling broken connections), and they should open a defect against their application to correct this. |
we take configuration backup from a qmgr running in windows.
It is running in v7.0.1.13
We restored that qmgr configuration to AIX, In AIX it is running in v8.0.0.4.
Same application used to connect windows qmgr. Now they shifted or pointed their connection to aix qmgr.
Does it cause any connectivity issues?
Do i want to recreate SVRCONN and listener object's?
But SDR and RCVR is running properly, no connectivity issues with them.
Client application C++ application.
At client side MQ version is v7.0.0.0 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 21, 2016 11:52 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The security model in MQ changed a huge amount between 7.0.1.3 and 8.0.0.4.
You can't just restore the save config and expect it to work OOTB.
There are many posts here (and in other places) that cover the sort of things you need to do.
For example, I googled for
| Quote: |
morags backstop rule
|
Morag has a series of posts on how to setup MQ 8 so that you can use existing (i.e. older clients) with the new/upgraded qmgr.
Take some time to try to understand the new security model and what you need to do to make the OOTB MQ8 work as before.
Do some testing, look at the MQ Logs and places like this for the reasons why your client connection is not working. fix that issue and move forward.
It will be a useful learning exercise.
Don't forget to document what you did. Also do all the changes via scripts.
Then you can properly configure your new QMGR in a supportable way.
Also, get the clients upgraded to at very least, the final FixPack for V7.0.0. Preferably, upgrade them to V8.0.0.4 (or later)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Mangesh1187 |
| Posted: Fri Dec 09, 2016 9:31 pm Post subject: |
|
|
Centurion
Joined: 23 Mar 2013
Posts: 116
|
Harish225 ,
Does your problem solved ? If yes please share the actions you have taken.
It will be helpful for others (including me )
Thanks |
|
| Back to top |
|
|
| harish225 |
| Posted: Mon Dec 12, 2016 9:08 pm Post subject: AMQ9209 |
|
|
Newbie
Joined: 18 Nov 2016
Posts: 8
|
Mangesh1187,
yes it is resolved. Their is network timeout on firewall at remote side. It is approximately 3600 sec(1 hour). If there are no message flows with in the time out. Then firewall terminate the idle connections. |
|
| Back to top |
|
|
|
|
