On Thu, Jan 16, 2014 at 12:30 PM, Ilya Kazakevich <
ilya.kazakev...@jetbrains.com> wrote:
>
> There is a servlet container with many concurrent users. Each user request
> works in its own thread from pool (tomcat is used)
> There is also ApacheMQ server that routes messages for users via JMS.
>
T
o), and (b) that only durable subscriptions ever persist messages. In
other words, non-durable Topic subscriptions will lose messages on broker
restarts.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connect-ApacheMQ-with-web-application-using-JMS-tp4676387p4676418.html
2014/1/16 Ilya Kazakevich :
> Hello,
>
>>-Original Message-
>>From: Jose María Zaragoza [mailto:demablo...@gmail.com]
>>Sent: Thursday, January 16, 2014 11:30 PM
>>To: users
>>Subject: Re: Connect ApacheMQ with web application using JMS
>
>
Hello,
>-Original Message-
>From: Jose María Zaragoza [mailto:demablo...@gmail.com]
>Sent: Thursday, January 16, 2014 11:30 PM
>To: users
>Subject: Re: Connect ApacheMQ with web application using JMS
>A Connection is thread safe, but Sessions, MessageProducers, and
2014/1/16 Ilya Kazakevich :
> We have 2 ideas:
>
> * Use one Connection and one Session for the whole web-app, create consumer
> for each user and store it in user session. Each time user opens page we do
> receiveNoWait and obtain all messages she got.
>
> * Fetch all messages from all consumers o
Hello,
There is a servlet container with many concurrent users. Each user request
works in its own thread from pool (tomcat is used)
There is also ApacheMQ server that routes messages for users via JMS.
To send message to user Mary you need to use topic "users.Mary".
So, web server subscribes to
