> Here is the output:
> $ ./starter SynchTopicExample1 testtopic
> Topic name is testtopic
> SUBSCRIBER THREAD: Waiting for message
> PUBLISHER THREAD: Publishing message 0: Here is a message
> SUBSCRIBER THREAD: Reading message: Here is a message
> SUBSCRIBER THREAD: Waiting for message
> PUBLISHER THREAD: Publishing message 1: Here is a message
> SUBSCRIBER THREAD: Reading message: Here is a message
> SUBSCRIBER THREAD: Waiting for message
> PUBLISHER THREAD: Publishing message 2: Here is a message
> SUBSCRIBER THREAD: Reading message: Here is a message
> SUBSCRIBER THREAD: Waiting for message
> SUBSCRIBER THREAD: timeout receiving message
> PUBLISHER THREAD: Publishing message 3: Here is a message
> PUBLISHER THREAD: Publishing message 4: Here is a message
> $
>
> As you can see, after the publisher sends out the 3rd message the
> subscriber times out. My expectation was that each receive() restarts
> the 30 second counter but what is shown is that the timeout is set
> in the first receive() and ignores the values passed in subsequent
> calls.
> Is this the expected behavior?
No. Expected is that it times out after that amount of ms you've
specified in receive(timeout). The timers in the current release are
implemented that way to create a new thread for each different interval.
This leads sometimes to timeouts which aren't exact. The new 3.0.0 has
already a completely new implementation of timers which are exact.
--
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/[email protected]/
