activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From THMayr <Thomas.M...@adesso.de>
Subject Re: Integrate ActiveMQ 5.13.1 into WildFly 10.0.0
Date Tue, 23 Feb 2016 22:01:05 GMT
OK, finally I found the following solution:

Instead of adding the ActiveMQ resource adapter configuration to
standalone.xml, I added it to standalone-full.xml, 
which seems to support MDBs. However you have the configure the connection
factory with a different name, because 
otherwise it conficts with the internal MQ configuration in this file. So I
used the JNDI name 
"java:/ActiveMQ/ConnectionFactory". The <admin-objects> are not required,
because the ActiveMQ adapter doesn't support
the @ActivationConfigProperties "connectionFactoryJndiName" or
"destinationJndiName" as required for EJB 3.0 compliant
MDBs (see  Using EJB 3.0 Compliant MDBs
<http://docs.oracle.com/cd/E21764_01/web.1111/e15493/annotations.htm#WLMDB10008> 
). So the configuration looks
like this:



This resource adapter is referenced by the MDB under the EJB3 subsystem:



When WildFly is started without the deployment of the EAR containing the
MDB, it logs the following messages on the
console:



No queues or connections are visible at this point in the ActiveMQ server.

The configuration of the MDB looks like this:



When the EAR containing this MD is deployed, WildFly logs the following
messages on the console:



Now, the queue is created on the ActiveMQ server with the name
"de.adesso.tma.test.ejb.RequestQueue" as defined as 
destination for the MDB and one consumer. The ActiveMQ console can now be
used to send a message via the queue to the
MDB.

What is still not clear, is the following error message:



Regards Thomas




--
View this message in context: http://activemq.2283324.n4.nabble.com/Integrate-ActiveMQ-5-13-1-into-WildFly-10-0-0-tp4708055p4708156.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message