-
1. Re: WAN
timfox Jun 9, 2006 2:00 PM (in response to jaink)If you are referring to running a cluster of jboss messaging servers across LAN, WAN or internet, then the answer is that 1.0 doesn't support clustering, it is a single server release.
Clustering across a LAN is due in 1.2, across WAN / internet in 1.4. -
2. Re: WAN
jaink Jun 9, 2006 2:17 PM (in response to jaink)I was refering to server to server communication without clustering them. Apologize for not being detailed.
Thanks. -
3. Re: WAN
timfox Jun 9, 2006 2:38 PM (in response to jaink)I'm not sure what you mean by "server to server communication without clustering", can you explain?
-
4. Re: WAN
jaink Jun 12, 2006 6:36 AM (in response to jaink)One JMS Server to another JMS Server across LAN.
-
5. Re: WAN
timfox Jun 12, 2006 10:03 AM (in response to jaink)"jaink" wrote:
One JMS Server to another JMS Server across LAN.
I don't understand.
What other reason than clustering would one JMS server contact another server?
Can you explain your use case in more detail please. -
6. Re: WAN
jaink Jun 13, 2006 7:05 AM (in response to jaink)We will have JMS Clients in different geographical location across WAN who would be connecting to their local JMS Servers. These JMS Servers will have to communicate (one server becoming client to another server). The Servers will not be on the same cluster.
-
7. Re: WAN
timfox Jun 13, 2006 9:57 AM (in response to jaink)Still don't get it.
How can one jms server "act" as a client to another server.
This is certainly not part of the jms spec. -
8. Re: WAN
timfox Jun 13, 2006 10:20 AM (in response to jaink)Perhaps you mean you have jms clients that communicate with a local server, then another jms client on the same node as the local server talks with another JMS server across a WAN.
-
9. Re: WAN
xenomino Jun 27, 2006 1:25 PM (in response to jaink)Ok timefox, remember JINI? A user (call him user A), would ask server A for a .jar file. Server A would look to see if he had it. If not, server A would ask Servers B, C, D ... Z for the .jar file. The server who had that .jar file would send it to server A. Server A would cache it, and send a copy to user A.
Now, lets see how we could do that with JMS! user A asks for all subscribe-able topics. Server A asks servers A through Z for thier topics and presents a list to user A. User A subscribes to topic Q on server Q. So, server A subscribes to topic Q on server Q and when a message is published to topic Q, the message is sent from the publishing user, to server Q, to server A, to user A.
This is what we're trying to do, which appears a chore, especially when you add in PKI requirements.