qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Carda <daniel.ca...@twtelecom.com>
Subject Still one more annoying error message...
Date Wed, 05 Sep 2012 18:12:33 GMT

Okay, I've got most of the errors fixed, but I'm still getting one more
annoying message about not being able to lock resources.

Could this be caused by the two of my MDB's pointing at the same QPID topic?  

Here's the error message from the start-up console log:

12:06:04,274 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) JBAS014142:
Started message driven bean 'ResourceConfigListenerMDB' with 'qpid-ra-0.19'
resource adapter
12:06:04,274 INFO  [org.jboss.as.ejb3] (MSC service thread 1-12) JBAS014142:
Started message driven bean 'SipSasResponseListenerBean' with 'qpid-ra-0.19'
resource adapter
12:06:04,274 INFO  [org.jboss.as.ejb3] (MSC service thread 1-7) JBAS014142:
Started message driven bean 'SipSasListenerBean' with 'qpid-ra-0.19'
resource adapter
12:06:04,274 INFO  [org.jboss.as.ejb3] (MSC service thread 1-14) JBAS014142:
Started message driven bean 'ServiceConfigListenerMDB' with 'qpid-ra-0.19'
resource adapter
12:06:04,575 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC
service thread 1-9) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401)
for context '/sip_application-war'
12:06:04,879 INFO  [org.apache.qpid.client.security.DynamicSaslRegistrar]
(IoReceiver - mrgdalprdn4/10.47.23.65:5672) Additional SASL providers
successfully registered.
12:06:04,883 INFO  [org.apache.qpid.client.security.CallbackHandlerRegistry]
(IoReceiver - mrgdalprdn4/10.47.23.65:5672) Callback handlers available for
SASL mechanisms: [EXTERNAL, GSSAPI, CRAM-MD5-HASHED, CRAM-MD5, AMQPLAIN,
PLAIN, ANONYMOUS]
12:06:04,989 INFO  [org.apache.qpid.client.AMQConnection] (Thread-79)
Connection 3 now connected from /10.5.24.164:38858 to
mrgdalprdn4/10.47.23.65:5672
12:06:04,989 INFO  [org.apache.qpid.client.AMQConnection] (Thread-80)
Connection 2 now connected from /10.5.24.164:38855 to
mrgdalprdn4/10.47.23.65:5672
12:06:04,989 INFO  [org.apache.qpid.client.AMQConnection] (Thread-81)
Connection 1 now connected from /10.5.24.164:38857 to
mrgdalprdn4/10.47.23.65:5672
12:06:04,991 INFO  [org.apache.qpid.client.AMQConnection] (Thread-78)
Connection 4 now connected from /10.5.24.164:38856 to
mrgdalprdn4/10.47.23.65:5672
12:06:05,551 INFO  [org.apache.qpid.client.AMQConnection] (IoReceiver -
mrgdalprdn4/10.47.23.65:5672) Not a hard-error connection not closing:
org.apache.qpid.AMQException: ch=0 id=3
ExecutionException(errorCode=RESOURCE_LOCKED, commandId=3, classCode=8,
commandCode=1, fieldIndex=0, description=resource-locked: Cannot grant
exclusive access to queue TempQueue1693ffe9-b9b2-4cb9-bc48-cc2d3026d6e8
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists]
12:06:05,559 WARN  [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(IoReceiver - mrgdalprdn4/10.47.23.65:5672) Received JMSException:
javax.jms.JMSException: Exception thrown against AMQConnection:
Host: mrgdalprdn4
Port: 5672
Virtual Host: test
Client ID: client_id
Active session count: 0: org.apache.qpid.AMQException: ch=0 id=3
ExecutionException(errorCode=RESOURCE_LOCKED, commandId=3, classCode=8,
commandCode=1, fieldIndex=0, description=resource-locked: Cannot grant
exclusive access to queue TempQueue1693ffe9-b9b2-4cb9-bc48-cc2d3026d6e8
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists] while endpoint was not activated.
12:06:05,598 INFO  [org.apache.qpid.client.AMQConnection] (Thread-81) Not a
hard-error connection not closing: org.apache.qpid.AMQException: ch=0 id=3
ExecutionException(errorCode=RESOURCE_LOCKED, commandId=3, classCode=8,
commandCode=1, fieldIndex=0, description=resource-locked: Cannot grant
exclusive access to queue TempQueue1693ffe9-b9b2-4cb9-bc48-cc2d3026d6e8
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists]
12:06:05,607 WARN  [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-81) Received JMSException: javax.jms.JMSException: Exception thrown
against AMQConnection:
Host: mrgdalprdn4
Port: 5672
Virtual Host: test
Client ID: client_id
Active session count: 0: org.apache.qpid.AMQException: ch=0 id=3
ExecutionException(errorCode=RESOURCE_LOCKED, commandId=3, classCode=8,
commandCode=1, fieldIndex=0, description=resource-locked: Cannot grant
exclusive access to queue TempQueue1693ffe9-b9b2-4cb9-bc48-cc2d3026d6e8
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists] while endpoint was not activated.
12:06:05,626 WARN  [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-81) Failure in Qpid activation
org.apache.qpid.ra.inflow.QpidActivationSpec(ra=org.apache.qpid.ra.QpidResourceAdapter@1d92bd6
destination=java:jboss/exported/SipMessageTopic
destinationType=javax.jms.Topic selector=SipMessageType =
'ResourceConfigMsg' ack=Auto-acknowledge durable=false clientID=null
user=null maxSession=1 connectionPerHandler=true): javax.jms.JMSException:
Error registering consumer: org.apache.qpid.AMQException: ch=0 id=3
ExecutionException(errorCode=RESOURCE_LOCKED, commandId=3, classCode=8,
commandCode=1, fieldIndex=0, description=resource-locked: Cannot grant
exclusive access to queue TempQueue1693ffe9-b9b2-4cb9-bc48-cc2d3026d6e8
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists]
        at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2056)
        at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2008)
        at
