Author |
Message
|
MQMB&WAS |
Posted: Wed Jul 27, 2016 8:01 pm Post subject: CWSJY0003W: MQJCA4023: Startup reconnection failed for Acti |
|
|
Centurion
Joined: 12 Jun 2016 Posts: 130
|
Messages are not processing from a queue, I don't see any errors on qmgr.
So I restarted the activation specs on the WAS8.5 servers.
I see below errors when I pause and resume the specs.
[7/15/16 22:32:57:730 CDT] 0000009d ActivationSpe I J2CA0524I: The Message Endpoint for ActivationSpec jms/mqas/ear/APP/appListener1 (com.ibm.mq.connector.inbound.ActivationSpecImpl) and MDB Application APP#app-EJB.jar#PubSubMDBBean1 is deactivated.
[7/15/16 22:32:57:768 CDT] 0000009d ActivationSpe I J2CA0524I: The Message Endpoint for ActivationSpec jms/mqas/ear/APP/appListener2 (com.ibm.mq.connector.inbound.ActivationSpecImpl) and MDB Application PP#app-EJB.jar#PubSubMDBBean2 is deactivated.
[7/15/16 22:33:08:620 CDT] 0000009c SibMessage W [:] CWSJY0003W: MQJCA4023: Startup reconnection failed for ActivationSpec 'javax.jms.Queue:jms/mqqd/ear/APP/InputQueue@ <1017283053>'. Exception details: '
Message : com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'APP.QA'.
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.
Class : class com.ibm.msg.client.jms.DetailedInvalidDestinationException
Caused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
Class : class com.ibm.mq.MQException
[7/15/16 22:33:08:625 CDT] 0000009c ActivationSpe I J2CA0523I: The Message Endpoint for ActivationSpec jms/mqas/ear/APP/appListener1 (com.ibm.mq.connector.inbound.ActivationSpecImpl) and MDB Application APP#app-EJB.jar#PubSubMDBBean1 is activated.
[7/15/16 22:33:08:902 CDT] 0000024c SibMessage W [:] CWSJY0003W: MQJCA4023: Startup reconnection failed for ActivationSpec 'javax.jms.Queue:jms/mqqd/ear/APP/InputQueue@ <1017283053>'. Exception details: '
Message : com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'APP.QA'.
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.
Class : class com.ibm.msg.client.jms.DetailedInvalidDestinationException
Stack : com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:498)
Caused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
Class : class com.ibm.mq.MQException
[7/15/16 22:33:08:905 CDT] 0000024c SibMessage W [:] CWSJY0003W: MQJCA4014: Failed to reconnect one or more MDBs after a connection failure.
But the queue does exist
dis qa(APP.QA)
1 : dis qa(APP.QA)
AMQ8409: Display Queue details.
QUEUE(APP.QA) TYPE(QALIAS)
TARGET(APP.QL)
CLUSNL( ) CLUSTER( )
CLWLPRTY(0) CLWLRANK(0)
CUSTOM( ) DEFBIND(NOTFIXED)
DEFPRTY(0) DEFPSIST(YES)
DEFPRESP(SYNC) DEFREADA(NO)
DESCR(APP)
GET(ENABLED) PUT(ENABLED)
PROPCTL(COMPAT) SCOPE(QMGR)
TARGTYPE(QUEUE)
dis qs(APP.QL)
1 : dis qs(APP.QL)
AMQ8450: Display queue status details.
QUEUE(APP.QL)
TYPE(QUEUE) CURDEPTH(1)
IPPROCS(0) LGETDATE( )
LGETTIME( ) LPUTDATE(2016-07-15)
LPUTTIME(13.21.53) MEDIALOG( )
MONQ(MEDIUM) MSGAGE(34660)
OPPROCS(0) QTIME( , )
UNCOM(NO)
could someone please tell why the messages are not processing?
Thanks in advance. |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
smdavies99 |
Posted: Wed Jul 27, 2016 11:25 pm Post subject: |
|
|
![](images/avatars/4738380695809c05f78f20.jpg) Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
This
Quote: |
WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
|
Tells you a lot.
You have identified that the Object exists. That is good.
But do you have access to the object and is that access sufficient to allow you what you want to do?
The MQ Logs (AMQERR01.log) for the queue manager will give you some more information on the failure.
Then you need to get your MQ Admins to give you access to the Queue. _________________ 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 |
|
![](templates/DAJ_Glass/images/spacer.gif) |
hughson |
Posted: Thu Jul 28, 2016 1:51 am Post subject: Re: CWSJY0003W: MQJCA4023: Startup reconnection failed for A |
|
|
![](images/avatars/810794940518bb946528b3.jpg) Padawan
Joined: 09 May 2013 Posts: 1916 Location: Bay of Plenty, New Zealand
|
MQMB&WAS wrote: |
[[7/15/16 22:33:08:625 CDT] 0000009c ActivationSpe I J2CA0523I: The Message Endpoint for ActivationSpec jms/mqas/ear/APP/appListener1 (com.ibm.mq.connector.inbound.ActivationSpecImpl) and MDB Application APP#app-EJB.jar#PubSubMDBBean1 is activated.
[7/15/16 22:33:08:902 CDT] 0000024c SibMessage W [:] CWSJY0003W: MQJCA4023: Startup reconnection failed for ActivationSpec 'javax.jms.Queue:jms/mqqd/ear/APP/InputQueue@ <1017283053>'. Exception details: '
Message : com.ibm.msg.client.jms.DetailedInvalidDestinationException: JMSWMQ2008: Failed to open MQ queue 'APP.QA'.
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.
Class : class com.ibm.msg.client.jms.DetailedInvalidDestinationException
Stack : com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:498)
Caused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2085' ('MQRC_UNKNOWN_OBJECT_NAME').
Class : class com.ibm.mq.MQException |
Are you sure they are connecting to the correct queue manager?
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
fjb_saper |
Posted: Thu Jul 28, 2016 4:59 am Post subject: |
|
|
![](images/avatars/gallery/misc/2.gif) Grand High Poobah
Joined: 18 Nov 2003 Posts: 20696 Location: LI,NY
|
And if the queue is in fact a cluster queue, are you sure the qmgr name on the destination is blank? Sometime even that did not work quite right and I had to set up a cluster alias and set that as qmgr name on the destination.
How is the destination defined:
- JNDI ? properties of the destination
- just the queue name being used in a createQueue from the session or the context?
- URI form? show us the URI used.
Have fun ![](images/smiles/innocent.gif) _________________ MQ & Broker admin |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
MQMB&WAS |
Posted: Mon Aug 01, 2016 5:08 pm Post subject: Re: CWSJY0003W: MQJCA4023: Startup reconnection failed for A |
|
|
Centurion
Joined: 12 Jun 2016 Posts: 130
|
They were using wrong DNS alias for the hostname field, issued was resolved after correcting it.
Thanks for all your inputs. |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
|