> The concept of Resource Limit in SwiftMQ is very useful
> but it is also somewhat restricting. In our case, we
> want to be able to pool our QueueSessions and retrieve
> a QueueSession from the pool in a round-robin fashion.
> However, since the resource limit increments even if we
> are sending to the same destination but on a different
> QueueSession (retrieved at random from the pool), we
> would reach the resource maximum at some point.
> My question is, is it possible to disable this feature?
The resources are incremented as they are consumed. So when you touch a
given limit you have consumed the resources at the router. When you send
unidentified to destinations via different sessions then you create a
producer on the router for every session/destination combination because
a producer depends on a session (it is created from it). That's how it
is. So if you touch the limit you've specified, you have 2 ways to
resolve it: increase the limit or use another approach in your
application.
--
Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/