Hi!
This is my suggestion:
The following problem occurs only if router has a lot of messages in it's
backstore and you use asynchronous message delivery (MessageListener). I
think you should switch to synchronous message delivery
(queueConsumer.receive()) for the time being.
This problem should be corrected in the next release.
I hope this helps.
Best regards,
Kovi
At 16:10 22.6.01 +0200, you wrote:
>hi!
>
>it seems that the swiftmq router will not accept more connections, if one of
>the queue listeners' onMessage method throws an exception.
>
>after that, no clients can connect to SwiftMQ (including the smq explorer) -
>they hang in the jndi initial context lookup...
>
>I'm using SMQ 2.1.0 and persistent queues. Has anyone experienced this?
>what can i do?
> - catch all exceptions in onMessage?
> - is there a configuration setting to work around this (eg. threadpool
>settings)?
>
> viktor
>
>
>
>------------------------------------------------------
>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/
------------------------------------------------------
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/
