[jira] [Created] (PROTON-1408) long-lived connections suffer large performance hit after many messages
michael goulish created PROTON-1408: --- Summary: long-lived connections suffer large performance hit after many messages Key: PROTON-1408 URL: https://issues.apache.org/jira/browse/PROTON-1408 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: michael goulish In long-running soak tests, in which connections are never taken down, I am seeing a sudden & severe performance degradation when the number of messages over the connection reaches about 6.4 billion. This is happening in tests with two senders, two receivers & one router intermediating. I have tried C libUV clients as well as CPP clients. Behavior is not identical, but I see sudden performance drop, ie. 8x throughput decrease or worse, in both cases. Alan / Ted / Ken see an issue in use of improper comparison logic in pn_do_disposition(), in transport.c . I am trying to prove this now. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-637) system_tests_sasl_plain and system_tests_deprecated fail when cyrus-sasl-plain is not installed
[ https://issues.apache.org/jira/browse/DISPATCH-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-637. Resolution: Fixed Fix Version/s: 0.8.0 > system_tests_sasl_plain and system_tests_deprecated fail when > cyrus-sasl-plain is not installed > --- > > Key: DISPATCH-637 > URL: https://issues.apache.org/jira/browse/DISPATCH-637 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Eric Sammons >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > The current readme for dispatch and qpid-proton do not mention a dependency > on cyrus-sasl-plain; however, with out the cyrus-sasl-plain package the > system_tests_sasl_plain and system_tests_deprecated tests will fail. > README should mention this dependency. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-637) system_tests_sasl_plain and system_tests_deprecated fail when cyrus-sasl-plain is not installed
[ https://issues.apache.org/jira/browse/DISPATCH-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872469#comment-15872469 ] ASF subversion and git services commented on DISPATCH-637: -- Commit 6ebae2e63e52163bc9742c0a02f6b610cad01e9d in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=6ebae2e ] DISPATCH-637 - Added cyrus-sasl libraries to the list of to-be-installed libraries > system_tests_sasl_plain and system_tests_deprecated fail when > cyrus-sasl-plain is not installed > --- > > Key: DISPATCH-637 > URL: https://issues.apache.org/jira/browse/DISPATCH-637 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Eric Sammons >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > The current readme for dispatch and qpid-proton do not mention a dependency > on cyrus-sasl-plain; however, with out the cyrus-sasl-plain package the > system_tests_sasl_plain and system_tests_deprecated tests will fail. > README should mention this dependency. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1403) c proactor library
[ https://issues.apache.org/jira/browse/PROTON-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872448#comment-15872448 ] ASF subversion and git services commented on PROTON-1403: - Commit d5c0152a71ea889c4f3688b78dd323e705796c83 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d5c0152 ] PROTON-1403: Add missing qpid-proton-proactor library configuration > c proactor library > -- > > Key: PROTON-1403 > URL: https://issues.apache.org/jira/browse/PROTON-1403 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18.0 > > > Move the libuv proactor example into an installed library. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPIDJMS-264) Incoming messages are dispatched out of order
[
https://issues.apache.org/jira/browse/QPIDJMS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872428#comment-15872428
]
Timothy Bish edited comment on QPIDJMS-264 at 2/17/17 8:04 PM:
---
Pretty sure this is the underlying issue. If you could retest with a snapshot
build to confirm that'd be great or wait until 0.21.0 which will have this fix.
QPIDJMS-266
was (Author: tabish121):
Pretty sure this is the underlying issue. If you could retest with a snapshot
build to confirm that'd be great or wait until 0.21.0 which will have this fix.
> Incoming messages are dispatched out of order
> --
>
> Key: QPIDJMS-264
> URL: https://issues.apache.org/jira/browse/QPIDJMS-264
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.20.0
>Reporter: Alex Rudyy
>Priority: Critical
> Attachments: out-of-order-issue.tar.gz, out-of-order.log.tgz
>
>
> Both current trunk version and version 0.20.0 of JMS Client can dispatch
> incoming messages out of order into client application. I did not test
> earlier versions. The messages are received in the right order but Client
> dispatches them occasionally out of order.
> I used the following code to reproduce the issue with trunk version of Java
> Broker.
> {code}
> public static void main(String[] args) throws Exception
> {
> for (int i=0;i<100;i++)
> {
> execute(i);
> }
> }
> public static void execute(int iteration) throws Exception
> {
> System.out.println("Iteration " + iteration);
> Connection managingConnection = createConnection();
> Session session =
> managingConnection.createSession(Session.SESSION_TRANSACTED);
> Connection consumingConnection = createConnection();
> Session consumerSession = consumingConnection.createSession(true,
> Session.SESSION_TRANSACTED);
> Queue queue = createTestQueue(session, "Q3-test");
> session.commit();
> MessageConsumer consumer = consumerSession.createConsumer(queue);
> Connection producingConnection = createConnection();
> Session producerSession = producingConnection.createSession(true,
> Session.SESSION_TRANSACTED);
> MessageProducer producer = producerSession.createProducer(queue);
> producer.send(producerSession.createTextMessage("msg1"));
> producer.send(producerSession.createTextMessage("msg2"));
> producer.send(producerSession.createTextMessage("msg3"));
> producer.send(producerSession.createTextMessage("msg4"));
> producerSession.commit();
> consumingConnection.start();
> TextMessage tm = (TextMessage) consumer.receive();
> System.out.println(">" + tm.getText());
> if (!"msg1".equals(tm.getText()))
> {
> throw new RuntimeException("Unexpected");
> }
> deleteQueue(session, "Q3-test");
> consumingConnection.close();
> producingConnection.close();
> managingConnection.close();
> }
> private static Queue createTestQueue(Session session, String queueName)
> throws JMSException
> {
> MessageProducer producer =
> session.createProducer(session.createQueue("$management"));
> MapMessage createMessage = session.createMapMessage();
> createMessage.setStringProperty("type", "org.apache.qpid.Queue");
> createMessage.setStringProperty("operation", "CREATE");
> createMessage.setString("name", queueName);
> createMessage.setString("object-path", "org.apache.qpid.Queue");
> producer.send(createMessage);
> if (session.getTransacted())
> {
> session.commit();
> }
> return session.createQueue(queueName);
> }
> private static void deleteQueue(Session session, String queueName)throws
> JMSException
> {
> MessageProducer producer =
> session.createProducer(session.createQueue("$management"));
> MapMessage createMessage = session.createMapMessage();
> createMessage.setStringProperty("type", "org.apache.qpid.Queue");
> createMessage.setStringProperty("operation", "DELETE");
> createMessage.setStringProperty("index", "object-path");
> createMessage.setStringProperty("key", queueName);
> producer.send(createMessage);
> if (session.getTransacted())
> {
> session.commit();
> }
> }
> private static Connection createConnection() throws JMSException,
> NamingException {
> Properties properties = new Properties();
> properties.put("java.naming.factory.initial",
> "org.apache.qpid.jms.jndi.JmsInitialContextFactory");
> properties.put("connection
[jira] [Comment Edited] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872429#comment-15872429 ] Timothy Bish edited comment on QPIDJMS-239 at 2/17/17 8:03 PM: --- Pretty sure this is the underlying issue. If you could retest with a snapshot build to confirm that'd be great or wait until 0.21.0 which will have this fix. QPIDJMS-266 was (Author: tabish121): Pretty sure this is the underlying issue. If you could retest with a snapshot build to confirm that'd be great or wait until 0.21.0 which will have this fix. > Client ack session occasionally seen to redeliver recovered messages out of > order > - > > Key: QPIDJMS-239 > URL: https://issues.apache.org/jira/browse/QPIDJMS-239 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.11.0, 0.20.0 >Reporter: Keith Wall > Attachments: > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0_proton.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.txt > > > Test org.apache.qpid.test.unit.ack.RecoverTest#testOrderingWithAsyncConsumer > [1] fails occasional when run against the Java Broker. The test publishes a > number of messages then uses an async message listener to consume them. For > each message, the message listener recovers the session five times before > finally acknowledging the message, then the cycle repeats. In failure case, > I see the Qpid JMS Client delivery an unexpected message to the application > after a sequence of expected. > We have seen the failure on the Apache CI and I can reproduce the problem on > my laptop (every 15-20 runs of the test). > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-MMS-1.0/40/artifact/trunk/systests/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.txt > I have reproduced locally against 0.20.0 too. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-264) Incoming messages are dispatched out of order
[
https://issues.apache.org/jira/browse/QPIDJMS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872428#comment-15872428
]
Timothy Bish commented on QPIDJMS-264:
--
Pretty sure this is the underlying issue. If you could retest with a snapshot
build to confirm that'd be great or wait until 0.21.0 which will have this fix.
> Incoming messages are dispatched out of order
> --
>
> Key: QPIDJMS-264
> URL: https://issues.apache.org/jira/browse/QPIDJMS-264
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.20.0
>Reporter: Alex Rudyy
>Priority: Critical
> Attachments: out-of-order-issue.tar.gz, out-of-order.log.tgz
>
>
> Both current trunk version and version 0.20.0 of JMS Client can dispatch
> incoming messages out of order into client application. I did not test
> earlier versions. The messages are received in the right order but Client
> dispatches them occasionally out of order.
> I used the following code to reproduce the issue with trunk version of Java
> Broker.
> {code}
> public static void main(String[] args) throws Exception
> {
> for (int i=0;i<100;i++)
> {
> execute(i);
> }
> }
> public static void execute(int iteration) throws Exception
> {
> System.out.println("Iteration " + iteration);
> Connection managingConnection = createConnection();
> Session session =
> managingConnection.createSession(Session.SESSION_TRANSACTED);
> Connection consumingConnection = createConnection();
> Session consumerSession = consumingConnection.createSession(true,
> Session.SESSION_TRANSACTED);
> Queue queue = createTestQueue(session, "Q3-test");
> session.commit();
> MessageConsumer consumer = consumerSession.createConsumer(queue);
> Connection producingConnection = createConnection();
> Session producerSession = producingConnection.createSession(true,
> Session.SESSION_TRANSACTED);
> MessageProducer producer = producerSession.createProducer(queue);
> producer.send(producerSession.createTextMessage("msg1"));
> producer.send(producerSession.createTextMessage("msg2"));
> producer.send(producerSession.createTextMessage("msg3"));
> producer.send(producerSession.createTextMessage("msg4"));
> producerSession.commit();
> consumingConnection.start();
> TextMessage tm = (TextMessage) consumer.receive();
> System.out.println(">" + tm.getText());
> if (!"msg1".equals(tm.getText()))
> {
> throw new RuntimeException("Unexpected");
> }
> deleteQueue(session, "Q3-test");
> consumingConnection.close();
> producingConnection.close();
> managingConnection.close();
> }
> private static Queue createTestQueue(Session session, String queueName)
> throws JMSException
> {
> MessageProducer producer =
> session.createProducer(session.createQueue("$management"));
> MapMessage createMessage = session.createMapMessage();
> createMessage.setStringProperty("type", "org.apache.qpid.Queue");
> createMessage.setStringProperty("operation", "CREATE");
> createMessage.setString("name", queueName);
> createMessage.setString("object-path", "org.apache.qpid.Queue");
> producer.send(createMessage);
> if (session.getTransacted())
> {
> session.commit();
> }
> return session.createQueue(queueName);
> }
> private static void deleteQueue(Session session, String queueName)throws
> JMSException
> {
> MessageProducer producer =
> session.createProducer(session.createQueue("$management"));
> MapMessage createMessage = session.createMapMessage();
> createMessage.setStringProperty("type", "org.apache.qpid.Queue");
> createMessage.setStringProperty("operation", "DELETE");
> createMessage.setStringProperty("index", "object-path");
> createMessage.setStringProperty("key", queueName);
> producer.send(createMessage);
> if (session.getTransacted())
> {
> session.commit();
> }
> }
> private static Connection createConnection() throws JMSException,
> NamingException {
> Properties properties = new Properties();
> properties.put("java.naming.factory.initial",
> "org.apache.qpid.jms.jndi.JmsInitialContextFactory");
> properties.put("connectionfactory.myFactoryLookup",
> "amqp://localhost:5672");
> Context context = new InitialContext(properties);
> try
> {
> ConnectionFactory factory = (ConnectionFactory)
> context.lookup("myFactoryLookup");
>
[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order
[ https://issues.apache.org/jira/browse/QPIDJMS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872429#comment-15872429 ] Timothy Bish commented on QPIDJMS-239: -- Pretty sure this is the underlying issue. If you could retest with a snapshot build to confirm that'd be great or wait until 0.21.0 which will have this fix. > Client ack session occasionally seen to redeliver recovered messages out of > order > - > > Key: QPIDJMS-239 > URL: https://issues.apache.org/jira/browse/QPIDJMS-239 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.11.0, 0.20.0 >Reporter: Keith Wall > Attachments: > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0_proton.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer_0.20.0.txt, > > TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.txt > > > Test org.apache.qpid.test.unit.ack.RecoverTest#testOrderingWithAsyncConsumer > [1] fails occasional when run against the Java Broker. The test publishes a > number of messages then uses an async message listener to consume them. For > each message, the message listener recovers the session five times before > finally acknowledging the message, then the cycle repeats. In failure case, > I see the Qpid JMS Client delivery an unexpected message to the application > after a sequence of expected. > We have seen the failure on the Apache CI and I can reproduce the problem on > my laptop (every 15-20 runs of the test). > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-MMS-1.0/40/artifact/trunk/systests/target/surefire-reports/java-mms.1-0/TEST-org.apache.qpid.test.unit.ack.RecoverTest.testOrderingWithAsyncConsumer.txt > I have reproduced locally against 0.20.0 too. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDJMS-266) Race on session start and message dispatch can deliver messages in wrong order
[ https://issues.apache.org/jira/browse/QPIDJMS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-266. -- Resolution: Fixed > Race on session start and message dispatch can deliver messages in wrong order > -- > > Key: QPIDJMS-266 > URL: https://issues.apache.org/jira/browse/QPIDJMS-266 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.20.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.21.0 > > > If a connection is started in which consumer have been created and messages > are incoming a call to start can end in a race where on incoming message can > jump the line and be delivered ahead of previously queued messages. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-266) Race on session start and message dispatch can deliver messages in wrong order
[ https://issues.apache.org/jira/browse/QPIDJMS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872419#comment-15872419 ] ASF subversion and git services commented on QPIDJMS-266: - Commit 1b8f246553816947f8bab66b522ec6f5b84707b2 in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=1b8f246 ] QPIDJMS-266 Fix race on connection start with inbound messages If a connection is started in which consumer have been created and messages are incoming a call to start can end in a race where on incoming message can jump the line and be delivered ahead of previously queued messages. Stop storing messages in the session stopped messages queue and just pass them along to the consumer, it won't dispatch them until started again. > Race on session start and message dispatch can deliver messages in wrong order > -- > > Key: QPIDJMS-266 > URL: https://issues.apache.org/jira/browse/QPIDJMS-266 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.20.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.21.0 > > > If a connection is started in which consumer have been created and messages > are incoming a call to start can end in a race where on incoming message can > jump the line and be delivered ahead of previously queued messages. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-266) Race on session start and message dispatch can deliver messages in wrong order
Timothy Bish created QPIDJMS-266: Summary: Race on session start and message dispatch can deliver messages in wrong order Key: QPIDJMS-266 URL: https://issues.apache.org/jira/browse/QPIDJMS-266 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Affects Versions: 0.20.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 0.21.0 If a connection is started in which consumer have been created and messages are incoming a call to start can end in a race where on incoming message can jump the line and be delivered ahead of previously queued messages. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton-j issue #4: SSLContext changes
Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton-j/pull/4 Actually, if you could also confirm if its just working for you that would be good too, as I can then look to kick off the release process on 0.18.0 some time, perhaps next week. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1407) pn_collector_next and pn_collector_peek are inconsistent
[ https://issues.apache.org/jira/browse/PROTON-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1407. - Resolution: Fixed > pn_collector_next and pn_collector_peek are inconsistent > > > Key: PROTON-1407 > URL: https://issues.apache.org/jira/browse/PROTON-1407 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.17.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18.0 > > > pn_collector_peek() == NULL is not a reliable test for an empty collector if > you use pn_collector_next(). next() leaves the event on the head of the queue > until the following call to next, which is confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1403) c proactor library
[ https://issues.apache.org/jira/browse/PROTON-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872309#comment-15872309 ] ASF subversion and git services commented on PROTON-1403: - Commit 6a2316a5d0a4e274802de81744ceae534323ba17 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6a2316a ] PROTON-1403: Rename pn_proactor_grab -> pn_proactor_get > c proactor library > -- > > Key: PROTON-1403 > URL: https://issues.apache.org/jira/browse/PROTON-1403 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18.0 > > > Move the libuv proactor example into an installed library. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1407) pn_collector_next and pn_collector_peek are inconsistent
[ https://issues.apache.org/jira/browse/PROTON-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872308#comment-15872308 ] ASF subversion and git services commented on PROTON-1407: - Commit 7368c34c1d141ba7754289161453d598860ea3da in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7368c34 ] PROTON-1407: pn_collector_next and pn_collector_peek are inconsistent Make the behavior consistent as follows: - peek returns the head of the collector - pop() and next() remove the head of the collector, pop() discards it, next() returns it - next() keeps the returned event alive until the following call to next() next() no longer uses the head of the collector to keep returned events alive, the returned event is remembered via a separate pointer. > pn_collector_next and pn_collector_peek are inconsistent > > > Key: PROTON-1407 > URL: https://issues.apache.org/jira/browse/PROTON-1407 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: 0.17.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18.0 > > > pn_collector_peek() == NULL is not a reliable test for an empty collector if > you use pn_collector_next(). next() leaves the event on the head of the queue > until the following call to next, which is confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1405) Capability to use SSLContext provided by the application.
[ https://issues.apache.org/jira/browse/PROTON-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1405: --- Issue Type: New Feature (was: Improvement) > Capability to use SSLContext provided by the application. > - > > Key: PROTON-1405 > URL: https://issues.apache.org/jira/browse/PROTON-1405 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-j >Affects Versions: proton-j-0.18.0 >Reporter: Shibi Sudhakaran >Assignee: Robbie Gemmell > Fix For: 0.18.0 > > > Applications would like to provide SSLContext to proton-j rather than > proton-j creating SSLContext from .pem files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-1405) Capability to use SSLContext provided by the application.
[ https://issues.apache.org/jira/browse/PROTON-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned PROTON-1405: -- Assignee: Robbie Gemmell > Capability to use SSLContext provided by the application. > - > > Key: PROTON-1405 > URL: https://issues.apache.org/jira/browse/PROTON-1405 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.18.0 >Reporter: Shibi Sudhakaran >Assignee: Robbie Gemmell > Fix For: 0.18.0 > > > Applications would like to provide SSLContext to proton-j rather than > proton-j creating SSLContext from .pem files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1405) Capability to use SSLContext provided by the application.
[ https://issues.apache.org/jira/browse/PROTON-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1405. Resolution: Fixed Fix Version/s: 0.18.0 > Capability to use SSLContext provided by the application. > - > > Key: PROTON-1405 > URL: https://issues.apache.org/jira/browse/PROTON-1405 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.18.0 >Reporter: Shibi Sudhakaran >Assignee: Robbie Gemmell > Fix For: 0.18.0 > > > Applications would like to provide SSLContext to proton-j rather than > proton-j creating SSLContext from .pem files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1405) Capability to use SSLContext provided by the application.
[ https://issues.apache.org/jira/browse/PROTON-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872257#comment-15872257 ] ASF GitHub Bot commented on PROTON-1405: Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton-j/pull/4 I've pushed an updated set of changes, to address some of my earlier feedback and some issues with the subsequent commit. Give things a try out on master and comment here or on PROTON-1405 if you have any issues. > Capability to use SSLContext provided by the application. > - > > Key: PROTON-1405 > URL: https://issues.apache.org/jira/browse/PROTON-1405 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.18.0 >Reporter: Shibi Sudhakaran > > Applications would like to provide SSLContext to proton-j rather than > proton-j creating SSLContext from .pem files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton-j issue #4: SSLContext changes
Github user gemmellr commented on the issue: https://github.com/apache/qpid-proton-j/pull/4 I've pushed an updated set of changes, to address some of my earlier feedback and some issues with the subsequent commit. Give things a try out on master and comment here or on PROTON-1405 if you have any issues. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1405) Capability to use SSLContext provided by the application.
[ https://issues.apache.org/jira/browse/PROTON-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872253#comment-15872253 ] ASF GitHub Bot commented on PROTON-1405: Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton-j/pull/4 > Capability to use SSLContext provided by the application. > - > > Key: PROTON-1405 > URL: https://issues.apache.org/jira/browse/PROTON-1405 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.18.0 >Reporter: Shibi Sudhakaran > > Applications would like to provide SSLContext to proton-j rather than > proton-j creating SSLContext from .pem files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton-j pull request #4: SSLContext changes
Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton-j/pull/4 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1405) Capability to use SSLContext provided by the application.
[ https://issues.apache.org/jira/browse/PROTON-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872251#comment-15872251 ] ASF subversion and git services commented on PROTON-1405: - Commit 4d9a89bdc366582032df2e4cc5d37f2cabc02ad3 in qpid-proton-j's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=4d9a89b ] PROTON-1405: add ability to pass in the SSLContext to use, as opposed to the configuration to create one This closes #4 > Capability to use SSLContext provided by the application. > - > > Key: PROTON-1405 > URL: https://issues.apache.org/jira/browse/PROTON-1405 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.18.0 >Reporter: Shibi Sudhakaran > > Applications would like to provide SSLContext to proton-j rather than > proton-j creating SSLContext from .pem files. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-637) system_tests_sasl_plain and system_tests_deprecated fail when cyrus-sasl-plain is not installed
[ https://issues.apache.org/jira/browse/DISPATCH-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-637: -- Assignee: Ganesh Murthy > system_tests_sasl_plain and system_tests_deprecated fail when > cyrus-sasl-plain is not installed > --- > > Key: DISPATCH-637 > URL: https://issues.apache.org/jira/browse/DISPATCH-637 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Eric Sammons >Assignee: Ganesh Murthy > > The current readme for dispatch and qpid-proton do not mention a dependency > on cyrus-sasl-plain; however, with out the cyrus-sasl-plain package the > system_tests_sasl_plain and system_tests_deprecated tests will fail. > README should mention this dependency. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1407) pn_collector_next and pn_collector_peek are inconsistent
Alan Conway created PROTON-1407: --- Summary: pn_collector_next and pn_collector_peek are inconsistent Key: PROTON-1407 URL: https://issues.apache.org/jira/browse/PROTON-1407 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.17.0 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.18.0 pn_collector_peek() == NULL is not a reliable test for an empty collector if you use pn_collector_next(). next() leaves the event on the head of the queue until the following call to next, which is confusing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-637) system_tests_sasl_plain and system_tests_deprecated fail when cyrus-sasl-plain is not installed
Eric Sammons created DISPATCH-637: - Summary: system_tests_sasl_plain and system_tests_deprecated fail when cyrus-sasl-plain is not installed Key: DISPATCH-637 URL: https://issues.apache.org/jira/browse/DISPATCH-637 Project: Qpid Dispatch Issue Type: Bug Reporter: Eric Sammons The current readme for dispatch and qpid-proton do not mention a dependency on cyrus-sasl-plain; however, with out the cyrus-sasl-plain package the system_tests_sasl_plain and system_tests_deprecated tests will fail. README should mention this dependency. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-57) Cmake installer should check for presence of Node.js and Rhea client
[ https://issues.apache.org/jira/browse/QPIDIT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-57. Resolution: Fixed > Cmake installer should check for presence of Node.js and Rhea client > > > Key: QPIDIT-57 > URL: https://issues.apache.org/jira/browse/QPIDIT-57 > Project: Apache QPID IT > Issue Type: Bug > Components: Installation >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Currently the presence of both node.js and Rhea are assumed. The cmake > installer should check for the presence of node.js, and if that is present, > then for Rhea itself. If found, then the Rhea tests should be enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-66) Shims should install into a libexec directory, not into the Python site-packages path
[ https://issues.apache.org/jira/browse/QPIDIT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872049#comment-15872049 ] ASF subversion and git services commented on QPIDIT-66: --- Commit 5b4cc511bc1b16295132edf21446ff03f1a96808 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=5b4cc51 ] QPIDIT-66: Install shims into libexec directory > Shims should install into a libexec directory, not into the Python > site-packages path > - > > Key: QPIDIT-66 > URL: https://issues.apache.org/jira/browse/QPIDIT-66 > Project: Apache QPID IT > Issue Type: Bug > Components: Installation >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Currently, the shims are installed into a shims subdirectory in the Python > install path for qpid_interop_test. This is not a standard install convention > or location and will cause confusion for users. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-66) Shims should install into a libexec directory, not into the Python site-packages path
[ https://issues.apache.org/jira/browse/QPIDIT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-66. Resolution: Fixed > Shims should install into a libexec directory, not into the Python > site-packages path > - > > Key: QPIDIT-66 > URL: https://issues.apache.org/jira/browse/QPIDIT-66 > Project: Apache QPID IT > Issue Type: Bug > Components: Installation >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Currently, the shims are installed into a shims subdirectory in the Python > install path for qpid_interop_test. This is not a standard install convention > or location and will cause confusion for users. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-636) README claims qpid-proton-c-devel >= 0.13 is required; however, cmake complains with 0.14
[
https://issues.apache.org/jira/browse/DISPATCH-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-636:
---
Fix Version/s: 0.8.0
> README claims qpid-proton-c-devel >= 0.13 is required; however, cmake
> complains with 0.14
> -
>
> Key: DISPATCH-636
> URL: https://issues.apache.org/jira/browse/DISPATCH-636
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Eric Sammons
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
>
> Attempting to follow the readme to clone, build, and install dispatch-router
> results in a cmake error.
> {quote}
> $ cat /etc/redhat-release
> CentOS Linux release 7.3.1611 (Core)
> $ cmake ..
> CMake Error at CMakeLists.txt:103 (find_package):
> Could not find a configuration file for package "Proton" that is compatible
> with requested version "0.15".
> The following configuration files were considered but not accepted:
> /usr/lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> /lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> -- Configuring incomplete, errors occurred!
> See also "/home/dispatch/qpid-dispatch/my_build/CMakeFiles/CMakeOutput.log".
> $ rpm -q qpid-proton-c-devel
> qpid-proton-c-devel-0.14.0-2.el7.x86_64
> {quote}
> This seems to conflict with the documented README and will pose problems on
> platforms where qpid-proton-c-devel >= 0.15 is not yet available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-636) README claims qpid-proton-c-devel >= 0.13 is required; however, cmake complains with 0.14
[
https://issues.apache.org/jira/browse/DISPATCH-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Sammons resolved DISPATCH-636.
---
Resolution: Fixed
Verified that the README has been updated. -Thanks!
> README claims qpid-proton-c-devel >= 0.13 is required; however, cmake
> complains with 0.14
> -
>
> Key: DISPATCH-636
> URL: https://issues.apache.org/jira/browse/DISPATCH-636
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Eric Sammons
>Assignee: Ganesh Murthy
>
> Attempting to follow the readme to clone, build, and install dispatch-router
> results in a cmake error.
> {quote}
> $ cat /etc/redhat-release
> CentOS Linux release 7.3.1611 (Core)
> $ cmake ..
> CMake Error at CMakeLists.txt:103 (find_package):
> Could not find a configuration file for package "Proton" that is compatible
> with requested version "0.15".
> The following configuration files were considered but not accepted:
> /usr/lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> /lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> -- Configuring incomplete, errors occurred!
> See also "/home/dispatch/qpid-dispatch/my_build/CMakeFiles/CMakeOutput.log".
> $ rpm -q qpid-proton-c-devel
> qpid-proton-c-devel-0.14.0-2.el7.x86_64
> {quote}
> This seems to conflict with the documented README and will pose problems on
> platforms where qpid-proton-c-devel >= 0.15 is not yet available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-636) README claims qpid-proton-c-devel >= 0.13 is required; however, cmake complains with 0.14
[
https://issues.apache.org/jira/browse/DISPATCH-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872017#comment-15872017
]
ASF subversion and git services commented on DISPATCH-636:
--
Commit 43846b47845df1dd2d7dd682c4d6abec357fd50b in qpid-dispatch's branch
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=43846b4 ]
DISPATCH-636 - Updated version of Proton that is required to build from 0.13 to
0.15
> README claims qpid-proton-c-devel >= 0.13 is required; however, cmake
> complains with 0.14
> -
>
> Key: DISPATCH-636
> URL: https://issues.apache.org/jira/browse/DISPATCH-636
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Eric Sammons
>
> Attempting to follow the readme to clone, build, and install dispatch-router
> results in a cmake error.
> {quote}
> $ cat /etc/redhat-release
> CentOS Linux release 7.3.1611 (Core)
> $ cmake ..
> CMake Error at CMakeLists.txt:103 (find_package):
> Could not find a configuration file for package "Proton" that is compatible
> with requested version "0.15".
> The following configuration files were considered but not accepted:
> /usr/lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> /lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> -- Configuring incomplete, errors occurred!
> See also "/home/dispatch/qpid-dispatch/my_build/CMakeFiles/CMakeOutput.log".
> $ rpm -q qpid-proton-c-devel
> qpid-proton-c-devel-0.14.0-2.el7.x86_64
> {quote}
> This seems to conflict with the documented README and will pose problems on
> platforms where qpid-proton-c-devel >= 0.15 is not yet available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-636) README claims qpid-proton-c-devel >= 0.13 is required; however, cmake complains with 0.14
[
https://issues.apache.org/jira/browse/DISPATCH-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872018#comment-15872018
]
Ganesh Murthy commented on DISPATCH-636:
The CMakeLists.txt states that to build dispatch, Proton 0.15 is required as
seen below -
{noformat}
find_package(Proton 0.15 REQUIRED)
{noformat}
I fixed the README file to reflect the above -
{noformat}
- qpid-proton-c-devel (0.15 or later)
- python-qpid-proton (0.15 or later)
{noformat}
> README claims qpid-proton-c-devel >= 0.13 is required; however, cmake
> complains with 0.14
> -
>
> Key: DISPATCH-636
> URL: https://issues.apache.org/jira/browse/DISPATCH-636
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Eric Sammons
>
> Attempting to follow the readme to clone, build, and install dispatch-router
> results in a cmake error.
> {quote}
> $ cat /etc/redhat-release
> CentOS Linux release 7.3.1611 (Core)
> $ cmake ..
> CMake Error at CMakeLists.txt:103 (find_package):
> Could not find a configuration file for package "Proton" that is compatible
> with requested version "0.15".
> The following configuration files were considered but not accepted:
> /usr/lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> /lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> -- Configuring incomplete, errors occurred!
> See also "/home/dispatch/qpid-dispatch/my_build/CMakeFiles/CMakeOutput.log".
> $ rpm -q qpid-proton-c-devel
> qpid-proton-c-devel-0.14.0-2.el7.x86_64
> {quote}
> This seems to conflict with the documented README and will pose problems on
> platforms where qpid-proton-c-devel >= 0.15 is not yet available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-636) README claims qpid-proton-c-devel >= 0.13 is required; however, cmake complains with 0.14
[
https://issues.apache.org/jira/browse/DISPATCH-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-636:
--
Assignee: Ganesh Murthy
> README claims qpid-proton-c-devel >= 0.13 is required; however, cmake
> complains with 0.14
> -
>
> Key: DISPATCH-636
> URL: https://issues.apache.org/jira/browse/DISPATCH-636
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Eric Sammons
>Assignee: Ganesh Murthy
>
> Attempting to follow the readme to clone, build, and install dispatch-router
> results in a cmake error.
> {quote}
> $ cat /etc/redhat-release
> CentOS Linux release 7.3.1611 (Core)
> $ cmake ..
> CMake Error at CMakeLists.txt:103 (find_package):
> Could not find a configuration file for package "Proton" that is compatible
> with requested version "0.15".
> The following configuration files were considered but not accepted:
> /usr/lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> /lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
> -- Configuring incomplete, errors occurred!
> See also "/home/dispatch/qpid-dispatch/my_build/CMakeFiles/CMakeOutput.log".
> $ rpm -q qpid-proton-c-devel
> qpid-proton-c-devel-0.14.0-2.el7.x86_64
> {quote}
> This seems to conflict with the documented README and will pose problems on
> platforms where qpid-proton-c-devel >= 0.15 is not yet available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-636) README claims qpid-proton-c-devel >= 0.13 is required; however, cmake complains with 0.14
Eric Sammons created DISPATCH-636:
-
Summary: README claims qpid-proton-c-devel >= 0.13 is required;
however, cmake complains with 0.14
Key: DISPATCH-636
URL: https://issues.apache.org/jira/browse/DISPATCH-636
Project: Qpid Dispatch
Issue Type: Bug
Reporter: Eric Sammons
Attempting to follow the readme to clone, build, and install dispatch-router
results in a cmake error.
{quote}
$ cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
$ cmake ..
CMake Error at CMakeLists.txt:103 (find_package):
Could not find a configuration file for package "Proton" that is compatible
with requested version "0.15".
The following configuration files were considered but not accepted:
/usr/lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
/lib64/cmake/Proton/ProtonConfig.cmake, version: 0.14.0
-- Configuring incomplete, errors occurred!
See also "/home/dispatch/qpid-dispatch/my_build/CMakeFiles/CMakeOutput.log".
$ rpm -q qpid-proton-c-devel
qpid-proton-c-devel-0.14.0-2.el7.x86_64
{quote}
This seems to conflict with the documented README and will pose problems on
platforms where qpid-proton-c-devel >= 0.15 is not yet available.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7656) [Java Broker] Clarify concerns of Link and LinkEndpoint in AMQP 1.0 plugin
[ https://issues.apache.org/jira/browse/QPID-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7656. -- Resolution: Fixed > [Java Broker] Clarify concerns of Link and LinkEndpoint in AMQP 1.0 plugin > -- > > Key: QPID-7656 > URL: https://issues.apache.org/jira/browse/QPID-7656 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack > Fix For: qpid-java-7.0 > > > Currently, in the AMQP 1.0 layer there are classes of closely related > concepts with unclear responsibilities. More specifically, there is a > Link_1_0 class (and subclasses) and a LinkEndpoint class (again with > subclasses). The responsibilities of the classes should be clarified and the > code refactored to reflect this. > See the current (v3) [design of the > LinkRegistry|https://cwiki.apache.org/confluence/display/qpid/Link+Registry+Design] > for proposed responsibilities and APIs. > Essentially, this means moving most of the current implementation of Link > into the LinkEndpoint. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7664) Support defaultOutcome handling
[
https://issues.apache.org/jira/browse/QPID-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7664:
-
Fix Version/s: (was: Future)
qpid-java-7.0
> Support defaultOutcome handling
> ---
>
> Key: QPID-7664
> URL: https://issues.apache.org/jira/browse/QPID-7664
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-7.0
>
>
> The Java Broker currently does not respect the source's {{defaultOutcome}},
> despite concurring with the peer's choice.
> http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#type-source
> It currently arbitrarily decides to use a Modified{deliveryFailed=true} in
> some cases rather than respecting the default. Code is
> ({{org.apache.qpid.server.protocol.v1_0.ConsumerTarget_1_0.DispositionAction}}).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-529) Address annotation for Multi-Tenancy
[
https://issues.apache.org/jira/browse/DISPATCH-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-529.
---
Resolution: Fixed
> Address annotation for Multi-Tenancy
>
>
> Key: DISPATCH-529
> URL: https://issues.apache.org/jira/browse/DISPATCH-529
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Router Node
>Reporter: Ted Ross
>Assignee: Ted Ross
> Fix For: 0.8.0
>
>
> This feature provides an option on connection listeners to annotate addresses
> such that they are partitioned and isolated into vhost-specific spaces.
> The address annotation shall consist of the virtual host (Open.hostname from
> the connecting container).
> Example configuration:
> {noformat}
> listener {
> host: ::
> port: 1
> multiTenant: yes
> ...
> }
> {noformat}
> With this configuration, clients that connect via port 1 will be subject
> to partitioning. If a client connects via "myapp.com", and subscribes a
> receiver for source address "orders", the internal address (for routing and
> storage on a broker queue) shall be "myapp.com/orders".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7673) [Java Broker, AMQP 1.0] Fix asynchronous close of AMQP 1.0 sessions when closeSessionAsync is invoked multiple times
[ https://issues.apache.org/jira/browse/QPID-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7673: - Fix Version/s: (was: qpid-java-7.0) Future > [Java Broker, AMQP 1.0] Fix asynchronous close of AMQP 1.0 sessions when > closeSessionAsync is invoked multiple times > > > Key: QPID-7673 > URL: https://issues.apache.org/jira/browse/QPID-7673 > Project: Qpid > Issue Type: Improvement >Affects Versions: qpid-java-6.1.1, qpid-java-7.0 >Reporter: Alex Rudyy > Fix For: Future > > > When method closeSessionAsync is invoked multiple times (for example from > TransactionTimeoutTicker#tick) that might result in multiple End frames being > sent for the same session. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7672) [Java Broker] Ensure that existing ticker implementations handle multiple invocations of tick method for the same event
[ https://issues.apache.org/jira/browse/QPID-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7672: - Fix Version/s: (was: qpid-java-7.0) Future > [Java Broker] Ensure that existing ticker implementations handle multiple > invocations of tick method for the same event > --- > > Key: QPID-7672 > URL: https://issues.apache.org/jira/browse/QPID-7672 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.0.6, qpid-java-6.1.1 >Reporter: Alex Rudyy > Fix For: Future > > > The changes implemented as part QPID-7670 allow multiple invocations of tick > method after expiration of tick interval. The existing ticker implementations > need to be verified and changed if necessary to handle correctly multiple > invocations for the same event. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7675) [Java Broker] Runtime exception can be thrown by REST API on failure to create BDB HA Virtual Host Node
[
https://issues.apache.org/jira/browse/QPID-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7675:
-
Fix Version/s: qpid-java-6.0.7
> [Java Broker] Runtime exception can be thrown by REST API on failure to
> create BDB HA Virtual Host Node
> ---
>
> Key: QPID-7675
> URL: https://issues.apache.org/jira/browse/QPID-7675
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1,
> qpid-java-6.0.6, qpid-java-6.1.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-7.0, qpid-java-6.1.2, qpid-java-6.0.7
>
>
> RuntimeException is thrown on creation of BDB HA Virtual Host using REST API
> when validation of existing node in group fails. The stack trace is provided
> below:
> {noformat}
> java.lang.RuntimeException: Cannot retrieve state for node 'myNode'
> (localhost:5000) from group 'myGroup'
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.connectToHelperNodeAndCheckPermittedHosts(ReplicatedEnvironmentFacade.java:1858)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.getPermittedNodesFromHelper(BDBHAVirtualHostNodeImpl.java:564)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.validateOnCreate(BDBHAVirtualHostNodeImpl.java:544)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:847)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:834)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:157)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:145)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:624)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:833)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:76)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:125)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.createVirtualHostNodeAsync(BrokerImpl.java:601)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.addChildAsync(BrokerImpl.java:655)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2066)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2061)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_92]
> at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_92]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper
[jira] [Updated] (QPID-7675) [Java Broker] Runtime exception can be thrown by REST API on failure to create BDB HA Virtual Host Node
[
https://issues.apache.org/jira/browse/QPID-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7675:
-
Description:
RuntimeException is occasionally thrown on creation of BDB HA Virtual Host
using REST API when validation of existing node in group fails. The stack trace
is provided below:
{noformat}
java.lang.RuntimeException: Cannot retrieve state for node 'myNode'
(localhost:5000) from group 'myGroup'
at
org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.connectToHelperNodeAndCheckPermittedHosts(ReplicatedEnvironmentFacade.java:1858)
~[qpid-bdbstore-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.getPermittedNodesFromHelper(BDBHAVirtualHostNodeImpl.java:564)
~[qpid-bdbstore-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.validateOnCreate(BDBHAVirtualHostNodeImpl.java:544)
~[qpid-bdbstore-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:847)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:834)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:157)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:145)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:624)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:833)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:76)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:125)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.BrokerImpl.createVirtualHostNodeAsync(BrokerImpl.java:601)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.BrokerImpl.addChildAsync(BrokerImpl.java:655)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2066)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2061)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at java.security.AccessController.doPrivileged(Native Method)
~[na:1.8.0_92]
at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_92]
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:305)
~[qpid-broker-core-6.1.1.jar:6.1.1]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
~[na:1.8.0_92]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
~[na:1.8.0_92]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
~[na:1.8.0_92]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_92]
Caused by: com.sleepycat.je.rep.utilint.BinaryProtocol$ProtocolException:
Expected message type: class
com.sleepycat.je.rep.impl.BinaryNodeStateProtocol$BinaryNodeStateResponse but
found: class com.sleepycat.je.rep.utilint.BinaryProtocol$ProtocolError
at
com.sleepycat.je.rep.utilint.BinaryProtocol.read(BinaryProtocol.java:516)
~[je-5.0.104.jar:5.0.104]
at
[jira] [Updated] (QPID-7675) [Java Broker] Runtime exception can be thrown by REST API on failure to create BDB HA Virtual Host Node
[
https://issues.apache.org/jira/browse/QPID-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7675:
-
Priority: Minor (was: Major)
> [Java Broker] Runtime exception can be thrown by REST API on failure to
> create BDB HA Virtual Host Node
> ---
>
> Key: QPID-7675
> URL: https://issues.apache.org/jira/browse/QPID-7675
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1,
> qpid-java-6.0.6, qpid-java-6.1.1
>Reporter: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-7.0, qpid-java-6.1.2, qpid-java-6.0.7
>
>
> RuntimeException is thrown on creation of BDB HA Virtual Host using REST API
> when validation of existing node in group fails. The stack trace is provided
> below:
> {noformat}
> java.lang.RuntimeException: Cannot retrieve state for node 'myNode'
> (localhost:5000) from group 'myGroup'
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.connectToHelperNodeAndCheckPermittedHosts(ReplicatedEnvironmentFacade.java:1858)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.getPermittedNodesFromHelper(BDBHAVirtualHostNodeImpl.java:564)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.validateOnCreate(BDBHAVirtualHostNodeImpl.java:544)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:847)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:834)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:157)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:145)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:624)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:833)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:76)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:125)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.createVirtualHostNodeAsync(BrokerImpl.java:601)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.addChildAsync(BrokerImpl.java:655)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2066)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2061)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_92]
> at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_92]
> at
> org.apache.qpid.server.configuration.updater.Task
[jira] [Commented] (QPID-7675) [Java Broker] Runtime exception can be thrown by REST API on failure to create BDB HA Virtual Host Node
[
https://issues.apache.org/jira/browse/QPID-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871844#comment-15871844
]
Keith Wall commented on QPID-7675:
--
We said we would additional ensure that underlying message is logged so we are
closer to understanding the root cause of the problem. We probably have
{{org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade#getRemoteNodeState}}
catch JE's ProtocolException and log the unexpectedMessage it contains.
> [Java Broker] Runtime exception can be thrown by REST API on failure to
> create BDB HA Virtual Host Node
> ---
>
> Key: QPID-7675
> URL: https://issues.apache.org/jira/browse/QPID-7675
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1,
> qpid-java-6.0.6, qpid-java-6.1.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-7.0, qpid-java-6.1.2
>
>
> RuntimeException is thrown on creation of BDB HA Virtual Host using REST API
> when validation of existing node in group fails. The stack trace is provided
> below:
> {noformat}
> java.lang.RuntimeException: Cannot retrieve state for node 'myNode'
> (localhost:5000) from group 'myGroup'
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.connectToHelperNodeAndCheckPermittedHosts(ReplicatedEnvironmentFacade.java:1858)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.getPermittedNodesFromHelper(BDBHAVirtualHostNodeImpl.java:564)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.validateOnCreate(BDBHAVirtualHostNodeImpl.java:544)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:847)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:834)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:157)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:145)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:624)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:833)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:76)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:125)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.createVirtualHostNodeAsync(BrokerImpl.java:601)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.addChildAsync(BrokerImpl.java:655)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2066)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2061)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$Callab
[jira] [Updated] (QPID-7675) [Java Broker] Runtime exception can be thrown by REST API on failure to create BDB HA Virtual Host Node
[
https://issues.apache.org/jira/browse/QPID-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7675:
-
Fix Version/s: qpid-java-6.1.2
qpid-java-7.0
> [Java Broker] Runtime exception can be thrown by REST API on failure to
> create BDB HA Virtual Host Node
> ---
>
> Key: QPID-7675
> URL: https://issues.apache.org/jira/browse/QPID-7675
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.32, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2,
> qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1,
> qpid-java-6.0.6, qpid-java-6.1.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-7.0, qpid-java-6.1.2
>
>
> RuntimeException is thrown on creation of BDB HA Virtual Host using REST API
> when validation of existing node in group fails. The stack trace is provided
> below:
> {noformat}
> java.lang.RuntimeException: Cannot retrieve state for node 'myNode'
> (localhost:5000) from group 'myGroup'
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.connectToHelperNodeAndCheckPermittedHosts(ReplicatedEnvironmentFacade.java:1858)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.getPermittedNodesFromHelper(BDBHAVirtualHostNodeImpl.java:564)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.validateOnCreate(BDBHAVirtualHostNodeImpl.java:544)
> ~[qpid-bdbstore-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:847)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$6.execute(AbstractConfiguredObject.java:834)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:157)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:145)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:624)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.createAsync(AbstractConfiguredObject.java:833)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory.createAsync(AbstractConfiguredObjectTypeFactory.java:76)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.ConfiguredObjectFactoryImpl.createAsync(ConfiguredObjectFactoryImpl.java:125)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.createVirtualHostNodeAsync(BrokerImpl.java:601)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.BrokerImpl.addChildAsync(BrokerImpl.java:655)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2066)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$17.execute(AbstractConfiguredObject.java:2061)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:625)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:240)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:312)
> ~[qpid-broker-core-6.1.1.jar:6.1.1]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[na:1.8.0_92]
> at javax.security.auth.Subject.doAs(Subject.java:360) ~[na:1.8.0_92]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl
[jira] [Commented] (QPID-7622) Separate Qpid Broker for Java and 0-x JMS Client in source tree
[
https://issues.apache.org/jira/browse/QPID-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871384#comment-15871384
]
ASF subversion and git services commented on QPID-7622:
---
Commit 1783342 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1783342 ]
QPID-7622: [Java Broker] [0-10] Collasped ServerConnection, SessionSession etc
using inline refactoring
Methods in the base classes that were overridden and invoked using
super.method() are renamed methodSuper()
> Separate Qpid Broker for Java and 0-x JMS Client in source tree
> ---
>
> Key: QPID-7622
> URL: https://issues.apache.org/jira/browse/QPID-7622
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
>Reporter: Keith Wall
> Fix For: qpid-java-7.0
>
>
> As discussed here:
> http://qpid.2158936.n2.nabble.com/DISCUSS-Drop-the-AMQP-0-x-client-from-the-Qpid-for-Java-7-0-release-td7657770.html
> The proposal is to move the code and documentation that comprises the 0-x
> client to its own SVN root:
> https://svn.apache.org/repos/asf/qpid/qpid-jms-0-x
> The Java Broker and integration tests suites will remain at:
> https://svn.apache.org/repos/asf/qpid/qpid-java
> Maven dependencies will be used to pull in the appropriate 0-x client for
> integration testing purposes (as we already do with the Qpid JMS Client).
> The {{qpid-common}} module (and maven release artefact) will be eliminated.
> * Classes that the Broker requires will be moved into the class hierarchy of
> the existing plugin modules {{amqp-0-10-protocol}} and {{amqp-0-8-protocol}}
> e.g. {{org/apache/qpid/server/protocol/vx_y}}.* There is some generic code
> used by many modules such as BindingURL whose copy shall live in broker-core.
> * Code that the 0-x client requires will be copied into the client module.
> The package names will be unchanged.
> This will allow the Broker and 0-x Client to co-exist in the same JVM without
> class loading collision. Class movements will be organised in such a way to
> preserve SVN history.
> The structure of trunk qpid-jms-0-x will look like:
> - qpid-jms-0-x
> + client
>+ example
> + jaa
> + example
> + ra
> + docs
> + jms-client-0-10
> + jms-client-0-8
> There will need to be a new parent POM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
