you have (AFAIK) two choices:
1. create an EJB that can publish messages using standard JMS API (and ofcourse using MDB to subscribe/consume)
2. Create a service (MBean) that can instantiate your test client (if you expose a method on the MBean, it can be invoked via JMX console.
Actually, the question is not how to accomplish this. But how to configure the server so that it does not throw the exception when we try to run the client.
loader constraints violated when linking org/jboss/remoting/InvokerLocator
have you had a chance to look at this:
Hope this helps. Shout if not.
It looks like you have a classLoading scoping problem.
I think I did not explain clearly what we are trying to do. We are not trying to run the jboss-messaging client code from an MDB which the provided link addresses. We have the JMS as you will have it from a stanalone client (running in its own JVM). However, we want to invoke it from a jboss server instance because we want to take advantage of the management capabilities of the server. Therefore, we have an MBean which on startup creates and InitialContext with the properties pointing to the remove server and tries to lookup the ConnectionFactory. That is when we get the exception.
Any help will be greately appreciated
As you have not deployed your MBean in a scoped env (unfortunately you should have them scoped - there's a work around, see below), your JMS client is failing..
So, the best and official way is - to scope your client!
Unofficial way - replace the JBoss's jboss-remoting.jar with those bundled with JBM. I experiemented this with earlier and current versions of JBM and it worked for me without any hassles!
We have same issue. We are using EJB3 MDBs and a servlet that creates a local listerner in the same server instance as JBM (1.2.0.GA).
Could you please let me us know what finally worked for you? I have tried replacing remoting jar but EJB3 seems to stop working then.