TWM client message publishing behavior.
Article ID: KB0089509
Updated On:
| Products | Versions |
|---|---|
| TIBCO Web Messaging for TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
By design, when the client connection to the TWM server is dropped, trying to call MessageProducer -> send() will block forever until the connection is restored.
When calling a TWM client API from within a GUI application which typically runs the code from the main UI thread, the user interface will be blocked when send() is called and the connection is dropped. We suggest calling send() from within a background thread other than the main UI thread. Note that trying to call the send() method on the same MessageProducer while the previous send() has not returned will result in an IllegalStateException of "Message send already in progress".
By design, when the client connection to the TWM server is dropped, trying to call MessageProducer -> send() will block forever until the connection is restored.
When calling a TWM client API from within a GUI application which typically runs the code from the main UI thread, the user interface will be blocked when send() is called and the connection is dropped. We suggest calling send() from within a background thread other than the main UI thread. Note that trying to call the send() method on the same MessageProducer while the previous send() has not returned will result in an IllegalStateException of "Message send already in progress".
Issue/Introduction
TWM client message publishing behavior.
Additional Information
Feedback
Yes
No
Powered by
