[
https://issues.apache.org/activemq/browse/AMQNET-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56104#action_56104
]
Jim Gomes commented on AMQNET-213:
----------------------------------
This new behavior of needing to call connection.Start() caused me some trouble,
too. I spent about a day or so tracking down what was wrong. Code that was
working, suddenly stopped working. I think we need to clearly call out this
behavior in the release notes for 1.2.0.
> selector not working anymore
> ----------------------------
>
> Key: AMQNET-213
> URL: https://issues.apache.org/activemq/browse/AMQNET-213
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ
> Affects Versions: 1.2.0
> Reporter: Palm Kevin
> Assignee: Jim Gomes
>
> When I try to commit a message (which connection and session already has been
> closed), then previously I executed this code:
> {quote}
> Public Sub Commit(ByVal message As IMessage)
> Using connection As IConnection = Me.CreateIncomingConnection()
> Using session As ISession =
> connection.CreateSession(AcknowledgementMode.AutoAcknowledge)
> Dim consumer =
> session.CreateConsumer(message.NMSDestination, "NMSMessageID='" +
> message.NMSMessageId + "'")
> Dim fetchedMessage =
> consumer.Receive(TimeSpan.FromMilliseconds(100))
> If fetchedMessage Is Nothing Then _
> Throw New Exception("Unable to commit message: cannot
> find message with id '" + message.NMSMessageId + "'")
> consumer.Close()
> End Using
> End Using
> End Sub
> {quote}
> Now, my code always throws the exception because the searched message cannot
> be found!
> This code is *working with release 1.1.0*. but it *doens't work with Trunk*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
