You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mark Gellings (JIRA)" <ji...@apache.org> on 2010/11/19 22:53:25 UTC
[jira] Commented: (AMQNET-218) NMS session should dispose
appropriately if listener delegate still processing message
[ https://issues.apache.org/activemq/browse/AMQNET-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63422#action_63422 ]
Mark Gellings commented on AMQNET-218:
--------------------------------------
Out of curiosity did logic change in regards to dispose/close and aborting the thread since Feb 2010? Perhaps related to AMQNET-242?
It seems as if when you don't set the Dispose/CloseStopTimeouts on the Session it defaults to 30s now.
Just wondering because what didn't work with my more complex code now is working fine. :)
> NMS session should dispose appropriately if listener delegate still processing message
> --------------------------------------------------------------------------------------
>
> Key: AMQNET-218
> URL: https://issues.apache.org/activemq/browse/AMQNET-218
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: NMS
> Affects Versions: 1.2.0
> Environment: ActiveMQ 5.2
> Reporter: Mark Gellings
> Assignee: Timothy Bish
> Fix For: 1.2.0
>
>
> We have a unit test working with NMS 1.1 and not with NMS 1.2.
> It appears that in v1.2 on Session.Dispose the consumer thread is not aborted properly. If I'm processing a message say that takes 2 minutes to complete and try and dispose the session it waits the full two minutes.
> With v1.1 if disposing on the session, it aborted after a timeout of 30s. Calling dispose on the message consumer directly would behave as calling dispose on the session is in v1.2.
> This is a problem if the consumer runs in a windows service as the SCM errors out when a user tries to shut down the service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.