| Author |
Message
|
| x22ips |
 Posted: Thu Jul 18, 2019 5:30 am Post subject: TopicSender : JMSWMQ2008: Failed to open MQ queue |
 |
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
Hello,
I'm from mq support team and we receive error code from application side:
Application tries to send messages to topic.
2019-07-17 14:41:18.274 ERROR 3568 — [enerContainer-1] c.d.adi.visibility.jms.TopicSender : JMSWMQ2008: Failed to open MQ queue 'T.001.CHANGE_NOTIFICATION'.; nested exception is com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMS ('M WMQ2008: Failed to open MQ queue 'T.001.CHANGE_NOTIFICATION'.\nJMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.\nUse the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' QRC_UNKNOWN_OBJECT_NAME').\n",
TOPIC and Subscription are defined and required permission are configured as well.
From application log file:
2019-07-18 14:40:05.640 INFO 111976 --- [io-12731-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet'
2019-07-18 14:40:05.657 INFO 111976 --- [io-12731-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 17 ms
2019-07-18 14:42:29.037 INFO 111976 --- [enerContainer-1] c.d.a.v.jms.QueueMessageListener : Incoming message
JMSMessage class: jms_text
JMSType: null
JMSDeliveryMode: 2
JMSDeliveryDelay: 0
JMSDeliveryTime: 0
JMSExpiration: 1563453808789
JMSPriority: 4
JMSMessageID: ID:414d51205153573231544131202020204d7d225d83aeec22
JMSTimestamp: 1563453748789
JMSCorrelationID: null
JMSDestination: queue:///Q.001_MEDIT.VIS_EXT
JMSReplyTo: null
JMSRedelivered: false
CA_APM_CorID: 051AF609AC18092A4E858E0A0A44B38E,1:2,0,0,,,AgAAAVVIQgAAAAFGAAAAAQAAABFqYXZhLnV0aWwuSGFzaE1hcAAAAARIQgAAAAJGAAAAAgAAABBqYXZhLmxhbmcuU3RyaW5nAApUeG5UcmFjZUlkSEIAAAADRQAAAAIAJDA1MTUzNURGQUMxODA5MkE0RTg1OEUwQTUzODUwNkFCOTQ0NkhCAAAABEUAAAACABNDYWxsZXIgQ29tcG9uZW50IElESEIAAAAFRQAAAAIAATJIQgAAAAZFAAAAAgAPQ2FsbGVyVGltZXN0YW1wSEIAAAAHRQAAAAIADTE1NjM0NTM3NDg3ODlIQgAAAAhFAAAAAgARVXBzdHJlYW1HVUlEQ2FjaGVIQgAAAAlGAAAAAwAAABNqYXZhLnV0aWwuQXJyYXlMaXN0AAAAAUhCAAAACkUAAAACACAwNTFBNTc0QUFDMTgwOTJBNEU4NThFMEE2QTczMkRFMw==
JMSXAppID: catalina.startup.Bootstrap
JMSXDeliveryCount: 1
JMSXUserID: medit
JMS_IBM_Character_Set: UTF-8
JMS_IBM_Encoding: 273
JMS_IBM_Format: MQSTR
JMS_IBM_MsgType: 8
JMS_IBM_PutApplType: 28
JMS_IBM_PutDate: 20190718
brand: A
environment: tui
market: 50000
senderApp: 001_MEDIT
senderHost: ivwb1379
setupDocument: visibility_A_50000_customer.xml
targetGroup: customer
type: VISIBILITY_CHANGE
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<visibility-items brand-code="A" market-code ...
2019-07-18 14:42:29.039 INFO 111976 --- [enerContainer-1] c.d.a.v.jms.QueueMessageListener : Received message ID:414d51205153573231544131202020204d7d225d83aeec22 timestamp: 1563453748789
2019-07-18 14:42:29.061 INFO 111976 --- [enerContainer-1] c.d.a.v.jms.QueueMessageListener : Message transformed successfully.
2019-07-18 14:42:29.134 INFO 111976 --- [enerContainer-1] c.d.adi.visibility.jms.TopicSender : sending message on topic [T.001_MEDIT.CHANGE_NOTIFICATION] with properties [{market=50000, targetGroup=customer, senderApp=001_MEDIT, type=VISIBILITY_CHANGE, brand=A, senderHost=ivwb3836.app-test.web.adi.vag}]
2019-07-18 14:42:29.151 ERROR 111976 --- [enerContainer-1] c.d.adi.visibility.jms.TopicSender : JMSWMQ2008: Failed to open MQ queue 'T.001_MEDIT.CHANGE_NOTIFICATION'.; nested exception is com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'T.001_MEDIT.CHANGE_NOTIFICATION'.
JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.
Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
Any idea?
Many thanks.
Last edited by x22ips on Thu Jul 18, 2019 12:22 pm; edited 1 time in total |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jul 18, 2019 6:34 am Post subject: Re: TopicSender : JMSWMQ2008: Failed to open MQ queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| x22ips wrote: |
| TOPIC and Subscription are defined and required permission are configured as well. |
Does that queue in fact exist? How does that queue name factor into the topic (or more likely subscription) that you're talking about?
Why do the application team say their application is trying to open it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Jul 18, 2019 3:38 pm Post subject: Re: TopicSender : JMSWMQ2008: Failed to open MQ queue |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| x22ips wrote: |
2019-07-18 14:42:29.151 ERROR 111976 --- [enerContainer-1] c.d.adi.visibility.jms.TopicSender : JMSWMQ2008: Failed to open MQ queue 'T.001_MEDIT.CHANGE_NOTIFICATION'.;
nested exception is com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'T.001_MEDIT.CHANGE_NOTIFICATION'.
JMS attempted to perform an MQOPEN, but WebSphere MQ reported an error.
Use the linked exception to determine the cause of this error.
Check that the specified queue and queue manager are defined correctly.;
nested exception is com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME'). |
The root cause is that the QUEUE (not TOPIC) called T.001_MEDIT.CHANGE_NOTIFICATION has not been defined.
What do you see if you issue the following MQSC command?
| Code: |
| DISPLAY QUEUE(T.001_MEDIT.CHANGE_NOTIFICATION) |
This suggests to me that you are using ProviderVersion 6 - the old pre-V7 queued pub/sub interface. What is your ProviderVersion of your JMS application?
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| x22ips |
| Posted: Fri Jul 19, 2019 1:15 am Post subject: |
|
|
Novice
Joined: 02 Dec 2013
Posts: 22
|
sending message on topic [T.001_MEDIT.CHANGE_NOTIFICATION]
it is not a queue it should be a topic:
dis TOPIC(T.001_MEDIT.CHANGE_NOTIFICATION)
AMQ8633: Display topic details.
TOPIC(T.001_MEDIT.CHANGE_NOTIFICATION)
TYPE(LOCAL)
TOPICSTR(T.001_MEDIT.CHANGE_NOTIFICATION)
DESCR( ) CLUSTER( )
CLROUTE(DIRECT) DURSUB(ASPARENT)
PUB(ASPARENT) SUB(ASPARENT)
DEFPSIST(ASPARENT) DEFPRTY(ASPARENT)
DEFPRESP(ASPARENT) ALTDATE(2017-12-11)
ALTTIME(00.41.06) PMSGDLV(ASPARENT)
NPMSGDLV(ASPARENT) PUBSCOPE(ASPARENT)
SUBSCOPE(ASPARENT) PROXYSUB(FIRSTUSE)
WILDCARD(PASSTHRU) MDURMDL( )
MNDURMDL( ) MCAST(ASPARENT)
COMMINFO( ) USEDLQ(ASPARENT)
CUSTOM( ) |
|
| Back to top |
|
|
| hughson |
| Posted: Fri Jul 19, 2019 2:47 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Please read my previous response in full.
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jul 19, 2019 3:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hughson wrote: |
| Please read my previous response in full. |
My most worthy associate has explained your problem very clearly (as is her special skill).
The ongoing problem is that it doesn't line up with your flawed understanding.
Reread her response.
(All Hail Morag! All Hail Morag!)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kykb |
| Posted: Tue Apr 11, 2023 6:45 am Post subject: |
|
|
Newbie
Joined: 10 Apr 2023
Posts: 4
|
|
| Back to top |
|
|
|
|
