qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
Date Wed, 24 Oct 2012 20:14:14 GMT

    [ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483546#comment-13483546
] 

Robbie Gemmell commented on QPID-4389:
--------------------------------------

Hi Andrew,

The issue is actually client side as Alex mentioned, so the change made on trunk doesnt involve
the broker.

The use of the Binding URL format is a workaround if you dont want to update to the latest
client, as using BindingURL destination format the issue shouldnt occur (and its proably worth
mentioning that in addition to the full syntax outlined on the page, you should jsut be able
to use "BURL:your.topic.name" and it will use the amq.topic exchange by default, or set the
system property as Alex outlined so that you can emit the BURL: prefix). How your program
is written probably shouldnt need to change, just the values used for your destinations.

Robbie
                
> 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, qpid.log
>
>
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message