Yes, I saw the part about hot deployment.
So, always restart the server every time I do a deploy. The good news is
JBoss 7 starts up much faster than previous version.
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-tp34340522p34340591.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]
