We are using AMQ5.1. We have an MDB with the following Annotations...
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="AMQ.Calypso.Event
This issue is resolved, my JBoss installation was severely tweaked to for
JBoss messaging. Once I got onto a standard JBoss installation, everything
was fine.
- Dave
eidolon1138 wrote:
>
>
>
> I have an MDB that listens to an ActiveMQ queue. It work beautifully. It
> registe
I am using JBoss4.2.2 and a stand-alone AMQ5.1. All my MDBs are decorated
with Annotations so I don't have any deployment descriptors. In this
situation it is easiest to just hard-code the queue name (destination). My
customer has multiple environments (dev, sit, qa, prd) and wants to use
uniqu
I have an MDB that listens to an ActiveMQ queue. It work beautifully. It
registers with AMQ and onMessage fires for each message posted to the queue.
I have a business rule that forces me to process all messages in the order
they were posted to the queue. To accomplish this, I have set
maxMessag