JMS session pooling for large number of topic subscribers

I am writing an application that will create many JMS theme subscribers. What's the best practice for reusing sessions?

Session per subscriber? Session pool? With a session per subscriber, the number of threads seems unreasonable. Does this work for something like ServerSessionPool? What I've seen so far seems to suggest that the ServerSessionPool is geared more towards receiving a single receiver receiving messages at the same time, rather than multiple receivers.

I am currently working with HornetQ 2.0.0GA embedded in JBoss EAP 4.3.0CP6.

+2


a source to share


1 answer


You will most likely need a lot of sessions since the session is a stream. Here's a link to a really good answer that explains the context.



In the unlikely event that JMS topic subscriptions are on the same thread, note that they will all share the same unit of work if it is a transaction session.

+1


a source







All Articles