WebLogic 6.1 does not support JMS Clustering at all. So you will not be able to do things like automatic fail-over. I am sure you could hack something together but we all know how hacks go...
WebLogic 6.1 supports distributed destinations. Which basically means you pin the actual JMS destination to a server in the cluster in the rest point to it. This allows you to do things like deploying cluster-wide MDBs and such. It gives location transparency for the destination, meaning clients don't need to know on which server the destination is actually located. This of course means that if the server with the destination fails then you are in trouble.
In WLS 7.0 you can configure fail-over destinations but as of yet, the fail-over is a manual process. In a future release automatic fail-over for JMS has been promised. Doesn't do us much good right now does it?
Traditionally, JMS has always been the weakest link in WebLogic's clustering technology. If you really need robust messaging you could always use a third-party MOM, like Sonic MQ, which supports JMS Clustering. I find that most projects don't need that type of reliability though.
The problem with your suggestion is that there is no way to ensure that messages are not lost. If the provider goes down then any of the messages stored are not going to be migrated to the new provider.
[ December 01, 2002: Message edited by: Chris Mathews ]
