[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: JMS Chat Application
From:       Rob Davies <rajdavies () gmail ! com>
Date:       2008-03-31 8:10:45
Message-ID: DC6AA41A-67A1-4997-8DED-A0033ABCF5BF () gmail ! com
[Download RAW message or body]

inlined:
On 29 Mar 2008, at 00:50, francois1 wrote:

>
> Hi,
>
> My chat application needs to multicast messages to the proper chat  
> rooms. An
> important requirement is that clients must be able to subscribe and
> unsubscribe to/from chat rooms. It looks like that it could be done  
> with
> message selectors.
>
> Here is my tentative architecture:
>
> 1) 1 server runs the JMS provider that manages a topic (ActiveMQ)
> 2) a servers farm (maybe 5 nodes) relays messages between the JMS  
> provider
> and the clients (browsers)
> 3) each node of the servers farm opens 1 JMS topic connection to the  
> JMS
> provider
> 4) each JMS topic connection is used to spawn 1 JMS topic session  
> per client
> (possibly 2,000 per server)
>
> My questions are:
>
> 1) Is it OK to end up with 5 JMS topic connections (1 per node in the
> servers farm) and 5 x 2,000 = 10,000 JMS sessions? Isn’t it too many?
That shouldn't be a big deal
>
> 2) Should I go for plain JMS API, or do you think that Spring can  
> help me? I
> have tried to use Spring JMS templates and message listeners, but I  
> have
> struggled with the management of resources (create / kill sessions,  
> launch /
> stop message listeners).
I Spring makes things easy - but see http://activemq.apache.org/spring-support.html
and in particular http://activemq.apache.org/jmstemplate-gotchas.html
>
>
> Any other comment is welcome.
>
> Thank you,
> Francois
> -- 
> View this message in context: http://www.nabble.com/JMS-Chat-Application-tp16365161s2354p16365161.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


[prev in list] [next in list] [prev in thread] [next in thread]