| Author |
Message
|
| fjb_saper |
 Posted: Thu Jun 30, 2016 8:44 pm Post subject: FDC in TopicHost routed PUB SUB |
 |
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
What happened this used to work?
The environment: Windows 10 Home 64 bits, MQ 8004 and MQ8005 (did the upgrade) cmdlevel (800)
Cluster: PS1 through PS6, PS1 and PS2 are FR, PS4 and PS6 are topic hosts
Topic definition:
| Code: |
1 : dis topic(sports) all
AMQ8633: Display topic details.
TOPIC(SPORTS) TYPE(LOCAL)
TOPICSTR(Sports) DESCR( )
CLUSTER(CLS1) CLROUTE(TOPICHOST)
DURSUB(YES) PUB(ENABLED)
SUB(ENABLED) DEFPSIST(YES)
DEFPRTY(0) DEFPRESP(ASYNC)
ALTDATE(2016-06-30) ALTTIME(19.42.28)
PMSGDLV(ALL) NPMSGDLV(ALLAVAIL)
PUBSCOPE(ALL) SUBSCOPE(ALL)
PROXYSUB(FIRSTUSE) WILDCARD(PASSTHRU)
MDURMDL(SYSTEM.DURABLE.MODEL.QUEUE)
MNDURMDL(SYSTEM.NDURABLE.MODEL.QUEUE)
MCAST(ENABLED)
COMMINFO(SYSTEM.DEFAULT.COMMINFO.MULTICAST)
USEDLQ(YES) CUSTOM( ) |
PS5 subscribes to topicstr('Sports/Soccer')
Everything works fine if you publish on the TopicHost qmgr.
Now Publish on PS3 and PS5 is missing the message....
It is stuck on PS6 ( or PS4 ) in the SYSTEM.INTER.QMGR.PUBS queue and following FDC is being cut... As the process dies there is 0 ipprocs for that queue.
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu June 30 2016 22:27:48 Eastern Daylight Time |
| UTC Time :- 1467340068.293000 |
| UTC Time Offset :- 60 (Eastern Daylight Time) |
| Host Name :- FJS-HP |
| Operating System :- Windows 8 Unknown x64 Edition, Build 9200 |
| PIDS :- 5724H7251 |
| LVLS :- 8.0.0.5 |
| Product Long Name :- WebSphere MQ for Windows (x64 platform) |
| Vendor :- IBM |
| O/S Registered :- 1 |
| Data Path :- C:\MQ\Data |
| Installation Path :- C:\mq\mq8 |
| Installation Name :- mq8 (1) |
| License Type :- Developer |
| Probe Id :- PS000090 |
| Application Name :- MQM |
| Component :- psiReceivePublications |
| SCCS Info :- |
| ...ot1\p800_P\src\com.ibm.mq.common\base\src\cmqxzmup.c, |
| Line Number :- 2854 |
| Build Date :- May 16 2016 |
| Build Level :- p800-005-160516.2 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\mq\mq8\bin64\amqzmuf0.exe |
| Arguments :- -m PS4 |
| Addressing mode :- 64-bit |
| Process :- 00011420 |
| Thread :- 00000009 ReceivePubs |
| Session :- 00000000 |
| QueueManager :- PS4 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 36 |
| ConnId(2) QM :- 56 |
| Last HQC :- 2.6.6-3136 |
| Last HSHMEMB :- 2.13.13-350528 |
| Last ObjectName :- |
| Major Errorcode :- MQRC_SYNCPOINT_NOT_ALLOWED |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2569 a09 |
| Comment1 :- |
| Comment2 :- |
| Comment3 :- PS4 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
psiReceivePublications
xcsFFST
|
Did not find anything about the probeid... 
_________________
MQ & Broker admin |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jun 30, 2016 10:02 pm Post subject: Re: FDC in TopicHost routed PUB SUB |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| fjb_saper wrote: |
What happened this used to work?
The environment: Windows 10 Home 64 bits, MQ 8004 and MQ8005 (did the upgrade) cmdlevel (800)
|
Perhaps an update to that (IMHO) abomination of an OS called Windows 10 broke it?
All in the name of security you know.... 
Me? I'm doing the Ostrich trick with that OS. No, never, no way, nope, etc. Not going down that path. I tried it and all sorts of software (not MQ related) that ran on W7 and W8 is broke on W10. As for the printer support... Ugh. I tried and after a few days, I got my old laserjet working but boy was it painful.
Sorry, but that's where I'd look first. Then your AV software.
_________________
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 |
|
|
| hughson |
| Posted: Fri Jul 01, 2016 2:11 am Post subject: Re: FDC in TopicHost routed PUB SUB |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
The FDC says:-
| fjb_saper wrote: |
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| Major Errorcode :- MQRC_SYNCPOINT_NOT_ALLOWED |
| |
+-----------------------------------------------------------------------------+ |
|
If you look up that return code in Knowledge Center you see:-
| IBM Knowledge Center wrote: |
2569 (0A09) (RC2569): MQRC_SYNCPOINT_NOT_ALLOWED
Explanation
An MQPUT or MQPUT1 call using MQPMO_SYNCPOINT was made to a topic that is defined as MCAST(ENABLED). This is not allowed.
Completion Code
MQCC_FAILED
Programmer response
Change the application to use MQPMO_NO_SYNCPOINT, or alter the topic to disable the use of Multicast and retry the operation.
|
You show that the topic object you are using is configured to use Multicast.
| fjb_saper wrote: |
Topic definition:
| Code: |
1 : dis topic(sports) all
AMQ8633: Display topic details.
TOPIC(SPORTS) TYPE(LOCAL)
TOPICSTR(Sports) DESCR( )
CLUSTER(CLS1) CLROUTE(TOPICHOST)
DURSUB(YES) PUB(ENABLED)
SUB(ENABLED) DEFPSIST(YES)
DEFPRTY(0) DEFPRESP(ASYNC)
ALTDATE(2016-06-30) ALTTIME(19.42.28)
PMSGDLV(ALL) NPMSGDLV(ALLAVAIL)
PUBSCOPE(ALL) SUBSCOPE(ALL)
PROXYSUB(FIRSTUSE) WILDCARD(PASSTHRU)
MDURMDL(SYSTEM.DURABLE.MODEL.QUEUE)
MNDURMDL(SYSTEM.NDURABLE.MODEL.QUEUE)
MCAST(ENABLED)
COMMINFO(SYSTEM.DEFAULT.COMMINFO.MULTICAST)
USEDLQ(YES) CUSTOM( ) |
|
| fjb_saper wrote: |
| What happened this used to work? |
Did you change to start using persistent messages? Because Multicast has never accepted persistent messages.
Or did you change to start using multicast?
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 01, 2016 4:42 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Thanks Morag. Did not realize arith1 was the reason code...
Removed Multicast, bounced the pub engine and got my stuff delivered as expected.
So why is there the option to do multicast, when you have no control over the publication where somebody might publish a persistent message? Also there should be a check that prevents you from enabling multicast if you state the default topic behavior to be with persistent messages... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hughson |
| Posted: Fri Jul 01, 2016 12:22 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| fjb_saper wrote: |
| So why is there the option to do multicast, when you have no control over the publication where somebody might publish a persistent message? |
The option to do Multicast is there should you need it. The MQRC covers you for the case where you put a persistent message. Just like a temporary dynamic queue, you can configure it and use it in an invalid way.
| fjb_saper wrote: |
| Also there should be a check that prevents you from enabling multicast if you state the default topic behavior to be with persistent messages... |
Just because you have DEFPRTY set to persistent doesn't mean you'll ever put a persistent message to that topic. Equally it won't stop someone putting a persistent message if it's set to non-persistent.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 01, 2016 8:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| hughson wrote: |
| fjb_saper wrote: |
| So why is there the option to do multicast, when you have no control over the publication where somebody might publish a persistent message? |
The option to do Multicast is there should you need it. The MQRC covers you for the case where you put a persistent message. Just like a temporary dynamic queue, you can configure it and use it in an invalid way.
| fjb_saper wrote: |
| Also there should be a check that prevents you from enabling multicast if you state the default topic behavior to be with persistent messages... |
Just because you have DEFPRTY set to persistent doesn't mean you'll ever put a persistent message to that topic. Equally it won't stop someone putting a persistent message if it's set to non-persistent.
Cheers
Morag |
Well they did enforce the blocking of wildcards for administrative topics... Don't know if it is on SYSTEM.ADMIN.TOPIC or just on any topic starting with $SYS/MQ.... but you cannot delete the admin topic and create one with $SYS/MQ/.... that allows wildcards.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hughson |
| Posted: Fri Jul 01, 2016 8:16 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
My point was that the enforcement you suggest for MCAST wouldn't enforce what you wanted it to enforce.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jul 02, 2016 9:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| hughson wrote: |
My point was that the enforcement you suggest for MCAST wouldn't enforce what you wanted it to enforce.
Cheers
Morag |
This is where I don't get your point at all.
If in the Topic setup you specify the default persistent attribute to be persistent (which would indicate intent, as the default is set to non persistent), why allow you to specify multicast when it is known not to work with persistent messages....
The perhaps more relevant question would be: (and I have not tried this), is it possible to create multiple topic objects with the same topic string but different attributes ?
I understand that in the current state that would probably pose some problems as the inheritance of the attributes is no longer defined with multiple parents to choose from...
In a different String, still related to PUB/SUB:
It used to be that you could use a Topic Consumer with an administrative subscription (alias queue SYSTEM.JMS.X.yyy pointing to the real queue).
It looks like that possibility is now gone too and that you'd have to use a queue consumer in that case.
Managed subscriptions where the only ones I was able to use from my JMS program....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
