|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
client installation |
« View previous topic :: View next topic » |
Author |
Message
|
chris boehnke |
Posted: Mon Sep 14, 2009 2:20 pm Post subject: client installation |
|
|
 Partisan
Joined: 25 Jul 2006 Posts: 369
|
ALL,
We have MQ client version 6.0.0.0 on our AIX server. We are planning to apply latest fixpack MQ v6.0.2.7. We have applications on this server which use MQ client to connect to MQ queue managers on a different server.
When I do a ps -ef|grep mqm I don't see any mq processess running.
While applying the fix pack, do I need to ask the application team to stop their applications?
let me know your thoughts. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Sep 14, 2009 2:23 pm Post subject: Re: client installation |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
chris boehnke wrote: |
ALL,
We have MQ client version 6.0.0.0 on our AIX server. We are planning to apply latest fixpack MQ v6.0.2.7. We have applications on this server which use MQ client to connect to MQ queue managers on a different server.
When I do a ps -ef|grep mqm I don't see any mq processess running.
While applying the fix pack, do I need to ask the application team to stop their applications?
let me know your thoughts. |
Are you sure there is no java process running using the mq java libraries?
And I would not expect any of the client applications to be running under mqm...
Ask all applications using MQ to shutdown before upgrading.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mvic |
Posted: Mon Sep 14, 2009 2:51 pm Post subject: Re: client installation |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
chris boehnke wrote: |
When I do a ps -ef|grep mqm I don't see any mq processess running. |
How do you know this from the ps listing? For example a client app might be called "myclientapp". If you are grep-ing for mqm, then you won't match that program. Best to consult the application owners to find out the names of their processes. Alternatively if your OS allows you to find all processes that have loaded libmqmcs_r.a or libmqmcs.a (this is AIX, different file extension on other platforms), this could be a more reliable test. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Sep 15, 2009 5:42 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9470 Location: US: west coast, almost. Otherwise, enroute.
|
ps -ef | grep amq will display wmq internal processes. _________________ 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 |
|
 |
mvic |
Posted: Tue Sep 15, 2009 7:07 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
bruce2359 wrote: |
ps -ef | grep amq will display wmq internal processes. |
Don't forget runmqchl, runmqlsr, runmqchi, rcdmqimg, rcrmqobj, setmqaut, str..., dsp..., etc. etc. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Sep 15, 2009 12:34 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
mvic wrote: |
bruce2359 wrote: |
ps -ef | grep amq will display wmq internal processes. |
Don't forget runmqchl, runmqlsr, runmqchi, rcdmqimg, rcrmqobj, setmqaut, str..., dsp..., etc. etc. |
Back to Chris's question, I did not know that you considered those to be client processes. I would have thought of them as server processes.
As client processes you might particularly want to check for any client trigger monitor, as well as any application using MQ.
You will need to upgrade both the client trigger monitor and all MQ libraries (including java) installed on your machine...
The safest way is still to make sure all client applications on the machine shut down.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mvic |
Posted: Tue Sep 15, 2009 3:32 pm Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
fjb_saper wrote: |
mvic wrote: |
bruce2359 wrote: |
ps -ef | grep amq will display wmq internal processes. |
Don't forget runmqchl, runmqlsr, runmqchi, rcdmqimg, rcrmqobj, setmqaut, str..., dsp..., etc. etc. |
Back to Chris's question, I did not know that you considered those to be client processes. I would have thought of them as server processes. |
Good point. I wasn't claiming they were client processes, but was attempting to correct the previous statement.
Quote: |
As client processes you might particularly want to check for any client trigger monitor, as well as any application using MQ. |
All processes that have loaded anything from /opt/mqm will need to be closed down to allow the upgrade - client, server, whatever. |
|
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
|
|
|
|