| Author |
Message |
 Topic: dspmq output changed without qmgr being started |
gbarber
Replies: 2
Views: 5883
|
 Forum: General Discussion Posted: Mon Jan 31, 2022 9:11 am Subject: dspmq output changed without qmgr being started |
| I found out that some of the filesystems were recovered from backups that were taken weeks ago (a time when the qmanager was running). I didn't think the filesystems affected contained any MQ related ... |
| Topic: dspmq output changed without qmgr being started |
gbarber
Replies: 2
Views: 5883
|
Forum: General Discussion Posted: Fri Jan 28, 2022 1:33 pm Subject: dspmq output changed without qmgr being started |
I shutdown my V9.1.0.3 queue manager using endmqm <qmgr>
After that the dspmq output showed "STATUS(Ended normally)"
After my server administrator did some work I logged in again t ... |
| Topic: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
gbarber
Replies: 9
Views: 9333
|
Forum: General IBM MQ Support Posted: Mon Mar 23, 2020 8:20 am Subject: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
Also why is a DURABLE subscription on the SYSTEM.JMS.ND.* queue ? Do they not have any of the SYSTEM.JMS.D.* queues defined for durable subscriptions? 
Right, that's one of the puzzling t ... |
| Topic: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
gbarber
Replies: 9
Views: 9333
|
Forum: General IBM MQ Support Posted: Fri Mar 20, 2020 6:47 am Subject: Re: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
V9 JMS client subscriptions dont show up as DURABLE so there is no risk of leaving orphans there.
The JMS Client at V9 will use MQSUB - unless you deliberately tell it to use the back-level ProviderV ... |
| Topic: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
gbarber
Replies: 9
Views: 9333
|
Forum: General IBM MQ Support Posted: Thu Mar 19, 2020 11:39 am Subject: Re: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
Here is a subscription from a JMS app, which disappears as soon as the subscribing application is killed with the -9 option
AMQ8096I: IBM MQ subscription inquired.
SUBID(414D512053545247573031202 ... |
| Topic: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
gbarber
Replies: 9
Views: 9333
|
Forum: General IBM MQ Support Posted: Wed Mar 18, 2020 8:46 am Subject: Re: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
I'm looking for a way to change the default subscription so that it does not show up as DURABLE(YES)
ALTER for a SUB doesn't seem to support changing the DURABLE attribute.
Are your subscriptions th ... |
| Topic: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
gbarber
Replies: 9
Views: 9333
|
Forum: General IBM MQ Support Posted: Tue Mar 17, 2020 1:23 pm Subject: Change SYSTEM.DEFAULT.SUB to be DURABLE(NO)? |
I have a V9.1.0.2 MQ installation on RHEL with PUBSUB enabled in the QM
My V6 JMS client subscriptions show up as DURABLE(YES), but don't behave that way (as evidenced by kill -9 of the clients not l ... |
| Topic: V6.0 JMS Client subscriber receiving corrupt message |
gbarber
Replies: 7
Views: 8408
|
Forum: General IBM MQ Support Posted: Tue Mar 17, 2020 1:14 pm Subject: CLOSED: IBM acknowledged this as being a bug |
IBM support indicated that this would be resolved in 9.1.0.6
They also indicated that the bug only manifests if the qm.ini has
MQIBindType=FASTPATH |
| Topic: V6.0 JMS Client subscriber receiving corrupt message |
gbarber
Replies: 7
Views: 8408
|
Forum: General IBM MQ Support Posted: Fri Jan 17, 2020 7:06 am Subject: V6.0 JMS Client subscriber receiving corrupt message |
| We're unable to upgrade our JMS clients at this time so we need to deal with the problem at hand. Based on IBMs compatibility documentation the V6 client is supported with V9.1 QM so this should defi ... |
| Topic: V6.0 JMS Client subscriber receiving corrupt message |
gbarber
Replies: 7
Views: 8408
|
Forum: General IBM MQ Support Posted: Thu Jan 16, 2020 1:37 pm Subject: V6.0 JMS Client subscriber receiving corrupt message |
New to the site and think we have a doozy on our hands.
We have a V9.1 QM With PSMODE(ENABLED)
We have a publisher publishing an XML message containing a large (>260KB) base64 encoded string. ... |
