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 » Queue Manager strange behaviour

Post new topic  Reply to topic
 Queue Manager strange behaviour « View previous topic :: View next topic » 
Author Message
kordi
PostPosted: Wed Nov 04, 2015 6:40 am    Post subject: Queue Manager strange behaviour Reply with quote

Centurion

Joined: 28 May 2012
Posts: 146
Location: PL

Hi,

We have 7.5.0.4 QMGR installed on windows box. I noticed that every initiation queue has two opened input connections. That was strange because for each of initiation queue there was only one trigger monitor running.

After some time I had a problem with transmission queue. There was three process putting on the queue, but when I check them, these process came from receiver channels, which were stopped. This transmission queue is used only by one sender channel so no thing like that should have happened. We could not start sender channel because this xmitq was in use, we could not clear messages (neither clear nor get) from that queue either because queue was in use. No errors in logs, no FDC files. After stopping QMGR with -i flag, we could not start QMGR because there were processes which was still running. After killing them, we still couldn't start QMGR. Reboot fixed the situation, now every initq has only one connection.

Do you know what could case these problems? Maybe there were steps I didn't take but I should?

Thanks
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Nov 04, 2015 7:41 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Put and Get disable the init queue and see who complains.

Review the AMQERR logs and look for FDCs.

Other appropriate and normal MQ troubleshooting procedures.
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
kordi
PostPosted: Wed Nov 04, 2015 8:29 am    Post subject: Reply with quote

Centurion

Joined: 28 May 2012
Posts: 146
Location: PL

thanks mqjeff for your reply.

yep, that might be helpful.

Nothing in AMQERR and no FDC generated :/
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Nov 04, 2015 8:56 am    Post subject: Re: Queue Manager strange behaviour Reply with quote

Poobah

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

kordi wrote:

There was three process putting on the queue, but when I check them, these process came from receiver channels, which were stopped.

Please explain what your mean by
Quote:
these process came from receiver channels
. Do you mean that these processes had names like amqrmppa? What were the process names exactly?

kordi wrote:
After killing them, we still couldn't start QMGR.

Please be a bit more precise. Why couldn't you (re)start the qmgr? What errors did you observe?
_________________
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
kordi
PostPosted: Thu Nov 05, 2015 2:39 am    Post subject: Reply with quote

Centurion

Joined: 28 May 2012
Posts: 146
Location: PL

Sorry for my English.

Xmitq had 3 opened output count. When I check queue status
dis qs(xxx) type(handle) all
these 3 connections was coming from receiver channels.

That was pretty strange because only sender channel should put on transmission queue.

Unfortunately there is nothing in the logs regarding problems with starting Queue Manager. What I remember was message informing about mq processes still runing in the system preventing MQ from starting. Actually this happened to me few times before on different windows machines. That's why I don't like to install MQ on non unix servers.


I don't really understand 2 things:
1. Why each of my initqs had 2 connections from the relevant mq trigger monitor
2. Why xmitq had OPPROCS(3) whily only one sender channel was using it and this connections were not coming from this channel.

Anyway, that must be some internal MQ error because after restart everything went back to normal.

I found only one FDC file:
Code:

+-----------------------------------------------------------------------------+
|                                                                             |
| WebSphere MQ First Failure Symptom Report                                   |
| =========================================                                   |
|                                                                             |
| Date/Time         :- Wed November 04 2015 12:14:09 GMT Standard Time        |
| UTC Time          :- 1446639249.060000                                      |
| UTC Time Offset   :- 60 (GMT Daylight Time)                                 |
| Host Name         :- CDCS199571                                             |
| Operating System  :- Windows Server 2008 R2 Server Standard Edition, Build  |
|   7601: SP1                                                                 |
| PIDS              :- 5724H7220                                              |
| LVLS              :- 7.5.0.4                                                |
| Product Long Name :- WebSphere MQ for Windows                               |
| Vendor            :- IBM                                                    |
| Installation Path :- D:\Program Files\IBM\WebSphere MQ                      |
| Installation Name :- Installation1    (1)                                   |
| License Type      :- Production                                             |
| Probe Id          :- KN280050                                               |
| Application Name  :- MQM                                                    |
| Component         :- kqiDoFilterOnConn                                      |
| SCCS Info         :- F:\build\slot1\p750_P\src\lib\lqm\amqkgena.c,          |
| Line Number       :- 3038                                                   |
| Build Date        :- Aug  7 2014                                            |
| Build Level       :- p750-004-140807                                        |
| Build Type        :- IKAP - (Production)                                    |
| UserID            :- user12                                                 |
| Process Name      :- D:\Program Files\IBM\WebSphere MQ\bin\amqzlaa0.exe     |
| Addressing mode   :- 32-bit                                                 |
| Process           :- 00006472                                               |
| Thread            :- 00000007                                               |
| QueueManager      :- RITFT1                                                 |
| UserApp           :- FALSE                                                  |
| ConnId(1) IPCC    :- 836                                                    |
| ConnId(2) QM      :- 64                                                     |
| Last HQC          :- 2.5.5-9173108                                          |
| Last HSHMEMB      :- 1.1.1-6022040                                          |
| Major Errorcode   :- krcE_UNEXPECTED_ERROR                                  |
| Minor Errorcode   :- OK                                                     |
| Probe Type        :- INCORROUT                                              |
| Probe Severity    :- 2                                                      |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred.  |
| FDCSequenceNumber :- 0                                                      |
| Arith1            :- 536901649 20007811                                     |
|                                                                             |
+-----------------------------------------------------------------------------+
Back to top
View user's profile Send private message
Inisah
PostPosted: Thu Nov 05, 2015 2:54 am    Post subject: Reply with quote

Apprentice

Joined: 21 Mar 2014
Posts: 44

According to the FDC, this requires a patching to 7.5.0.6
Please check the below link

http://www-01.ibm.com/support/docview.wss?uid=swg1IV67952
Back to top
View user's profile Send private message
kordi
PostPosted: Thu Nov 05, 2015 2:40 pm    Post subject: Reply with quote

Centurion

Joined: 28 May 2012
Posts: 146
Location: PL

Yes, indeed, thanks Inisah. I wonder why I could not find it googling with probe id of FDC.
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 » Queue Manager strange behaviour
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.