[jira] [Updated] (QPID-2796) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-2796: -- Status: Ready To Review (was: In Progress) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client -- Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- 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-2796) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503707#comment-13503707 ] Rob Godfrey commented on QPID-2796: --- Added a system test: http://svn.apache.org/viewvc?rev=1413539view=rev [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client -- Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- 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-2796) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503723#comment-13503723 ] Rob Godfrey commented on QPID-2796: --- I've made a further check-in to address Robbie's review comments: http://svn.apache.org/viewvc?rev=1413549view=rev [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client -- Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Rob Godfrey Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- 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] [Assigned] (QPID-2796) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-2796: - Assignee: Robbie Gemmell (was: Rob Godfrey) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client -- Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- 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
Re: x-bindings misunderstanding
Hello Gordon,
Sorry about the last email, seems like stuff are working now, sort of.
But I think I found another problem, to make sure we are on the same path,
here is my Consumer again:
Queue receiverQ = session.createQueue(receiverQ; +
{create:always, auto-delete:true,
exclusive:true,
node:{x-bindings:[{exchange:'amq.topic', key:'producerQ'}]}});
MessageConsumer consumer = session.createConsumer(receiverQ);
consumer.setMessageListener(new MyMessageListener());
while(true){}
And my producer:
String ALTERNATE_EXCHANGE = amq.topic;
String requestsQueue =producerQ34; {create:always,
node:{x-declare:{auto-delete:true, exclusive:true, alternate-exchange:
'+ALTERNATE_EXCHANGE+'}}}; // +
Session session = createSession();
MessageProducer producer =
session.createProducer(session.createQueue(requestsQueue));
TextMessage message = session.createTextMessage(Some Payload);
producer.send(message);
Thread.sleep(10 * 1000);
Start broker, start Consumer, start Producer, kill Producer.
Expected: message will come into the Consumer I have.
De facto: It does.
Everything is fine in the case above.
Then, without restarting the broker:
Edit the key in the consumer:
Queue receiverQ = session.createQueue(receiverQ; +
{create:always, auto-delete:true,
exclusive:true,
node:{x-bindings:[{exchange:'amq.topic', key:'123producerQ456'}]}});
Start Consumer, start Producer, kill Producer.
Expected: because the routing key is different, the message should not come
into the consumer.
De facto : it does.
It looks like the broker does some caching, because if I re-start the
broker, and run the case above(case 2), no message hits my listener.
btw, I can post the code on bitbucket of alike, in case you need it.
I sent the logs also to your email.
Thank You,
Eugene.
--
View this message in context:
http://apache-qpid-developers.2158895.n2.nabble.com/x-bindings-misunderstanding-tp7583454p7583501.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Re: x-bindings misunderstanding
On 11/26/2012 11:20 AM, eugene wrote:
Hello Gordon,
Sorry about the last email, seems like stuff are working now, sort of.
But I think I found another problem, to make sure we are on the same path,
here is my Consumer again:
Queue receiverQ = session.createQueue(receiverQ; +
{create:always, auto-delete:true,
exclusive:true,
node:{x-bindings:[{exchange:'amq.topic', key:'producerQ'}]}});
MessageConsumer consumer = session.createConsumer(receiverQ);
consumer.setMessageListener(new MyMessageListener());
while(true){}
The problem is your receiverQ is not being created with auto-delete and
exclusive set. This means that the queue is not deleted when you restart
the consumer and because your binding are scoped to the node (i.e. match
the queues lifecycle) not the link, then both bindings will exist when
you have restarted the consumer.
The reason the queue is not auto-deleted is that your address is wrong.
The auto-delet and exclusive need to be within the node, and enclosed in
a x-declare, much as you do for the producer.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Re: x-bindings misunderstanding
:) ups..! Thank You Gordon, everything seems as expected right now. Thank You, Eugene. -- View this message in context: http://apache-qpid-developers.2158895.n2.nabble.com/x-bindings-misunderstanding-tp7583454p7583503.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-4472) NPE when connecting over AMQP 1.0 with no SASL layer
Gordon Sim created QPID-4472:
Summary: NPE when connecting over AMQP 1.0 with no SASL layer
Key: QPID-4472
URL: https://issues.apache.org/jira/browse/QPID-4472
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.20
Reporter: Gordon Sim
In doing some interop testing, I ran the c++ client (qpid::messaging) against
the java broker without a SASL layer, triggering a NullPointerException and
broker shutdown:
{noformat}
[Broker] BRK-1004 : Qpid Broker Ready
java.lang.NullPointerException
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.received(ProtocolEngine_1_0_0.java:280)
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.received(ProtocolEngine_1_0_0.java:49)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine$SelfDelegateProtocolEngine.received(MultiVersionProtocolEngine.java:556)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine$SelfDelegateProtocolEngine.received(MultiVersionProtocolEngine.java:442)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:118)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:37)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
at java.lang.Thread.run(Thread.java:722)
#
# Unhandled Exception java.lang.NullPointerException in Thread IoReceiver -
/127.0.0.1:59542
#
# Exiting
#
java.lang.NullPointerException
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.closed(ProtocolEngine_1_0_0.java:293)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:102)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
at java.lang.Thread.run(Thread.java:722)
{noformat}
--
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-4469) [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect()
[ https://issues.apache.org/jira/browse/QPID-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4469: - Status: Ready To Review (was: In Progress) [Java common] remove unused sslContext parameter from OutgoingNetworkTransport#connect() Key: QPID-4469 URL: https://issues.apache.org/jira/browse/QPID-4469 Project: Qpid Issue Type: Improvement Components: Java Client, Java Common Affects Versions: 0.14, 0.16, 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 OutgoingNetworkTransport#connect() takes an sslContext parameter. This is unused by the transport implementations because SSL is implemented in the client as a wrapper over the transport. The 0-10 path of the client supplies null for this arg, but the 08/0-9/0-9-1 patch still creates and supplies one. The parameter should be removed to ensure consistency now and in the future. -- 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-4472) NPE when connecting over AMQP 1.0 with no SASL layer
[
https://issues.apache.org/jira/browse/QPID-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503789#comment-13503789
]
Rob Godfrey commented on QPID-4472:
---
I've made a change to the Non-SASL AMQP 1.0 code which will hopefully address
this issue
Let me know if you continue to see problems
NPE when connecting over AMQP 1.0 with no SASL layer
Key: QPID-4472
URL: https://issues.apache.org/jira/browse/QPID-4472
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.20
Reporter: Gordon Sim
In doing some interop testing, I ran the c++ client (qpid::messaging) against
the java broker without a SASL layer, triggering a NullPointerException and
broker shutdown:
{noformat}
[Broker] BRK-1004 : Qpid Broker Ready
java.lang.NullPointerException
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.received(ProtocolEngine_1_0_0.java:280)
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.received(ProtocolEngine_1_0_0.java:49)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine$SelfDelegateProtocolEngine.received(MultiVersionProtocolEngine.java:556)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine$SelfDelegateProtocolEngine.received(MultiVersionProtocolEngine.java:442)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:118)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:37)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
at java.lang.Thread.run(Thread.java:722)
#
# Unhandled Exception java.lang.NullPointerException in Thread IoReceiver -
/127.0.0.1:59542
#
# Exiting
#
java.lang.NullPointerException
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.closed(ProtocolEngine_1_0_0.java:293)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:102)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
at java.lang.Thread.run(Thread.java:722)
{noformat}
--
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-4473) [Java Client] Resolve stream might not be closed issue reported by findbugs tool in JMSObjectMessage
Alex Rudyy created QPID-4473: Summary: [Java Client] Resolve stream might not be closed issue reported by findbugs tool in JMSObjectMessage Key: QPID-4473 URL: https://issues.apache.org/jira/browse/QPID-4473 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.18, 0.16 Reporter: Alex Rudyy Assignee: Alex Rudyy Priority: Minor Fix For: 0.21 Findbugs reports the error org.apache.qpid.client.message.JMSObjectMessage.read(ByteBuffer) may fail to close stream -- 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-4472) NPE when connecting over AMQP 1.0 with no SASL layer
[
https://issues.apache.org/jira/browse/QPID-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503795#comment-13503795
]
Gordon Sim commented on QPID-4472:
--
That certainly seems to prevent the NPE.
NPE when connecting over AMQP 1.0 with no SASL layer
Key: QPID-4472
URL: https://issues.apache.org/jira/browse/QPID-4472
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.20
Reporter: Gordon Sim
In doing some interop testing, I ran the c++ client (qpid::messaging) against
the java broker without a SASL layer, triggering a NullPointerException and
broker shutdown:
{noformat}
[Broker] BRK-1004 : Qpid Broker Ready
java.lang.NullPointerException
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.received(ProtocolEngine_1_0_0.java:280)
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.received(ProtocolEngine_1_0_0.java:49)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine$SelfDelegateProtocolEngine.received(MultiVersionProtocolEngine.java:556)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine$SelfDelegateProtocolEngine.received(MultiVersionProtocolEngine.java:442)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:118)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:37)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161)
at java.lang.Thread.run(Thread.java:722)
#
# Unhandled Exception java.lang.NullPointerException in Thread IoReceiver -
/127.0.0.1:59542
#
# Exiting
#
java.lang.NullPointerException
at
org.apache.qpid.server.protocol.ProtocolEngine_1_0_0.closed(ProtocolEngine_1_0_0.java:293)
at
org.apache.qpid.server.protocol.MultiVersionProtocolEngine.closed(MultiVersionProtocolEngine.java:102)
at
org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222)
at java.lang.Thread.run(Thread.java:722)
{noformat}
--
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-4473) [Java Client] Resolve stream might not be closed issue reported by findbugs tool in JMSObjectMessage
[ https://issues.apache.org/jira/browse/QPID-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-4473: - Status: Ready To Review (was: In Progress) [Java Client] Resolve stream might not be closed issue reported by findbugs tool in JMSObjectMessage -- Key: QPID-4473 URL: https://issues.apache.org/jira/browse/QPID-4473 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.16, 0.18 Reporter: Alex Rudyy Assignee: Alex Rudyy Priority: Minor Fix For: 0.21 Findbugs reports the error org.apache.qpid.client.message.JMSObjectMessage.read(ByteBuffer) may fail to close stream -- 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] [Assigned] (QPID-4473) [Java Client] Resolve stream might not be closed issue reported by findbugs tool in JMSObjectMessage
[ https://issues.apache.org/jira/browse/QPID-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-4473: Assignee: Robbie Gemmell (was: Alex Rudyy) Robbie, Could you please review the change? [Java Client] Resolve stream might not be closed issue reported by findbugs tool in JMSObjectMessage -- Key: QPID-4473 URL: https://issues.apache.org/jira/browse/QPID-4473 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.16, 0.18 Reporter: Alex Rudyy Assignee: Robbie Gemmell Priority: Minor Fix For: 0.21 Findbugs reports the error org.apache.qpid.client.message.JMSObjectMessage.read(ByteBuffer) may fail to close stream -- 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-4474) ensure the BDBHAMessageStore JMX MBean name is quoted
Robbie Gemmell created QPID-4474: Summary: ensure the BDBHAMessageStore JMX MBean name is quoted Key: QPID-4474 URL: https://issues.apache.org/jira/browse/QPID-4474 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Fix For: 0.21 Ensure the BDBHAMessageStore JMX MBean name is quoted. The name of the other MBeans (Virtualhost, Queue, Exchange) are quoted to allow them to contain names which cant be encoded in an JMX ObjectName without use of quotes. The BDBHAMessageStore should also have its name quoted, for the same reasons and also for consistency with the other MBeans. -- 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] [Assigned] (QPID-4474) ensure the BDBHAMessageStore JMX MBean name is quoted
[ https://issues.apache.org/jira/browse/QPID-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPID-4474: Assignee: Robbie Gemmell ensure the BDBHAMessageStore JMX MBean name is quoted - Key: QPID-4474 URL: https://issues.apache.org/jira/browse/QPID-4474 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 Ensure the BDBHAMessageStore JMX MBean name is quoted. The name of the other MBeans (Virtualhost, Queue, Exchange) are quoted to allow them to contain names which cant be encoded in an JMX ObjectName without use of quotes. The BDBHAMessageStore should also have its name quoted, for the same reasons and also for consistency with the other MBeans. -- 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-4474) ensure the BDBHAMessageStore JMX MBean name is quoted
[ https://issues.apache.org/jira/browse/QPID-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-4474: - Status: Ready To Review (was: In Progress) ensure the BDBHAMessageStore JMX MBean name is quoted - Key: QPID-4474 URL: https://issues.apache.org/jira/browse/QPID-4474 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 Ensure the BDBHAMessageStore JMX MBean name is quoted. The name of the other MBeans (Virtualhost, Queue, Exchange) are quoted to allow them to contain names which cant be encoded in an JMX ObjectName without use of quotes. The BDBHAMessageStore should also have its name quoted, for the same reasons and also for consistency with the other MBeans. -- 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-4474) ensure the BDBHAMessageStore JMX MBean name is quoted
[ https://issues.apache.org/jira/browse/QPID-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503833#comment-13503833 ] Robbie Gemmell commented on QPID-4474: -- Change made via http://svn.apache.org/viewvc?rev=1413676view=rev ensure the BDBHAMessageStore JMX MBean name is quoted - Key: QPID-4474 URL: https://issues.apache.org/jira/browse/QPID-4474 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.18 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 Ensure the BDBHAMessageStore JMX MBean name is quoted. The name of the other MBeans (Virtualhost, Queue, Exchange) are quoted to allow them to contain names which cant be encoded in an JMX ObjectName without use of quotes. The BDBHAMessageStore should also have its name quoted, for the same reasons and also for consistency with the other MBeans. -- 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] [Resolved] (QPID-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved QPID-4415. Resolution: Fixed perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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] [Closed] (QPID-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce closed QPID-4415. -- perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503853#comment-13503853 ] Darryl L. Pierce commented on QPID-4415: Thank you! I've applied and test this patch. In addition to removing DESTDIR it seems to have fixed the problem, from what I see in my tests. perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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
Request for including in 0.20
QPID-4415: perl bindings installed in wrong place The fix is small and only impacts the Makefile.am for Qpid bindings. I've tested it and it appears to work properly. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgp4lZR3VRnZK.pgp Description: PGP signature
[jira] [Commented] (QPID-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503869#comment-13503869 ] Justin Ross commented on QPID-4448: --- http://svn.apache.org/viewvc?view=revisionrevision=1412239 Andrew, please review for 0.18 inclusion. Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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] [Assigned] (QPID-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned QPID-4448: - Assignee: Andrew Stitcher (was: Gordon Sim) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4449: -- Fix Version/s: 0.20 Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4448: -- Fix Version/s: 0.20 Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4449: -- Assignee: Ken Giusti (was: Ted Ross) Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503870#comment-13503870 ] Justin Ross commented on QPID-4449: --- http://svn.apache.org/viewvc?view=revisionrevision=1411761 Ken, please review for 0.20 inclusion. Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4448) Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault
[ https://issues.apache.org/jira/browse/QPID-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503869#comment-13503869 ] Justin Ross edited comment on QPID-4448 at 11/26/12 4:27 PM: - http://svn.apache.org/viewvc?view=revisionrevision=1412239 Andrew, please review for 0.20 inclusion. was (Author: justi9): http://svn.apache.org/viewvc?view=revisionrevision=1412239 Andrew, please review for 0.18 inclusion. Credit checking messages for sending on 0-10 of messages from 1.0 results in seg fault -- Key: QPID-4448 URL: https://issues.apache.org/jira/browse/QPID-4448 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.19 Reporter: Gordon Sim Assignee: Andrew Stitcher Fix For: 0.19, 0.20 thus restricting 1.0-0-10 interop -- 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-4451) Need to wait for outgoing messages to settle when calling Connection::close()
[ https://issues.apache.org/jira/browse/QPID-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503873#comment-13503873 ] Justin Ross commented on QPID-4451: --- This change is confined to the AMQP 1.0 path. Approved for 0.20. Need to wait for outgoing messages to settle when calling Connection::close() - Key: QPID-4451 URL: https://issues.apache.org/jira/browse/QPID-4451 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4452) issuing and handling of producer credit not implemented
[ https://issues.apache.org/jira/browse/QPID-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503874#comment-13503874 ] Justin Ross commented on QPID-4452: --- The change confined to the AMQP 1.0 code. Approved for 0.20. issuing and handling of producer credit not implemented --- Key: QPID-4452 URL: https://issues.apache.org/jira/browse/QPID-4452 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 Prevents proper stress testing. -- 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-4452) issuing and handling of producer credit not implemented
[ https://issues.apache.org/jira/browse/QPID-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503874#comment-13503874 ] Justin Ross edited comment on QPID-4452 at 11/26/12 4:33 PM: - http://svn.apache.org/viewvc?view=revisionrevision=1412242 The change confined to the AMQP 1.0 code. Approved for 0.20. was (Author: justi9): The change confined to the AMQP 1.0 code. Approved for 0.20. issuing and handling of producer credit not implemented --- Key: QPID-4452 URL: https://issues.apache.org/jira/browse/QPID-4452 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 Prevents proper stress testing. -- 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-4452) issuing and handling of producer credit not implemented
[ https://issues.apache.org/jira/browse/QPID-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503874#comment-13503874 ] Justin Ross edited comment on QPID-4452 at 11/26/12 4:33 PM: - http://svn.apache.org/viewvc?view=revisionrevision=1412242 The change is confined to the AMQP 1.0 code. Approved for 0.20. was (Author: justi9): http://svn.apache.org/viewvc?view=revisionrevision=1412242 The change confined to the AMQP 1.0 code. Approved for 0.20. issuing and handling of producer credit not implemented --- Key: QPID-4452 URL: https://issues.apache.org/jira/browse/QPID-4452 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 Prevents proper stress testing. -- 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-4453) [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message.
[ https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-4453: -- Fix Version/s: 0.20 [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message. --- Key: QPID-4453 URL: https://issues.apache.org/jira/browse/QPID-4453 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.18 Reporter: Hiram Chirino Assignee: Rob Godfrey Fix For: 0.20, 0.21 Attachments: QPID-4453.patch The following test case fails: ObjectMessage message = senderSession.createObjectMessage(); sender.send(message); Message msg = receiver.receive(TestConfig.TIMEOUT); Assert.assertTrue(The message should be an instance of ObjectMessage.\n, msg instanceof ObjectMessage); -- 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-4453) [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message.
[ https://issues.apache.org/jira/browse/QPID-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503877#comment-13503877 ] Justin Ross commented on QPID-4453: --- http://svn.apache.org/viewvc?view=revisionrevision=1412270 Patch reviewed by Rob. Approved for 0.20. [AMQP 1.0 JMS Client] ObjectMessage /w no body improperly converted to an AMQP message. --- Key: QPID-4453 URL: https://issues.apache.org/jira/browse/QPID-4453 Project: Qpid Issue Type: Bug Components: Java Client Affects Versions: 0.18 Reporter: Hiram Chirino Assignee: Rob Godfrey Fix For: 0.20, 0.21 Attachments: QPID-4453.patch The following test case fails: ObjectMessage message = senderSession.createObjectMessage(); sender.send(message); Message msg = receiver.receive(TestConfig.TIMEOUT); Assert.assertTrue(The message should be an instance of ObjectMessage.\n, msg instanceof ObjectMessage); -- 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-4455) [AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503880#comment-13503880
]
Justin Ross commented on QPID-4455:
---
http://svn.apache.org/viewvc?view=revisionrevision=1412280
Patch reviewed by Rob. Approved for 0.20.
[AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
Key: QPID-4455
URL: https://issues.apache.org/jira/browse/QPID-4455
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Hiram Chirino
Assignee: Rob Godfrey
Fix For: 0.20, 0.21
Attachments: QPID-4455.patch
The following test case is failing:
MessageProducer p = session.createProducer(queue);
TextMessage message = session.createTextMessage();
message.setText(hello);
p.send(message);
QueueBrowser browser = session.createBrowser(queue);
Enumeration enumeration = browser.getEnumeration();
while (enumeration.hasMoreElements()) {
Message m = (Message) enumeration.nextElement();
assertTrue(m instanceof TextMessage);
}
--
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-4455) [AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
[
https://issues.apache.org/jira/browse/QPID-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4455:
--
Fix Version/s: 0.20
[AMQP 1.0 JMS Client] Queue browsers were not returning jms messages
Key: QPID-4455
URL: https://issues.apache.org/jira/browse/QPID-4455
Project: Qpid
Issue Type: Bug
Components: Java Client
Reporter: Hiram Chirino
Assignee: Rob Godfrey
Fix For: 0.20, 0.21
Attachments: QPID-4455.patch
The following test case is failing:
MessageProducer p = session.createProducer(queue);
TextMessage message = session.createTextMessage();
message.setText(hello);
p.send(message);
QueueBrowser browser = session.createBrowser(queue);
Enumeration enumeration = browser.getEnumeration();
while (enumeration.hasMoreElements()) {
Message m = (Message) enumeration.nextElement();
assertTrue(m instanceof TextMessage);
}
--
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-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503886#comment-13503886 ] Justin Ross commented on QPID-4456: --- The first change, from Robbie's initial comment, is reviewed by Rob and approved for 0.20. update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Keith Wall Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- 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-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503895#comment-13503895 ] Justin Ross commented on QPID-4415: --- Hi, Darryl. Please add a comment with a link to the svn change. I didn't see it in the inclusion request mail. perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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-4459) Sender doesn't settle messages
[ https://issues.apache.org/jira/browse/QPID-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503897#comment-13503897 ] Justin Ross commented on QPID-4459: --- http://svn.apache.org/viewvc?view=revisionrevision=1412960 Confined to AMQP 1.0 implemenation. Approved for 0.20. Sender doesn't settle messages -- Key: QPID-4459 URL: https://issues.apache.org/jira/browse/QPID-4459 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4460) after drain, full credit is not replenished
[ https://issues.apache.org/jira/browse/QPID-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503898#comment-13503898 ] Justin Ross commented on QPID-4460: --- http://svn.apache.org/viewvc?view=revisionrevision=1412961 Confined to AMQP 1.0 impl. Approved for 0.20. after drain, full credit is not replenished --- Key: QPID-4460 URL: https://issues.apache.org/jira/browse/QPID-4460 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4464) broker does not set container name on AMQP 1.0 connection open
[ https://issues.apache.org/jira/browse/QPID-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503901#comment-13503901 ] Justin Ross commented on QPID-4464: --- http://svn.apache.org/viewvc?view=revisionrevision=1412962 Reviewed by me and approved for 0.20. broker does not set container name on AMQP 1.0 connection open -- Key: QPID-4464 URL: https://issues.apache.org/jira/browse/QPID-4464 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4465) only send subject filter if subject is specified
[ https://issues.apache.org/jira/browse/QPID-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503902#comment-13503902 ] Justin Ross commented on QPID-4465: --- http://svn.apache.org/viewvc?view=revisionrevision=1412963 Confined to AMQP 1.0 impl. Approved for 0.20. only send subject filter if subject is specified Key: QPID-4465 URL: https://issues.apache.org/jira/browse/QPID-4465 Project: Qpid Issue Type: Bug Components: C++ Client Affects Versions: 0.20 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.20 -- 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-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503937#comment-13503937 ] Darryl L. Pierce commented on QPID-4415: Sorry. Here's the link: http://svn.apache.org/viewvc?view=revisionrevision=1413693 perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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-4415) perl bindings installed in wrong place
[ https://issues.apache.org/jira/browse/QPID-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503971#comment-13503971 ] Justin Ross commented on QPID-4415: --- Reviewed by me. Approved for 0.20. perl bindings installed in wrong place -- Key: QPID-4415 URL: https://issues.apache.org/jira/browse/QPID-4415 Project: Qpid Issue Type: Bug Affects Versions: 0.18 Reporter: Jimmy Jones Assignee: Darryl L. Pierce Attachments: 0001-QPID-4415-Fixes-Perl-bindings-install-location.patch, perl-bindings-path.patch On Ubuntu 12.04, if I run configure --prefix=/usr the bindings get installed into /usr/usr/lib/perl5... However if I run make install from bindings/qpid/perl they get correctly installed. On RHEL5 the same issues occurs, but additionally the architecture string is incorrectly put twice into the path /usr/lib/perl/5.14/x86_64-linux-gnu-thread-multi/x86_64-linux-gnu-thread-multi -- 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
Review Request: Patch to allow proton to compile in C++
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8223/ --- Review request for qpid, Andrew Stitcher, Kenneth Giusti, and Rafael Schloming. Description --- See PROTON-159. Note: this edited patch will not compile and run. See the JIRA for the full patch and important background notes. This addresses bug PROTON-159. https://issues.apache.org/jira/browse/PROTON-159 Diffs - http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/CMakeLists.txt 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/bindings/python/CMakeLists.txt 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/examples/messenger/c/CMakeLists.txt 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/examples/messenger/c/recv.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/include/proton/engine.h 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/include/proton/ssl.h 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/include/proton/util.h 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/buffer.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/codec/codec.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/dispatcher/dispatcher.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/driver.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/engine/engine.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/message/message.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/messenger.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/proton.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/sasl/sasl.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/scanner.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/sys/io.h PRE-CREATION http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/sys/posix/io.c PRE-CREATION http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/types.c 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/util.h 1413444 http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/src/util.c 1413444 Diff: https://reviews.apache.org/r/8223/diff/ Testing --- RHEL 6.3 (64 bit) gcc and g++ each in Release and Debug cmake builds. proton-test, send/recv. Thanks, Cliff Jansen
Re: Review Request: QPID-4424 - prevent multiple threads from processing PollableQueue events simultaneously
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8147/#review13748 --- Ship it! Ship It! - Cliff Jansen On Nov. 23, 2012, 11:43 p.m., Steve Huston wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/8147/ --- (Updated Nov. 23, 2012, 11:43 p.m.) Review request for qpid, Andrew Stitcher, Chug Rolke, and Cliff Jansen. Description --- This change prevents multiple threads from processing events at the same time. They can be enqueued by multiple threads but not dispatched. This addresses bug QPID-4424. https://issues.apache.org/jira/browse/QPID-4424 Diffs - http://svn.apache.org/repos/asf/qpid/trunk/qpid/cpp/src/qpid/sys/windows/PollableCondition.cpp 1412730 Diff: https://reviews.apache.org/r/8147/diff/ Testing --- Original test case from QPID-4424. Thanks, Steve Huston
[jira] [Commented] (QPID-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504021#comment-13504021 ] Ken Giusti commented on QPID-4449: -- Justin/Ted - is the intent to deprecate the old non-shared-ptr API in favor of the new shared-ptr API? The changes look fine, btw - just curious as to the intent of the new method. -K Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504027#comment-13504027 ] Ted Ross commented on QPID-4449: Ken, The new shared-ptr interface is needed for the agent-in-the-broker. The original change forced all users to move to the shared-ptr API, including users of the stand-alone QMF Agent. QPID-4449 reverts the stand-alone agent API to be unchanged while allowing the in-broker agent to use the shared-ptr API for easier memory management of objects. -Ted Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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-4449) Fix for QPID-4286 changed the standalone qmf-agent API
[ https://issues.apache.org/jira/browse/QPID-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504048#comment-13504048 ] Justin Ross commented on QPID-4449: --- Reviewed by Ken. Approved for 0.20. Fix for QPID-4286 changed the standalone qmf-agent API -- Key: QPID-4449 URL: https://issues.apache.org/jira/browse/QPID-4449 Project: Qpid Issue Type: Bug Components: Qpid Managment Framework Affects Versions: 0.19 Reporter: Ted Ross Assignee: Ken Giusti Fix For: 0.19, 0.20, 0.21 The changes to qpid/trunk/qpid/cpp/include/qpid/management/Manageable.h cause applications that use the stand-alone qmf agent API to need to adapt. This file needs to be changed to provide backward compatibility for users of the API. -- 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
0.20 request roundup
The requests so far: - Ted - https://issues.apache.org/jira/browse/QPID-4449 - http://svn.apache.org/viewvc?rev=1411761view=rev - Approved - Gordon - https://issues.apache.org/jira/browse/QPID-4448 - http://svn.apache.org/viewvc?rev=1412239view=rev - Out for review, Andrew - https://issues.apache.org/jira/browse/QPID-4451 - http://svn.apache.org/viewvc?rev=1412241view=rev - Approved - https://issues.apache.org/jira/browse/QPID-4452 - http://svn.apache.org/viewvc?rev=1412242view=rev - Approved - https://issues.apache.org/jira/browse/QPID-4459 - http://svn.apache.org/viewvc?rev=1412960view=rev - Approved - https://issues.apache.org/jira/browse/QPID-4460 - http://svn.apache.org/viewvc?rev=1412961view=rev - Approved - https://issues.apache.org/jira/browse/QPID-4464 - http://svn.apache.org/viewvc?rev=1412962view=rev - Approved - https://issues.apache.org/jira/browse/QPID-4465 - http://svn.apache.org/viewvc?rev=1412963view=rev - Approved - Rob - https://issues.apache.org/jira/browse/QPID-4453 - http://svn.apache.org/viewvc?view=revisionrevision=1412270 - Approved - https://issues.apache.org/jira/browse/QPID-4455 - http://svn.apache.org/viewvc?view=revisionrevision=1412280 - Approved - Robbie - https://issues.apache.org/jira/browse/QPID-4456 - http://svn.apache.org/viewvc?rev=1412359view=rev - First part approved; second part out for review, Keith - NO-JIRA - http://svn.apache.org/viewvc?rev=1411615view=rev - Approved - NO-JIRA - http://svn.apache.org/viewvc?rev=1412358view=rev - Approved - Darryl - https://issues.apache.org/jira/browse/QPID-4415 - http://svn.apache.org/viewvc?view=revisionrevision=1413693 - Approved Let me know if I missed anything. Since we're still early in the release close down, where I was sufficiently confident, either because the change was isolated or straightforward, I approved without waiting for additional review. Thanks! Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.20 release update - beta is available
I've tested the qpid-java-0.20-beta.tar.gz binary that was built on 19 November and found no problems. I didn't test qpid-java-broker-0.20-beta.tar.gz because it is missing some jars, as mentioned by Robbie previously in this thread. Tested successfully: - Start broker with the following options: -p port -m jmxregistryport -l log4jFile --jmxconnectorport jmxconnectorport - Send and receive JMS messages using the Java client - Log in via JMX and web UI - View some messages via JMX and web UI - qpid.stop script - Broker log looks sane. Environment: - Linux Mint 12, x86_64 - Java: Oracle 1.6.0_29 Phil On 20 November 2012 00:56, Justin Ross jr...@redhat.com wrote: Hi. The beta distribution is available now from revision 1411386 of the release branch. http://people.apache.org/~**jross/qpid-0.20-beta/http://people.apache.org/~jross/qpid-0.20-beta/ I did some simple build and test runs of the cpp and java components on Fedora 16 x86-64. There was only one failure, concerning ssl_test in the cpp tests. http://people.apache.org/~**jross/qpid-0.20-beta-testing.**txthttp://people.apache.org/~jross/qpid-0.20-beta-testing.txt Please give the beta a try and report what you find. RC1 is set for 28 November. Thanks, Justin --- 0.20 release page: https://cwiki.apache.org/qpid/**020-release.htmlhttps://cwiki.apache.org/qpid/020-release.html --**--**- To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.**orgdev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
[
https://issues.apache.org/jira/browse/QPID-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston resolved QPID-4424.
Resolution: Fixed
Fix Version/s: 0.21
Fixed on trunk r1413889.
Requesting permission to merge to 0.20 branch. The change was reviewed on
review board by Andrew Stitcher and Cliff Jansen.
C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line
136
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system
Visual Studio 2010 32-bit executable
Reporter: Chuck Rolke
Assignee: Steve Huston
Priority: Blocker
Fix For: 0.21
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
qpidbrokerd.dll!qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
::dispatch(qpid::sys::PollableCondition cond={...}) Line 136 + 0x36
bytes C++
qpidbrokerd.dll!boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
* p=0x00c72b80, qpid::sys::PollableCondition a1={...}) Line 165 + 0x10
bytes C++
qpidbrokerd.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list1qpid::sys::PollableCondition (boost::_bi::typevoid
__formal={...},
boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition f={...},
boost::_bi::list1qpid::sys::PollableCondition a={...},
boost::_bi::typevoid __formal={...}) Line 314C++
qpidbrokerd.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()qpid::sys::PollableCondition(qpid::sys::PollableCondition
a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ,void,qpid::sys::PollableCondition
::invoke(boost::detail::function::function_buffer function_obj_ptr={...},
qpid::sys::PollableCondition a0={...}) Line 154 C++
qpidcommond.dll!boost::function1void,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableCondition a0={...}) Line 760 + 0x1a
bytes C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytes
C++
qpidcommond.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list1qpid::sys::windows::AsynchIoResult *
(boost::_bi::typevoid __formal={...},
boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
* f={...}, boost::_bi::list1qpid::sys::windows::AsynchIoResult *
a={...}, boost::_bi::typevoid __formal={...}) Line 314 C++
Re: FW: [jira] [Resolved] (QPID-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
Thanks, Steve. Approved.
On Mon, 26 Nov 2012, Steve Huston wrote:
Hi Justin,
Requesting permission to merge this fix to 0.20 - the jira is marked a blocker
and the fix was reviewed by Andrew and Cliff.
Thanks,
-Steve
-Original Message-
From: Steve Huston (JIRA) [mailto:j...@apache.org]
Sent: Monday, November 26, 2012 5:05 PM
To: Steve Huston
Subject: [jira] [Resolved] (QPID-4424) C++ Broker on Windows - Assertion
Failed: !dispatcher - PollableQueue.h line 136
[
https://issues.apache.org/jira/browse/QPID-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston resolved QPID-4424.
Resolution: Fixed
Fix Version/s: 0.21
Fixed on trunk r1413889.
Requesting permission to merge to 0.20 branch. The change was reviewed on
review board by Andrew Stitcher and Cliff Jansen.
C++ Broker on Windows - Assertion Failed: !dispatcher -
C++ PollableQueue.h line 136
--
--
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system Visual
Studio 2010 32-bit executable
Reporter: Chuck Rolke
Assignee: Steve Huston
Priority: Blocker
Fix For: 0.21
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
qpidbrokerd.dll!qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
::dispatch(qpid::sys::PollableCondition cond={...}) Line 136 + 0x36 bytes C++
qpidbrokerd.dll!boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
* p=0x00c72b80, qpid::sys::PollableCondition a1={...}) Line 165 + 0x10 bytes C++
qpidbrokerd.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message *,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message ,qpid::sys::PollableCondition
,boost::_bi::list1qpid::sys::PollableCondition (boost::_bi::typevoid __formal={...},
boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message ,qpid::sys::PollableCondition f={...},
boost::_bi::list1qpid::sys::PollableCondition a={...}, boost::_bi::typevoid __formal={...}) Line 314 C++
qpidbrokerd.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ::operator()qpid::sys::PollableCondition(qpid::sys::PollableCondition a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ,void,qpid::sys::PollableCondition ::invoke(boost::detail::function::function_buffer function_obj_ptr={...},
qpid::sys::PollableCondition a0={...}) Line 154 C++
qpidcommond.dll!boost::function1void,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableCondition a0={...}) Line 760 + 0x1a bytes C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytesC++
qpidcommond.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate *,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list1qpid::sys::windows::AsynchIoResult *
[jira] [Commented] (QPID-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
[
https://issues.apache.org/jira/browse/QPID-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504200#comment-13504200
]
Justin Ross commented on QPID-4424:
---
https://reviews.apache.org/r/8147/
Approved for 0.20.
C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line
136
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system
Visual Studio 2010 32-bit executable
Reporter: Chuck Rolke
Assignee: Steve Huston
Priority: Blocker
Fix For: 0.20, 0.21
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
qpidbrokerd.dll!qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
::dispatch(qpid::sys::PollableCondition cond={...}) Line 136 + 0x36
bytes C++
qpidbrokerd.dll!boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
* p=0x00c72b80, qpid::sys::PollableCondition a1={...}) Line 165 + 0x10
bytes C++
qpidbrokerd.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list1qpid::sys::PollableCondition (boost::_bi::typevoid
__formal={...},
boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition f={...},
boost::_bi::list1qpid::sys::PollableCondition a={...},
boost::_bi::typevoid __formal={...}) Line 314C++
qpidbrokerd.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()qpid::sys::PollableCondition(qpid::sys::PollableCondition
a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ,void,qpid::sys::PollableCondition
::invoke(boost::detail::function::function_buffer function_obj_ptr={...},
qpid::sys::PollableCondition a0={...}) Line 154 C++
qpidcommond.dll!boost::function1void,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableCondition a0={...}) Line 760 + 0x1a
bytes C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytes
C++
qpidcommond.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list1qpid::sys::windows::AsynchIoResult *
(boost::_bi::typevoid __formal={...},
boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
* f={...}, boost::_bi::list1qpid::sys::windows::AsynchIoResult *
a={...}, boost::_bi::typevoid __formal={...}) Line 314 C++
qpidcommond.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
[jira] [Updated] (QPID-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
[
https://issues.apache.org/jira/browse/QPID-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-4424:
--
Fix Version/s: 0.20
C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line
136
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system
Visual Studio 2010 32-bit executable
Reporter: Chuck Rolke
Assignee: Steve Huston
Priority: Blocker
Fix For: 0.20, 0.21
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
qpidbrokerd.dll!qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
::dispatch(qpid::sys::PollableCondition cond={...}) Line 136 + 0x36
bytes C++
qpidbrokerd.dll!boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
* p=0x00c72b80, qpid::sys::PollableCondition a1={...}) Line 165 + 0x10
bytes C++
qpidbrokerd.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list1qpid::sys::PollableCondition (boost::_bi::typevoid
__formal={...},
boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition f={...},
boost::_bi::list1qpid::sys::PollableCondition a={...},
boost::_bi::typevoid __formal={...}) Line 314C++
qpidbrokerd.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()qpid::sys::PollableCondition(qpid::sys::PollableCondition
a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ,void,qpid::sys::PollableCondition
::invoke(boost::detail::function::function_buffer function_obj_ptr={...},
qpid::sys::PollableCondition a0={...}) Line 154 C++
qpidcommond.dll!boost::function1void,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableCondition a0={...}) Line 760 + 0x1a
bytes C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytes
C++
qpidcommond.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list1qpid::sys::windows::AsynchIoResult *
(boost::_bi::typevoid __formal={...},
boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
* f={...}, boost::_bi::list1qpid::sys::windows::AsynchIoResult *
a={...}, boost::_bi::typevoid __formal={...}) Line 314 C++
qpidcommond.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1 ::operator()qpid::sys::windows::AsynchIoResult
[jira] [Resolved] (QPID-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-4456. -- Resolution: Fixed Changes look fine to me. update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Keith Wall Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- 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] [Closed] (QPID-4456) update the Java broker-only release package to account for changes in plugin system
[ https://issues.apache.org/jira/browse/QPID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-4456. update the Java broker-only release package to account for changes in plugin system --- Key: QPID-4456 URL: https://issues.apache.org/jira/browse/QPID-4456 Project: Qpid Issue Type: Task Components: Packaging Affects Versions: 0.19 Reporter: Robbie Gemmell Assignee: Keith Wall Priority: Blocker Fix For: 0.20 Following the simplification of the plugin system in the Java broker via QPID-4335 and the modifications to the tests in QPID-4353, the plugins are not being packaged in the broker-only release binary (as per discussion on QPID- just prior to the 0.20 beta). The build system should be updated to account for the changes and ensure the plugins are again included. -- 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-4424) C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line 136
[
https://issues.apache.org/jira/browse/QPID-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504246#comment-13504246
]
Steve Huston commented on QPID-4424:
Merged to 0.20 at r1413945
C++ Broker on Windows - Assertion Failed: !dispatcher - PollableQueue.h line
136
Key: QPID-4424
URL: https://issues.apache.org/jira/browse/QPID-4424
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.18
Environment: Windows Server 2008 R2 64-bit system
Visual Studio 2010 32-bit executable
Reporter: Chuck Rolke
Assignee: Steve Huston
Priority: Blocker
Fix For: 0.20, 0.21
Start broker with 'qpidd --auth no --no-data-dir'.
Sit for 15 or so seconds. No external connections from clients. No cluster.
Assert happens.
Stack at assert time:
msvcr100d.dll!_NMSG_WRITE(int rterrnum=10) Line 217C
msvcr100d.dll!abort() Line 61 + 0x7 bytes C
msvcr100d.dll!_wassert(const wchar_t * expr=0x5ff25504, const wchar_t *
filename=0x5ff25480, unsigned int lineno=136) Line 153 C
qpidbrokerd.dll!qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
::dispatch(qpid::sys::PollableCondition cond={...}) Line 136 + 0x36
bytes C++
qpidbrokerd.dll!boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
* p=0x00c72b80, qpid::sys::PollableCondition a1={...}) Line 165 + 0x10
bytes C++
qpidbrokerd.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list1qpid::sys::PollableCondition (boost::_bi::typevoid
__formal={...},
boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition f={...},
boost::_bi::list1qpid::sys::PollableCondition a={...},
boost::_bi::typevoid __formal={...}) Line 314C++
qpidbrokerd.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1
::operator()qpid::sys::PollableCondition(qpid::sys::PollableCondition
a1={...}) Line 33 C++
qpidbrokerd.dll!boost::detail::function::void_function_obj_invoker1boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
,qpid::sys::PollableCondition
,boost::_bi::list2boost::_bi::valueqpid::sys::PollableQueuestd::pairboost::shared_ptrqpid::broker::Exchange,qpid::broker::Message
*,boost::arg1 ,void,qpid::sys::PollableCondition
::invoke(boost::detail::function::function_buffer function_obj_ptr={...},
qpid::sys::PollableCondition a0={...}) Line 154 C++
qpidcommond.dll!boost::function1void,qpid::sys::PollableCondition
::operator()(qpid::sys::PollableCondition a0={...}) Line 760 + 0x1a
bytes C++
qpidcommond.dll!qpid::sys::PollableConditionPrivate::dispatch(qpid::sys::windows::AsynchIoResult
* result=0x00cad6e0) Line 81 C++
qpidcommond.dll!boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*::operator()(qpid::sys::PollableConditionPrivate * p=0x00c72cd0,
qpid::sys::windows::AsynchIoResult * a1=0x00cad6e0) Line 165 + 0x10 bytes
C++
qpidcommond.dll!boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1
::operator()boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list1qpid::sys::windows::AsynchIoResult *
(boost::_bi::typevoid __formal={...},
boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
* f={...}, boost::_bi::list1qpid::sys::windows::AsynchIoResult *
a={...}, boost::_bi::typevoid __formal={...}) Line 314 C++
qpidcommond.dll!boost::_bi::bind_tvoid,boost::_mfi::mf1void,qpid::sys::PollableConditionPrivate,qpid::sys::windows::AsynchIoResult
*,boost::_bi::list2boost::_bi::valueqpid::sys::PollableConditionPrivate
*,boost::arg1
[jira] [Resolved] (QPID-2796) [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client
[ https://issues.apache.org/jira/browse/QPID-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-2796. -- Resolution: Fixed Looks good to me. [Java] implement support for heartbeats following IO changes to the 0-8/0-9/0-9-1/0-10 broker and 0-8/0-9/0-9-1 client -- Key: QPID-2796 URL: https://issues.apache.org/jira/browse/QPID-2796 Project: Qpid Issue Type: Bug Components: Java Broker, Java Client Affects Versions: 0.15 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.21 The Java broker and client are not able to generate AMQP heartbeats following the updates to their IO layer. The 0-8/0-9/0-9-1 codepaths previously relied on the Mina IO layer to support this, and as such can no longer do so. The 0-10 path of the Java broker leverages much of the 0-10 implementation in common originally developed for the 0-10 Java client, which simply reflects heartbeats it receives from a broker and as such no heartbeats will ever be sent by broker or the client despite its support. -- 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
