To send messages you need a session.
You cannot get a session without an active
So the answer is no.
I believe you can do this if you run your client in a vm with a stripped down jboss with jbossmq deployed, and the queue deployed on the client. Obviously this is going to require a bunch of stuff on the client so message persistence works there.
I don't really see how any solution that allows you to always send messages no matter what state the rest of the system is in can work any differently than this. You need a connection to whatever is persisting the messages, and to make this always available it has to be entirely on the local machine.
I think he is asking for "work offline" type behaviour.
JBossMQ does not support this, even if you
send the messages to a local persistent queue you
still need something that will move them to the
real queue when the connection is available.