> I am using v. 2.2.4 and not using MDBs.
> The client is not a bean and running in a seperate VM
As said in the manual JMS RA does not work with 2.2.x.
Sorry, I should have said 2.4.x.
Ok, I have to review what you actually wrote to start with. Is the following conditions met:
- JBoss 2.4.x
- JMS RA used from with inside a session or entity bean
- send or sync receive only.
If not, it will not work. JMS-RA is for EJB:s only, it is not possible (or meaningfull) to use it ouside of the JBoss containers. Is that what you are trying to do.
Subscribing, on the other hand, should allways be done with MDB, when working inside JBoss.
Yes we are using JBoss 2.4.x
Yes JMS RA used from within an Entity bean to publish message.
> - send or sync receive only.
I am not sure what you are asking. Please explain.
The subscriber is a java client application outside the server VM.
The general scenario we are trying to accomplish with JBoss is this:
When entity bean gets changed it publishes a JMS message (sort of like a Database trigger). Since the message is published in the entity bean's setter methods, the message should only be truly published when the transaction commits. With the configuration described in the manual, this appears to work. However, we have no way of verifying this since our subscribers are unable to receive messages. As stated before, the manual does not address subscribers in this configuration.
Thanks for you help!
> However, we have no way of verifying this since our
> subscribers are unable to receive messages. As
> stated before, the manual does not address
> subscribers in this configuration.
Well, yes it is. Since the subscriber would be a standalone JMS client as covered in the part of the manual that treats normal JMS.
If you have a standard JMS subscriber that subscribed to the same destination your bean is publishing to it should work.
If not, there is a bug lurking somewhere. Have you turned debugging on in JBoss or looked into log/server.log?
> Thanks for you help!
As I stated in the original post, 'normal' configuration of JMS, messaging works fine, albeit non-transactionally. I understand this configuration is covered in the manual.
However, with JMS setup as a resource the subscriber is not covered. If this configuration does not affect the subscriber, then the documentation should probably mention it.
If the subscriber is unaffected by the publisher using JMS as a resource, and the subscriber is not receiving messages, then I must assume there is a bug.
You mention turning on debugging. Forgive me for my ignorance, as I am very new to Jboss and open-source, how do I turn debugging on?
And regarding the server.log, what information am I looking for?
Thanks again for your help!
> If the subscriber is unaffected by the publisher
> using JMS as a resource, and the subscriber is not
> receiving messages, then I must assume there is a
Yes, now we are on. How you publish a message to a destination has nothing to do with how you get it from the destination.
> You mention turning on debugging. Forgive me for my
> ignorance, as I am very new to Jboss and open-source,
> how do I turn debugging on?
> And regarding the server.log, what information am I
> looking for?
If you look, you will see.
Otherwise you will have to share your code and configuration.
> Thanks again for your help!