Well, you called that one right!
I completely pulled the WAR out of my compile/deploy and the double issue
went away. So, I've got an issue with my war and I can fix that.
Kudos to you! :handshake:
Okay, that problem is solved, but I'm still dealing with this (I can attach
everything if you need me to:
13:56:29,237 INFO [org.apache.qpid.client.AMQConnection] (Thread-79)
Connection 1 now connected from /10.5.24.164:63455 to
mrgdalprdn4/10.47.23.65:5672
13:56:29,237 INFO [org.apache.qpid.client.AMQConnection] (Thread-78)
Connection 2 now connected from /10.5.24.164:63456 to
mrgdalprdn4/10.47.23.65:5672
13:56:29,730 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 TempQueue72858922-f889-44b6-8a34-f19b349b0567
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists]
13:56:29,734 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 TempQueue72858922-f889-44b6-8a34-f19b349b0567
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists] while endpoint was not activated.
13:56:29,764 INFO [org.apache.qpid.client.AMQConnection] (Thread-79) 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 TempQueue72858922-f889-44b6-8a34-f19b349b0567
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists]
13:56:29,771 WARN [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-79) 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 TempQueue72858922-f889-44b6-8a34-f19b349b0567
(qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405: Already
exists] while endpoint was not activated.
13:56:29,779 WARN [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-79) Failure in Qpid activation
org.apache.qpid.ra.inflow.QpidActivationSpec(ra=org.apache.qpid.ra.QpidResourceAdapter@1eb6d3f
destination=java:jboss/exported/SipMessageTopic
destinationType=javax.jms.Topic 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 TempQueue72858922-f889-44b6-8a34-f19b349b0567
(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 TempQueue72858922-f889-44b6-8a34-f19b349b0567
(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
13:56:34,825 INFO [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-79) Attempting to reconnect
org.apache.qpid.ra.inflow.QpidActivationSpec(ra=org.apache.qpid.ra.QpidResourceAdapter@1eb6d3f
destination=java:jboss/exported/SipMessageTopic
destinationType=javax.jms.Topic ack=Auto-acknowledge durable=false
clientID=null user=null maxSession=1 connectionPerHandler=true)
13:56:34,937 INFO [org.apache.qpid.client.AMQConnection] (Thread-79)
Connection 3 now connected from /10.5.24.164:63466 to
mrgdalprdn4/10.47.23.65:5672
13:56:35,273 INFO [org.apache.qpid.ra.inflow.QpidExceptionHandler]
(Thread-79) Reconnected with Qpid
Weston M. Price wrote:
>
> Hi Dan,
> It looks like you might be including your EJB jar file in both your WAR
> and your EAR. This would explain the multiple deployments. In the latest
> JEE spec, EJB's can now be included in WAR files, but you only need one.
> So, my recommendation would be to modify your build to remove it from the
> WAR and include it only in the EAR file and test again. Note, doing a
> clean on the directories mentioned before as well as a restart is
> recommended.
>
> Regards,
>
> Weston
> On Aug 23, 2012, at 1:33 PM, Dan Carda wrote:
>
>>
>> Also, when I restart JBoss I delete the ./standalone/tmp directory to
>> clean
>> up any temp files.
>>
>> I have found this a good practice for both JBoss and WebLogic.
>>
>>
>>
>> Weston M. Price wrote:
>>>
>>> Hi Dan,
>>> Quick scan of the log on deployment. As noted in the README-JBOSS7.txt
>>> file in the source tree, hot deployment is currently not supported on
>>> AS7
>>> as there is an issue with destination creation that would result in one
>>> of
>>> the errors you are seeing:
>>>
>>> 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 TempQueue2323b34f-c466-45c9-8761-96108eaa34d5
>>> (qpid/broker/SessionAdapter.cpp:400), errorInfo={}) [error code 405:
>>> Already exists] while endpoint was not activated.
>>>
>>> So, when you redeploy the adapter or EAR, you will need to restart the
>>> AS7
>>> instance. Note, this is a AS7 issue not JCA per se.
>>>
>>> Just a thought of what I can see at this point.
>>>
>>> Regards,
>>>
>>> Weston
>>> On Aug 23, 2012, at 1:11 PM, Dan Carda wrote:
>>>
>>>>
>>>> Okay, I'm totally perplexed here and could use a second set of eyes.
>>>>
>>>> This might be more of a configuration issue, but with QPID in the mix I
>>>> can't tell.
>>>>
>>>> To start things out, here's some extra info you'll need.
>>>>
>>>> This is my jboss qpid-standalone.xml file:
>>>> http://old.nabble.com/file/p34340522/qpid-standalone.xml
>>>> qpid-standalone.xml
>>>>
>>>> This is a console output with the qpid rar deployed, but not my ear:
>>>> http://old.nabble.com/file/p34340522/startup-wo-ear-deploy.txt
>>>> startup-wo-ear-deploy.txt
>>>> To me, it looks like the RAR deploy went okay.
>>>>
>>>> This is the console output with my ear deployed:
>>>> http://old.nabble.com/file/p34340522/startup-with-deploy.txt
>>>> startup-with-deploy.txt
>>>> This blatantly did not go well.
>>>>
>>>> Finally, here's the example MDB I'm using. It's mostly commented-out
>>>> for
>>>> debug purposes. (What's important is the @MessageDriven section):
>>>> http://old.nabble.com/file/p34340522/ResourceConfigListenerMDB.java
>>>> ResourceConfigListenerMDB.java
>>>>
>>>> First, you can see when I deploy my EAR file I get tons of error
>>>> messages.
>>>> Some of these are just me. The ones concerning not pointing to a valid
>>>> jar
>>>> file are totally me. I have a JIRA ticket to track down those errors.
>>>> However, I don't think the missing jars are causing my issues.
>>>>
>>>> The interesting output is in the "startup-with-deploy" console output
>>>> file.
>>>>
>>>> First, I'm starting JBoss 7 AS from the command line. You can see from
>>>> the
>>>> output that SipMessageTopic has resources locked. I'm also getting a
>>>> message indicating resources "already exists". How is that possible?
>>>> I
>>>> just started the server 5 seconds prior?
>>>>
>>>> The amazing thing is...it actually works! I have a test program which
>>>> puts
>>>> a message on the bus and the ResourceConfigjListenerMDB message bean
>>>> picks
>>>> it up.
>>>>
>>>> Problem: For reasons which are not clear I'm getting double the number
>>>> of
>>>> MDB's I expect and ALL of them are picking up the incoming message.
>>>>
>>>> When you look in the ResourceConfigListenerMDB.java file I have the
>>>> "maxSession" set to 1. However, when you run my test program the
>>>> output
>>>> clearly shows 2 beans are answering the message. Also, if you increase
>>>> the
>>>> "maxSession" value to 2, then the test program shows 4 beans are
>>>> receiving
>>>> and processing the message.
>>>>
>>>> You can also see from the console output at deploy time two copies of
>>>> ResourceConfigListenerMDB are being registered. I have no clue why?
>>>>
>>>> Have you ever run into this problem before? Can you give me any
>>>> guidance
>>>> on
>>>> how to fix this? If I can just get the "double-bean-thing" fixed I can
>>>> whittle away at the error messages later.
>>>>
>>>> Many, Many Thanks!
>>>> Daniel Carda
>>>> tw telecom
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Pushing-Exasperation%E2%80%A6-tp34340522p34340522.html
>>>> Sent from the Qpid Developers mailing list archive at Nabble.com.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Pushing-Exasperation%E2%80%A6-tp34340522p34340630.html
>> Sent from the Qpid Developers mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
--
View this message in context:
http://old.nabble.com/Pushing-Exasperation%E2%80%A6-tp34340522p34341169.html
Sent from the Qpid Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
