JBoss store and forward JMS to remote JBoss on unreliable co

[parlor]

Hi,

I am using JBoss 3.2.1 with JBossMQ on multiple computers each running there own non-clustered instance. My question relates to sending a JMS message to a queue or durable topic from one computer to another with an "unreliable" network connection between the two. Is there any way to configure JBoss and/or JMS to store and forward a JMS message to a remote queue once the connection is detected to be available again? My scenario is thus

- PC 1 is connected to PC2
- PC 1 sends JMS messages to queue or topic on PC2
- PC 2 (or 1) loses its connection to the network
- PC 1 still sends messages to PC2 and JBoss stores them and forwards them once the connection to the remote provider is detected.

I have searched the forums here, the JBoss SAMS book, and the web and haven't found to much on this.

Thanks for anyones help

[adrian.brock]

Set up an MDB to pull the messages onto PC2
Search for ProviderURL to find the details for a remote MDB
connection.

The MDB will try to reconnect when the connection is not
available.

Regards,
Adrian

[sasgon]

Set up an MDB to pull the messages onto PC2
Search for ProviderURL to find the details for a remote MDB
connection.

The MDB will try to reconnect when the connection is not
available.

Regards,
Adrian

Hello,

I would like to up this discussion using slightly changed input data. I think the correct name for requested functionality is 'store-and-forward' for MQ clients?

What solutions do exist for this problem, in the case of multiple PC1?

Does 'store-and-forward’ functionality available in default configuration JBOSS and JMS?


Thank you,
Alex.

[adrian.brock]

No the correct name is MessageBridge.
It is on the TODO list waiting for a volunteer (no user questions please)
http://jboss.org/index.html?module=bb&op=viewtopic&t=46193

Store and Forward is what e-mail clients do.

I'm also interested in supporting this sort of "Work off-line" mode where the
client stores sent messages on disk until the JMS Server becomes available.