You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JMS spec says that if you have a thread that is both a consumer and a producer of messages then you need a session for each task. In JMSBroadcaster a single session is being shared for both these tasks. When using WebSphere MQ this causes an exception when creating the TextMessage for publishing.
The simple fix is to create two sessions in the setUp method one for publishing and one for consuming.
The text was updated successfully, but these errors were encountered:
The fix look good to me but I don't have the setup to test it. If that works for you, just do a pull request and I will integrate in the current 0.9-SNAPSHOT
The JMS spec says that if you have a thread that is both a consumer and a producer of messages then you need a session for each task. In JMSBroadcaster a single session is being shared for both these tasks. When using WebSphere MQ this causes an exception when creating the TextMessage for publishing.
The simple fix is to create two sessions in the setUp method one for publishing and one for consuming.
The text was updated successfully, but these errors were encountered: