Under what conditions and to what extent does SwiftMQ make use of
multi-threading in the context of the JMS Publisher/Subscriber model?
>From docs "ThreadpoolSwiftlet" (net.connection) and "NetworkSwiftlet"
(net.tcp.mode) i understand that the maximum of concurrency is to have one
thread per connection (= TopicConnection?).
What if one TopicSession creates multiple instances of TopicSubscriber,
subscribing to different topics? Is it possible to have messages received on
different topics be processed by different threads concurrently?
If so, what's about Topics related to each other in a Topic Hierarchy as
descibed in doc "JMS Implementation Notes"? (Example: If two TopicSubscriber
instances (assume ts1, ts2) within the same TopicSession subscribe to
iit.sales.EU and iit.sales, will messages published on iit.sales be
processed by a single thread (running ts1 and ts2 one after the other) or
two different threads (running ts1 and ts2 concurrently)?)
Background: To guarantee the right order of message delivery, concurrency
must be utilized with care. On the other hand, in some applications
concurrency can be desirable to improve performance.
.........................................
Mit freundlichem Gruß / With kind regards
Alexander Ortloff
Siemens AG
Transportation Systems
Rail Automation
System Development
TS RA SD 11
Ackerstr. 22
D-38126 Braunschweig
Germany
Fon: +49 531 226 2536, ... 5423
Fax: +49 531 2277 2536
MailTo:[EMAIL PROTECTED]
------------------------------------------------------
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/