org.apache.qpid.client.AMQConnectionDelegate_0_10.executeRetrySupport(AMQConnectionDelegate_0_10.java:369)
        at
org.apache.qpid.client.AMQConnection.executeRetrySupport(AMQConnection.java:593)
        at
org.apache.qpid.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102)
        at
org.apache.qpid.client.AMQSession.createConsumerImpl(AMQSession.java:2006)
        at
org.apache.qpid.client.AMQSession.createConsumer(AMQSession.java:988)
        at
org.apache.qpid.ra.inflow.QpidMessageHandler.setup(QpidMessageHandler.java:123)
        at
org.apache.qpid.ra.inflow.QpidMessageHandler.start(QpidMessageHandler.java:273)
        at
org.apache.qpid.ra.inflow.QpidActivation.setup(QpidActivation.java:122)
        at
org.apache.qpid.ra.inflow.QpidActivation$SetupActivation.run(QpidActivation.java:203)
        at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
Caused by: org.apache.qpid.AMQException: ch=0 id=3
ExecutionException(errorCode=RESOURCE_LOCKED, commandId=3, classCode=8,
commandCode=1, fieldIndex=0, description=resource-locked: Cannot grant
exclusive access to queue TempQueue1693ffe9-b9b2-4cb9-bc48-cc2d3026d6e8
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists]
        at
org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1051)
        at
org.apache.qpid.client.AMQSession_0_10.sync(AMQSession_0_10.java:1031)
        at
org.apache.qpid.client.AMQSession_0_10.sendQueueBind(AMQSession_0_10.java:380)
        at
org.apache.qpid.client.AMQSession_0_10.createSubscriptionQueue(AMQSession_0_10.java:1328)
        at
org.apache.qpid.client.AMQSession_0_10.handleAddressBasedDestination(AMQSession_0_10.java:1232)
        at
org.apache.qpid.client.AMQSession.registerConsumer(AMQSession.java:2925)
        at org.apache.qpid.client.AMQSession.access$500(AMQSession.java:102)
        at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2033)
        ... 11 more

12:06:06,134 INFO  [org.hibernate.validator.util.Version] (MSC service
thread 1-9) Hibernate Validator 4.2.0.Final
12:06:08,140 INFO  [org.richfaces.log.Cache] (MSC service thread 1-9)
Selected fallback cache factory
12:06:08,143 INFO  [org.richfaces.log.Cache] (MSC service thread 1-9)
Creating LRUMap cache instance using parameters:
{javax.faces.PROJECT_STAGE=Development, javax.faces.SKIP_COMMENTS=true}
12:06:08,158 INFO  [org.richfaces.log.Cache] (MSC service thread 1-9)
Creating LRUMap cache instance of 512 items capacity
12:06:08,353 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC
service thread 1-9) Monitoring
jndi:/default-host/sip_application-war/WEB-INF/faces-config.xml for
modifications
12:06:08,449 INFO  [org.jboss.web] (MSC service thread 1-9) JBAS018210:
Registering web context: /sip_application-war
12:06:08,453 INFO  [org.jboss.as] (MSC service thread 1-9) JBAS015951: Admin
console listening on http://127.0.0.1:10090
12:06:08,454 INFO  [org.jboss.as] (MSC service thread 1-9) JBAS015874: JBoss
AS 7.1.1.Final "Brontes" started in 12682ms - Started 463 of 571 services
(85 services are passive or on-demand)
12:06:08,827 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)
JBAS018559: Deployed "sip_application-ear-1.0-SNAPSHOT.ear"
12:06:08,828 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2)
JBAS018559: Deployed "qpid-ra-0.19.rar"
12:06:10,674 INFO  [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-81) Attempting to reconnect
org.apache.qpid.ra.inflow.QpidActivationSpec(ra=org.apache.qpid.ra.QpidResourceAdapter@1d92bd6
destination=java:jboss/exported/SipMessageTopic
destinationType=javax.jms.Topic selector=SipMessageType =
'ResourceConfigMsg' ack=Auto-acknowledge durable=false clientID=null
user=null maxSession=1 connectionPerHandler=true)
12:06:10,787 INFO  [org.apache.qpid.client.AMQConnection] (Thread-81)
Connection 5 now connected from /10.5.24.164:38863 to
mrgdalprdn4/10.47.23.65:5672
12:06:11,135 INFO  [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-81) Reconnected with Qpid


Thanks!
Daniel Carda
TW Telecom

-- 
View this message in context: http://old.nabble.com/Still-one-more-annoying-error-message...-tp34393689p34393689.html
Sent from the Qpid Developers mailing list archive at Nabble.com.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message