There is an event handler in the ATM example that reports the status
(/process/sequence/scope):
<scope name="connectedScope">
| [...]
| <eventHandlers>
| <onMessage operation="status" partnerLink="frontEnd"
portType="atm:atm"
| variable="sessionMsg">
| <correlations>
| <correlation set="sessionInteraction" />
| </correlations>
|
| <sequence name="statusSequence">
| [...]
| <reply operation="status" partnerLink="frontEnd"
portType="atm:atm"
| variable="statusRsp" />
| </sequence>
| </onMessage>
| </eventHandlers>
| </scope>
Anyway, when the test client requests the status, the instance isn't busy
executing the normal path, so it doesn't hit the issue you describe. It makes
sense: JMS delivers a session's messages serially. An activity in the normal
path receives a message. It resumes execution and, at the same time, an event
message arrives. The normal path completes and the scope tries to close event
listeners, because it thinks no events are pending; the event message has not
been delivered yet.
I don't fully understand why the consumer.close() call blocks. It is supposed
to block until a listener in progress completes, but in this case the session
has not delivered the message. Does the consumer "see" it has a pending
message? I need to investigate more.
Once again, thanks for your help.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922439#3922439
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922439
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
