[thammoud]

Using the JCA adapter in JBOSS 4.x. It looks like it is being launched correctly.

[timfox]

"thammoud" wrote:
Tim, that is exactly what I thought. Now, assuming that, how do I define connectors/acceptors for the remote clients. I am assuming that I will need to define these in hornetq-configuration.xml file. I tired doing that, but the file seems to be ignored so I must be doing something wrong.

You are misunderstanding the relationship between your application server, the JCA adaptor and the HornetQ server.

Let's take an example

You have your app server deployed on machine A

You have HornetQ deployed on machine B

You deploy your JCA adaptor on machine A (the app server). All your EJBS, MDBs etc either send or receive messages *through the JCA adaptor*.

Take a look at the diagram I posted on my last post.

So you don't deploy any acceptors/connectors or whatever on your app server. Your app server does not contain HornetQ.

You just configure the JCA adaptor to talk to the remote HornetQ instance

[ataylor]

you need to start HornetQ standalone and configure the queues etc in the standalone deployment

[timfox]

"thammoud" wrote:
Using the JCA adapter in JBOSS 4.x. It looks like it is being launched correctly.

No. The JCA adaptor will not start HornetQ!

The purpose of the adapter is to *connect* to a server, like any JCA adaptor. The server might be on a different machine, or on the same machine, depending where you've installed it.

This is no different to any other JCA adaptor. I suggest taking a look at the JCA tutorial. The idea of a JCA adaptor is for JEE components to access various different "Enterprise Information SYstems", i.e. databases, messaging servers, other stuff in a consistent way.

It is simply that, an adaptor. Hope that helps :)

[thammoud]

Makes perfect sense now. Thanks for the explanation. For the sake of keeping deployment simple, would you see any downside for instantiating an in-vm instance from some mbean of ours? We can bundle the right jars in the ear to make that happen. Otherwise we will bite the bullet and do a separate external launch.

[ataylor]

theres nothing to stop you writing your Bean wrappers if you want, or alternatively you could migrate to jboss 5.1 :)

[timfox]

"thammoud" wrote:
Makes perfect sense now. Thanks for the explanation. For the sake of keeping deployment simple, would you see any downside for instantiating an in-vm instance from some mbean of ours?.

No not at all. Although you'd have to write that MBean yourself.

It should be fairly straightforward - take a look at the embedding chapter and the stuff about standalone server to see how to instantiate a server programmatically.

If you create such an MBean you could consider contributing it back to the project and we can include it in the distro - this would be useful to many other users I think.

[thammoud]

Andy,

We tried to migrate to JBOSS 5.1 so that we can use Hornet. In all truthfulness, it was a horror show. The performance especially deployment is extremely slow. We were trying to get our 4.x code to work with 5.1 JBM first and then do the move to Hornet.

The issue thread is at: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160414

Even if they fixed the issue described, the deployment performance is so bad that non of our developers want to touch it. I wish that I had nicer things to say.