| Author |
Message
|
| chandu.yalamanchili |
 Posted: Fri Nov 06, 2009 12:14 pm Post subject: reason code 3155 |
 |
|
Apprentice
Joined: 29 Jun 2007
Posts: 29
|
Seeing these errors after implementing security on the Queues
####<Nov 6, 2009 1:50:20 PM CST> <Warning> <EJB> <mn1s34009> <dvb2b_managed1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257537020641> <BEA-010096> <The Message-Driven EJB: RecipientEventListenerBean is unable to connect to the JMS destination or bind to JCA resource adapter: jms/Recipient_1. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
####<Nov 6, 2009 1:50:20 PM CST> <Warning> <EJB> <mn1s34009> <dvb2b_managed1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257537020642> <BEA-010061> <The Message-Driven EJB: RecipientEventListenerBean is unable to connect to the JMS destination: jms/Recipient_1. The Error was:
com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: MQRCCF_SUBSCRIPTION_IN_USE Reason code 3155>
Can anyone shed some light on this
Thanks
Chandu |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Nov 06, 2009 12:19 pm Post subject: Re: reason code 3155 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chandu.yalamanchili wrote: |
| Seeing these errors after implementing security on the Queues |
Seeing this where?
| chandu.yalamanchili wrote: |
The Error was:
com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: MQRCCF_SUBSCRIPTION_IN_USE Reason code 3155>
Can anyone shed some light on this |
Seems clear enough.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chandu.yalamanchili |
| Posted: Fri Nov 06, 2009 12:23 pm Post subject: |
|
|
Apprentice
Joined: 29 Jun 2007
Posts: 29
|
| seeing errors on the weblogic managed server side. Please let me know if you need any more details |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Nov 06, 2009 12:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chandu.yalamanchili wrote: |
| seeing errors on the weblogic managed server side. Please let me know if you need any more details |
Sounds to me like as part of your security installation, you've left an active subscription. Possibly (and possibly not) from incorrectly terminating an MDB.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri Nov 06, 2009 12:27 pm Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| chandu.yalamanchili wrote: |
| Please let me know if you need any more details |
Pls, put in all in one shot, as much you know about the scenarios/cases you are trying to implement. Would be helpful. 
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| chandu.yalamanchili |
| Posted: Fri Nov 06, 2009 1:15 pm Post subject: |
|
|
Apprentice
Joined: 29 Jun 2007
Posts: 29
|
| Can you suggest how to deregister the subscription after the prcessing is done. |
|
| Back to top |
|
|
| chandu.yalamanchili |
| Posted: Fri Nov 06, 2009 1:59 pm Post subject: |
|
|
Apprentice
Joined: 29 Jun 2007
Posts: 29
|
The scenario is MDB' s on weblogic application server is trying to connect to the MQ Queue Manager using LDAP settings. One the Queue Manager we had resistricted application userid access depending on the Queues. And also implemented security on the SYSTEM.BROKER.CONTROL.QUEUE, SYSTEM.BROKER.DEFAULT.STREAM Queues by adding applications userid. seeing the errors in the weblogic logs
####<Nov 6, 2009 3:31:20 PM CST> <Warning> <EJB> <mn1s34009> <dvb2b_managed1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1257543080636> <BEA-010061> <The Message-Driven EJB: RecipientEventListenerBean is unable to connect to the JMS destination: jms/Recipient_1. The Error was:
com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: MQRCCF_SUBSCRIPTION_IN_USE Reason code 3155>
and on MBD is showing "MDB application is not connected to the messaging system". and seeing nothing in the Queue manager logs and no FDC. what need to be done to solve the errors.
Thanks
Chandu |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Nov 06, 2009 3:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| Broker command failed: MQRCCF_SUBSCRIPTION_IN_USE Reason code 3155 |
Seems quite clear.
There is already somebody consuming message from that subscription. Or the parms passed on the call do not exactly match those of the subscription. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| chandu.yalamanchili |
| Posted: Mon Nov 09, 2009 8:40 am Post subject: |
|
|
Apprentice
Joined: 29 Jun 2007
Posts: 29
|
| How to find which subscription is in use? |
|
| Back to top |
|
|
| neutron |
| Posted: Wed Mar 14, 2012 9:47 pm Post subject: JMSSubscriber: BrokerCommandFailedException: Broker command |
|
|
Novice
Joined: 25 Aug 2008
Posts: 21
|
My JMS application received this error during a subscription.
Prior to this error, the machine(A) that the JMS application is on crashed due to a CPU fatal error. Hence the cluster server failover the JMS subscriber to another machine (B) within 1 minutes. And when the subscriber tried to subscribe back to the topic, it hit the above error. The subscriber was only able to subscribe back after 2 minutes of several retries.
Questions:
1) Is this the expected behavior? Even its the same subscriber with the same subscription ID and client ID.
2) How long and where can i see the timeout setting for subscription?
Thanks |
|
| Back to top |
|
|
|
|
