P
Paul Connaughton
Guest
Hi Stefan, It depends on when the error is raised. If the error in the log occurred while the client was in a wait-for, listening for the next message, then the error would eventually be reported asynchronously through the errorConsumer. If the error in the log occurred while the listener was processing a message (either making ABL or ABL/JMS calls) then it would be a synchronous run-time condition and either an ABL STOP or ERROR condition could be raised. Bottom line, if you want to bullet proof your ABL/JMS listener from any type of connection loss then you need to implement the complete strategy shown in the sample subscriber code at the bottom of the article. Another option would be to upgrade your Sonic brokers to a new version and a fault tolerance license. You can then make use of the setFaultTolerant() ABL/JMS call which was introduced in OE 10.x with the symbiotic ClientConnect/ServerConnect adapters. HTH,
Continue reading...
Continue reading...