[
https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483348#comment-13483348
]
Andrew Burks commented on QPID-4389:
------------------------------------
After checking out the source code, building at the java sub-module, and
starting the server up, I am still running into the same issue where the second
message is not being picked up for some reason. Again, the first and last
messages are received no problem.
> Qpid topic exchange does not resend message when subsciber come back online
> ---------------------------------------------------------------------------
>
> Key: QPID-4389
> URL: https://issues.apache.org/jira/browse/QPID-4389
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.14
> Environment: Linux,Netbeans 7.2
> Reporter: Andrew Burks
> Assignee: Robbie Gemmell
> Labels: newbie
> Fix For: 0.19
>
> Attachments: DurSubProject.tar.gz
>
>
> When testing durable subscibers, I first publish a message to a subscriber to
> be sure it can receive messages. Checks out ok. Then I bring the subscriber
> down with subscriber.close() where subscriber is an instance of
> MessageConsumer. Next, I publish another message while the subscriber is
> down, then I bring the subsciber back up and wait 10 seconds for a
> message...no message comes. To be sure the everything is working properly, I
> create another message and publish it, the subscriber has no problem
> receiving it. My question is where has the second message gone? I would think
> that the message would have been queued up some place to be sent out again
> but that is not the case. Please let me know if I am looking at this totally
> wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
