| Author |
Message
|
| gqmallah |
 Posted: Tue Apr 03, 2007 7:09 am Post subject: Websphere MQ Explorer Ver 5.3 Problem |
 |
|
Newbie
Joined: 03 Apr 2007
Posts: 8
|
Dear All,
I am facing one problem in Websphere MQ version 5.3. Two Servers are installed Webspere MQ Series Version 5.3. They are sharing QUEUE MANAGERS also. Queue Managers and queues are created using MQ Explorer. When I close Webspere MQ Explorer I see all remote clustered Queue Manager's status become unavailable and not connected when I just select that particular Queue Manager it automatically changes its status to Available and Connected.
Could any body let me know how can we fix this problem where on closure of MQ Explorer each time Remote (clustered) Queue Managers become unavailable and this affect the flow of messages.
Thanks
Ghulam |
|
| Back to top |
|
 |
| gqmallah |
| Posted: Tue Apr 03, 2007 7:11 am Post subject: |
|
|
Newbie
Joined: 03 Apr 2007
Posts: 8
|
| Please Note: I am using Windows Server 2003 platform for Websphere MQ Version 5.3 |
|
| Back to top |
|
|
| tleichen |
| Posted: Wed Apr 04, 2007 6:22 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
If you're closing MQ Explorer, then where are you "seeing" these statuses? 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| gqmallah |
| Posted: Wed Apr 04, 2007 6:26 am Post subject: |
|
|
Newbie
Joined: 03 Apr 2007
Posts: 8
|
| After again starting Webpshere MQ Explorer. When I start it I see QMANAGERS status is unavailable and just when select that qmanager it become in running status. During its unavailbility our other companents fail to transfer messages to the unavailable qmanager. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 04, 2007 6:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Question - how does a problem with Explorer affect the flow of messages between queue managers? 
Am I missing something really obvious here?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tleichen |
| Posted: Wed Apr 04, 2007 6:33 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
I think what you are seeing is simply a residual effect in the way MQ Explorer is designed. I think it is putting up statuses before it determines what the true statuses are. Thus, the queue managers appear to be going unavailable, but I think you will find that, in reality, they are not. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| gqmallah |
| Posted: Wed Apr 04, 2007 6:34 am Post subject: |
|
|
Newbie
Joined: 03 Apr 2007
Posts: 8
|
| We have two servers over the network. Both servers have installed MQ version 5.3. They are sharing the Queue Managers. On one server when MQ Explorer is closed no messages are going through the managers and we see nothing on the target server. But when we start MQ explorer we initial see status is unavailable when we just select that remote queue manager it autoamtically shows RUNNING status. After this when we perform any transaction its arrived at other end. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 04, 2007 6:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gqmallah wrote: |
| We have two servers over the network. Both servers have installed MQ version 5.3. They are sharing the Queue Managers. On one server when MQ Explorer is closed no messages are going through the managers and we see nothing on the target server. But when we start MQ explorer we initial see status is unavailable when we just select that remote queue manager it autoamtically shows RUNNING status. After this when we perform any transaction its arrived at other end. |
In theory at least, the Explorer is an administration tool that has no direct effect on the queue managers it administers. You don't say what platform the queue managers are running on, but if they're running on Windows are they running on the same server as you're running Explorer? If so, are the MQ services running as the logged on user so when you close Exploter and sign out, the services stop?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gqmallah |
| Posted: Wed Apr 04, 2007 6:49 am Post subject: |
|
|
Newbie
Joined: 03 Apr 2007
Posts: 8
|
Yes MQ services are running as the system account. When we close the MQ Explorer. That service does not go down, it keep continue to run. We are using Windows Server 2003 in all servers.
Further more could you please let me know about the PDF's about WebSphere MQ Series V5.3 System Administratio or all other documents for Windows. Many thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 04, 2007 6:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gqmallah wrote: |
| Yes MQ services are running as the system account. When we close the MQ Explorer. That service does not go down, it keep continue to run. We are using Windows Server 2003 in all servers. |
If the service continues to run, what does the queue manager log give as the reason for it closing?
| gqmallah wrote: |
Further more could you please let me know about the PDF's about WebSphere MQ Series V5.3 System Administratio or all other documents for Windows. Many thanks |
What about them? They're on your install media and on the IBM website. Also available as an online info centre. Links available from the documentation button at the top of this page and many, many posts in this forum.
Or were you asking a different question about the PDFs??
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gqmallah |
| Posted: Wed Apr 04, 2007 6:55 am Post subject: |
|
|
Newbie
Joined: 03 Apr 2007
Posts: 8
|
| Sorry for supplementry question. Could you please help in getting my problem resolved? Why QMANAGER status is going to be unavailable and all transactions halts until I start the MQ Explorer and jusy select the repctive Queue Manager. |
|
| Back to top |
|
|
| gqmallah |
| Posted: Wed Apr 04, 2007 7:01 am Post subject: |
|
|
Newbie
Joined: 03 Apr 2007
Posts: 8
|
| In the log files of MQ it does not add any information about this problem. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 04, 2007 7:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gqmallah wrote: |
| Sorry for supplementry question. |
Supplementary question is fine. I just didn't understand what you were asking 
| gqmallah wrote: |
Could you please help in getting my problem resolved? Why QMANAGER status is going to be unavailable and all transactions halts until I start the MQ Explorer and jusy select the repctive Queue Manager. |
There should be a logical separation between Explorer and the queue manager(s) in it's view. If the queue manager and it's attendent services are shutting down when Explorer closes this is a configuration issue. The log should contain information about why the queue manager and/or the listener is closing.
Check again that the MQ services are set to run as mqm and are automatic. Check that the queue manager and component services are set as automatic. Check the log files for the time in question to see what's closing the services and/or why message flow is being interupted.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 04, 2007 7:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gqmallah wrote: |
| In the log files of MQ it does not add any information about this problem. |
It should at least contain an informatory note that the queue manager is stopping, and another when it's starting. If neither are present, the queue manager is not changing status when Explorer is closed and you have a different problem than the one you think you have. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 04, 2007 7:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Let's be a bit clear about what we mean by "log files".
On Windows, you should be looking at the Event Viewer in the Application log for events related to WebSphere MQ.
There will also be error log files in both <product-install>/errors and <product-install>/qmgrs/<queue manager>/errors.
You should not be looking at anything in <product-install>/log
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
