[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501167#comment-13501167 ] Andrew Burks commented on QPID-: One last inquiry, when using qpid-config I could specify the max-queue-count in number of messages, how is this accomplished in the Qpid Management web console? QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Assignee: Justin Ross Labels: newbie Attachments: config.xml I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) Java broker queue creation questions
[
https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501235#comment-13501235
]
Andrew Burks commented on QPID-:
{quote}(Its worth me noting: on the Java broker these settings are only used to
provide alerting (log file [viewable via the web ui], JMX notifications) and
are not hard limits).{quote}
Was this the case before the limited/incomplete QMFv1 support was removed in
the java broker?
Java broker queue creation questions
Key: QPID-
URL: https://issues.apache.org/jira/browse/QPID-
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.19
Environment: linux
Reporter: Andrew Burks
Assignee: Justin Ross
Labels: newbie
Attachments: config.xml
I have checked out the updated source code (up to revision 1411028) and when
executing qpid-config -a guest/guest@protoqpid:5672, I receive the error
Failed: RuntimeError: Timed out waiting for broker to synchronize.
Note: protoqpid is just an alias to localhost
--
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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) Java broker queue creation questions
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501259#comment-13501259 ] Andrew Burks commented on QPID-: Ok, then is there a plan to add this functionality? If not, that is fine. I am just wondering at this point. Java broker queue creation questions Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Assignee: Justin Ross Labels: newbie Attachments: config.xml I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500212#comment-13500212 ] Andrew Burks commented on QPID-: I have gotten past my initial issue. I had a few environment variables pointing to the older version of qpid I was using. Now the error I receive is Failed: NotFound: no such queue: qmf.default.topic, which leads me to believe that I have missed a setup script or something of that nature. QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500538#comment-13500538 ] Andrew Burks commented on QPID-: Ok, so is there something special that I need to do in order to set up the web console? I have tried http://localhost:8080/management, but my browser was unable to connect, so I changed the port number from 8080 to 5672 (the default port in which my broker is running on) and then I receive a white page with these characters: AMQP��� . Any idea what this means? QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500538#comment-13500538 ] Andrew Burks edited comment on QPID- at 11/19/12 7:34 PM: -- Ok, so is there something special that I need to do in order to set up the web console? I have tried http://localhost:8080/management, but my browser was unable to connect, so I changed the port number from 8080 to 5672 (the default port in which my broker is running on) and then I receive a pretty much blank white page with these characters: AMQP��� . Any idea what this means? was (Author: aburks18): Ok, so is there something special that I need to do in order to set up the web console? I have tried http://localhost:8080/management, but my browser was unable to connect, so I changed the port number from 8080 to 5672 (the default port in which my broker is running on) and then I receive a white page with these characters: AMQP��� . Any idea what this means? QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500590#comment-13500590 ] Andrew Burks commented on QPID-: I am using yhe trunk broker. And I have checked out my log file and I do not see any errors. QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500598#comment-13500598 ] Andrew Burks commented on QPID-: No. This is what I have when I start the broker: [Broker] BRK-1006 : Using configuration : /cots/qpid-0.20/trunk/qpid/java/broker/release/qpid-broker-0.19/etc/config.xml [Broker] BRK-1007 : Using logging configuration : /cots/qpid-0.20/trunk/qpid/java/broker/release/qpid-broker-0.19/etc/log4j.xml [Broker] BRK-1001 : Startup : Version: 0.19 Build: 1411311 [Broker] BRK-1010 : Platform : JVM : Sun Microsystems Inc. version: 1.6.0_25-b06 OS : Linux version: 3.6.5-2.fc16.x86_64 arch: amd64 [Broker] BRK-1011 : Maximum Memory : 1,065,025,536 bytes [Broker] BRK-1002 : Starting : Listening on TCP port 5672 [Broker] BRK-1004 : Qpid Broker Ready QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500590#comment-13500590 ] Andrew Burks edited comment on QPID- at 11/19/12 8:13 PM: -- I am using the trunk broker. And I have checked out my log file and I do not see any errors. was (Author: aburks18): I am using yhe trunk broker. And I have checked out my log file and I do not see any errors. QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500618#comment-13500618 ] Andrew Burks commented on QPID-: I have not touched the config.xml file (not even to apply your proposed changes) but I am attaching nonetheless QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie Attachments: config.xml I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Burks updated QPID-: --- Attachment: config.xml QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie Attachments: config.xml I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500637#comment-13500637 ] Andrew Burks commented on QPID-: So now everything says 0.21. Can I get the revision number that the 0.20 beta was cut at because I am getting a java.lang.Error: Properties init: Could not determine current working directory error QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie Attachments: config.xml I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4444) QPID Broker fails when running qpid-config command
Andrew Burks created QPID-: -- Summary: QPID Broker fails when running qpid-config command Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499978#comment-13499978 ] Andrew Burks commented on QPID-: Ultimately I plan to creates queues via a shell script QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-4444) QPID Broker fails when running qpid-config command
[ https://issues.apache.org/jira/browse/QPID-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499978#comment-13499978 ] Andrew Burks edited comment on QPID- at 11/19/12 12:51 AM: --- Ultimately I plan to create queues via a shell script was (Author: aburks18): Ultimately I plan to creates queues via a shell script QPID Broker fails when running qpid-config command -- Key: QPID- URL: https://issues.apache.org/jira/browse/QPID- Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.19 Environment: linux Reporter: Andrew Burks Labels: newbie I have checked out the updated source code (up to revision 1411028) and when executing qpid-config -a guest/guest@protoqpid:5672, I receive the error Failed: RuntimeError: Timed out waiting for broker to synchronize. Note: protoqpid is just an alias to localhost -- 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13484110#comment-13484110 ] Andrew Burks commented on QPID-4389: Thanks Alex, the dependency layout is what I needed to know. I will let you know what I come up with. Again, thanks Alex and Robbie for bearing with me. 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13484147#comment-13484147 ] Andrew Burks commented on QPID-4389: I've just tested my scenario out and it worked perfectly. Thanks. 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Burks updated QPID-4389: --- Attachment: qpid.log I have attached the log if it helps any 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Burks updated QPID-4389: --- Attachment: (was: qpid.log) 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Burks updated QPID-4389: --- Comment: was deleted (was: I have attached the log if it helps any) 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Burks updated QPID-4389: --- Attachment: qpid.log I have attached the log if it helps any 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483577#comment-13483577 ] Andrew Burks commented on QPID-4389: Ok, so if the issue is with the client, then how am I supposed to test it? 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
Andrew Burks created QPID-4389: -- Summary: 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 Broker Affects Versions: 0.14 Environment: Linux,Netbeans 7.2 Reporter: Andrew Burks 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-4389) Qpid topic exchange does not resend message when subsciber come back online
[ https://issues.apache.org/jira/browse/QPID-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Burks updated QPID-4389: --- Attachment: DurSubProject.tar.gz Attached a test project to show my steps 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 Broker Affects Versions: 0.14 Environment: Linux,Netbeans 7.2 Reporter: Andrew Burks Labels: newbie 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: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
