1 Reply Latest reply on Apr 15, 2010 6:19 PM by clebert.suconic

Why HornetQResourceAdapter uses InVMConnectionFactory

nnanda Apr 15, 2010 4:09 PM

Hi,

I was checking $JBOSS_HOME/server/default/deploy/hornetq-ra.rar/META-INF/ra.xml and I saw following:

<resourceadapter>
      <resourceadapter-class>org.hornetq.ra.HornetQResourceAdapter</resourceadapter-class>
      <config-property>
         <description>The transport type</description>
         <config-property-name>ConnectorClassName</config-property-name>
         <config-property-type>java.lang.String</config-property-type>
         <config-property-value>org.hornetq.core.remoting.impl.invm.InVMConnectorFactory</config-property-value>
      </config-property>

... ... ...

</resourceadapter>

What is the exact meaning of this?

Is my following assumption correct?

- HornetQ is used within JBoss AS (v. 5.1)

- JBoss is started on a remote host

- An MDB is deployed inside the remote JBoss and annotated (@ResourceAdapter("hornetq-ra.rar")) to use HornetQ and listen to the queue configured within HornetQ.

The MDB cannot consume the messages which are put in the queue by a remote client using Netty connection factory.

Is this a valid assumption?

Please provide some more details.

Thanks,

Niranjan

1. Re: Why HornetQResourceAdapter uses InVMConnectionFactory

clebert.suconic Apr 15, 2010 6:19 PM (in response to nnanda)

A lot of users will choose to deploy HornetQ inside the application server, what is the default approach.

For that, instead of going through TCP, we have MDBs talking to the server through the InVM Adaptor.

You may choose to change this if you decide to deploy HornetQ standalone or having the MDBs talking to a remote server. There's actually an example doing that on the distribution.
Actions