[jira] [Commented] (PROTON-1718) (Proton-J) Custom Sasl
[
https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314060#comment-16314060
]
Tim Taylor commented on PROTON-1718:
Okay, thanks for looking into it. Keep me posted as this is becoming a blocking
issue for me.
> (Proton-J) Custom Sasl
> --
>
> Key: PROTON-1718
> URL: https://issues.apache.org/jira/browse/PROTON-1718
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Affects Versions: proton-j-0.24.0
>Reporter: Tim Taylor
> Labels: features
>
> I would like to be able to provide a custom SASL implementation for Proton-j
> to use instead of being forced to use the default SaslImpl.java
> implementation.
> Ideally, code like below would be possible
> private class CustomSasl implements org.apache.qpid.proton.engine.Sasl
> {
> ...
> }
> ...
> ...
> //transport.sasl(...) saves the provided sasl implementation and uses it
> internally
> Sasl sasl = transport.sasl(new CustomSasl());
> Do you currently have a workaround that would allow me to use Proton-J this
> way?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1654) Windows build does not compile the examples that require C++11
[ https://issues.apache.org/jira/browse/PROTON-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313822#comment-16313822 ] ASF subversion and git services commented on PROTON-1654: - Commit 9cfe6c1db97633ad4704d4f828fa86c1fc1a1119 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9cfe6c1 ] PROTON-1654: [C++ binding] Fix C++03 library builds > Windows build does not compile the examples that require C++11 > -- > > Key: PROTON-1654 > URL: https://issues.apache.org/jira/browse/PROTON-1654 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.19.0 > > > * scheduled_send > * multithreaded_client > * multithreaded_client_flow_control > Do not get built on Windows because C++11 examples are explicitly excluded > there. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #135: PROTON-1732: [OSX] Enable swig for the Travis...
Github user astitcher commented on a diff in the pull request: https://github.com/apache/qpid-proton/pull/135#discussion_r159936304 --- Diff: .travis.yml --- @@ -23,29 +23,37 @@ compiler: - gcc - clang +env: +- PIP='pip' + matrix: include: - os: linux env: - QPID_PROTON_CMAKE_ARGS='-DCMAKE_BUILD_TYPE=Coverage' +- PIP='pip' --- End diff -- You don't need this as it is the same as the default above. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1718) (Proton-J) Custom Sasl
[
https://issues.apache.org/jira/browse/PROTON-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313451#comment-16313451
]
Robbie Gemmell commented on PROTON-1718:
A key reason I said the bit you quoted was your mention of multiple threads, so
if setting that aside then I'd mostly set it aside too. Thats not the only time
the reactor does IO, it chooses when to do IO work based on some mechanisms,
which I don't fully understand myself since I didn't write it and don't use it
in other components, but in this case it seems like it probably isn't necessary
as the nature of the SASL process will essentially mean thats what happens.
The SASL API caters to the original intended usage of proton as an engine, and
the reactors model hiding it in the way it does prevents you from using it as
intended. Rather than requiring a new SASL impl be provided, with associated
leakage of implementation classes through interfaces and/or making
implementation detail public for unsupported extension, looking into it I think
I see a nice alternative approach where a small addition could allow using the
existing SASL APIs essentially as intended even within the reactor (and perhaps
even making it easier to use outwith the reactor too). I'll put something up
around this on Monday for discussion.
> (Proton-J) Custom Sasl
> --
>
> Key: PROTON-1718
> URL: https://issues.apache.org/jira/browse/PROTON-1718
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Affects Versions: proton-j-0.24.0
>Reporter: Tim Taylor
> Labels: features
>
> I would like to be able to provide a custom SASL implementation for Proton-j
> to use instead of being forced to use the default SaslImpl.java
> implementation.
> Ideally, code like below would be possible
> private class CustomSasl implements org.apache.qpid.proton.engine.Sasl
> {
> ...
> }
> ...
> ...
> //transport.sasl(...) saves the provided sasl implementation and uses it
> internally
> Sasl sasl = transport.sasl(new CustomSasl());
> Do you currently have a workaround that would allow me to use Proton-J this
> way?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart
Rabih Mourad created QPID-8070: -- Summary: Qpid java broker is unable to reconnect to database after kill -9 then restart Key: QPID-8070 URL: https://issues.apache.org/jira/browse/QPID-8070 Project: Qpid Issue Type: Bug Components: Broker-J Affects Versions: qpid-java-6.1.4 Reporter: Rabih Mourad Hello, We are using Qpid java broker version 6.1.4. Our test case: We have a JMS client sending messages continuously in autoAck mode to a messaging cluster. The cluster is composed of 1 dispatch router and 2 java brokers which are connected to an Oracle Db. At some point, the test kills a broker using kill -9 and then attempts to restart it. Randomly, we have a NullPointerException while the broker is restarting and connecting to the virtual host node (the full error stack is at the end of the email). Do you have any idea why this is happening? is there a chance that a kill -9 on a broker leaves the Db in an unstable state? Best regards, Rabih 2018-01-03 17:16:45,930 INFO [VirtualHostNode-default-Config] (q.m.t.recovery_start) - [Broker] [vh(/default)/ms(GenericJDBCMessageStore)] TXN-1004 : Recovery Start 2018-01-03 17:16:45,938 WARN [VirtualHostNode-default-Config] (o.a.q.s.v.SynchronousMessageStoreRecoverer) - Message id 1 in log references queue with id 0b2a06aa-6d46-49aa-885f-63f3cd73108d which is not in the configuration, entry will be discarded 2018-01-03 17:16:45,946 ERROR [VirtualHostNode-default-Config] (o.a.q.s.m.AbstractConfiguredObject) - Failed to open object with name 'default'. Object will be put into ERROR state. java.lang.NullPointerException: null at org.apache.qpid.server.store.AbstractJDBCMessageStore.commitTranAsync(AbstractJDBCMessageStore.java:826) at org.apache.qpid.server.store.AbstractJDBCMessageStore.access$600(AbstractJDBCMessageStore.java:59) at org.apache.qpid.server.store.AbstractJDBCMessageStore$JDBCTransaction.commitTranAsync(AbstractJDBCMessageStore.java:1205) at org.apache.qpid.server.store.jdbc.GenericAbstractJDBCMessageStore$RecordedJDBCTransaction.commitTranAsync(GenericAbstractJDBCMessageStore.java:142) at org.apache.qpid.server.virtualhost.SynchronousMessageStoreRecoverer$MessageInstanceVisitor.handle(SynchronousMessageStoreRecoverer.java:219) at org.apache.qpid.server.store.AbstractJDBCMessageStore$JDBCMessageStoreReader.visitMessageInstances(AbstractJDBCMessageStore.java:1911) at org.apache.qpid.server.virtualhost.SynchronousMessageStoreRecoverer.recover(SynchronousMessageStoreRecoverer.java:82) at org.apache.qpid.server.virtualhost.AbstractVirtualHost.postCreateDefaultExchangeTasks(AbstractVirtualHost.java:2581) at org.apache.qpid.server.virtualhost.AbstractVirtualHost.onActivate(AbstractVirtualHost.java:2563) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1482) at org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1461) at org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:1035) at org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:1029) at org.apache.qpid.server.model.AbstractConfiguredObject$22$1.run(AbstractConfiguredObject.java:2609) at org.apache.qpid.server.model.AbstractConfiguredObject$22$1.run(AbstractConfiguredObject.java:2605) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:360) at org.apache.qpid.server.model.AbstractConfiguredObject$22.onSuccess(AbstractConfiguredObject.java:2604) at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319) at org.apache.qpid.server.configuration.updater.TaskExecutorImpl$ImmediateIfSameThreadExecutor.execute(TaskExecutorImpl.java:404) at org.apache.qpid.server.configuration.updater.TaskExecutorImpl.execute(TaskExecutorImpl.java:187) at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156) at com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101) at com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170) at com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322) at org.apache.qpid.server.model.AbstractConfiguredObject.addFutureCallback(AbstractConfiguredObject.java:2599) at
[jira] [Commented] (PROTON-1722) 0.20.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313405#comment-16313405 ] ASF subversion and git services commented on PROTON-1722: - Commit fe3c38ccf1cfb27a23793f414755befa146e7c01 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=fe3c38c ] PROTON-1722, PROTON-1669: restore versions for 0.19.0-rc2 > 0.20.0 release tasks > > > Key: PROTON-1722 > URL: https://issues.apache.org/jira/browse/PROTON-1722 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: proton-c-0.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1722) 0.20.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313400#comment-16313400 ] ASF subversion and git services commented on PROTON-1722: - Commit f3054e391218a20c88ecd803f39e325388f45d82 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f3054e3 ] PROTON-1722, PROTON-1669: update versions for 0.20.0-SNAPSHOT > 0.20.0 release tasks > > > Key: PROTON-1722 > URL: https://issues.apache.org/jira/browse/PROTON-1722 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: proton-c-0.20.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1669) 0.19.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313398#comment-16313398 ] ASF subversion and git services commented on PROTON-1669: - Commit 01917c713a00dc50c148fb726229e9aa444bbf0c in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=01917c7 ] PROTON-1669: update versions for 0.19.0-rc1 > 0.19.0 release tasks > > > Key: PROTON-1669 > URL: https://issues.apache.org/jira/browse/PROTON-1669 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: proton-c-0.19.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1669) 0.19.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313406#comment-16313406 ] ASF subversion and git services commented on PROTON-1669: - Commit fe3c38ccf1cfb27a23793f414755befa146e7c01 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=fe3c38c ] PROTON-1722, PROTON-1669: restore versions for 0.19.0-rc2 > 0.19.0 release tasks > > > Key: PROTON-1669 > URL: https://issues.apache.org/jira/browse/PROTON-1669 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: proton-c-0.19.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1721) [ruby] resovler errors are not handled correctly
[ https://issues.apache.org/jira/browse/PROTON-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313403#comment-16313403 ] ASF subversion and git services commented on PROTON-1721: - Commit cd06716a08c936f5e7db053355a033b4af45529f in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=cd06716 ] PROTON-1724: Revert "PROTON-1721 [ruby] resovler errors are not handled correctly" This reverts commit c4d5fde71d925f3f44b0e29d672de7b039ee709f. In the context of Ruby it is better to raise these exceptions immediately than to bury them as events. > [ruby] resovler errors are not handled correctly > > > Key: PROTON-1721 > URL: https://issues.apache.org/jira/browse/PROTON-1721 > Project: Qpid Proton > Issue Type: Bug >Reporter: Alan Conway >Assignee: Alan Conway > > Exceptions raised by TCPSocket.new/TCPServer.new are raised out of > Container#connnect/listen instead of being turned into error events. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1703) [cpp] Remove auto_settle from receiver options
[ https://issues.apache.org/jira/browse/PROTON-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313394#comment-16313394 ] ASF subversion and git services commented on PROTON-1703: - Commit b9f9402598171602ed7d3c6f7dd410906d1d0684 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b9f9402 ] Revert PROTON-1703: [cpp] Remove auto_settle from receiver_options Reverted the change for binary compatibility but deprecated auto_settle since it is a no-op on receiver. To remove at next major revision. > [cpp] Remove auto_settle from receiver options > -- > > Key: PROTON-1703 > URL: https://issues.apache.org/jira/browse/PROTON-1703 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.19.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > > auto_settle is a sender-only option, the receiver equivalent is auto_accept. > auto_settle is only used at messaging_adapter.cpp#L172, which applies only to > senders, it was included in the option list by mistake. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1725) [ruby] broker example does not work if run outside home directory
[ https://issues.apache.org/jira/browse/PROTON-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313404#comment-16313404 ] ASF subversion and git services commented on PROTON-1725: - Commit 45bd5733ec4c682f81b2a3efb4dbf43d10b1fae9 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=45bd573 ] PROTON-1725: [ruby] broker example should work if SSL certs not found > [ruby] broker example does not work if run outside home directory > - > > Key: PROTON-1725 > URL: https://issues.apache.org/jira/browse/PROTON-1725 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Alan Conway >Assignee: Alan Conway > > The ruby broker example looks for SSL config files in the current directory > and is supposed to proceed without SSL if it doesn't find them. Due to a > typo, it instead creates an invalid SSL context and refuses all comers. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1717) [C proactor] Allow initialization of transport and connection before binding
[ https://issues.apache.org/jira/browse/PROTON-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313397#comment-16313397 ] ASF subversion and git services commented on PROTON-1717: - Commit 4d16e6183d4d0eb39e2a29d2a3a289fef2327201 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4d16e61 ] PROTON-1717 [C proactor] Fix build error in example Fix build error on older compilers in ssl-send example. > [C proactor] Allow initialization of transport and connection before binding > > > Key: PROTON-1717 > URL: https://issues.apache.org/jira/browse/PROTON-1717 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.18.1 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > The C proactor allows the user to configure a connection before it is bound > to a transport, but does not allow configuring the transport before binding. > Some security configurations require this. > Modify the proactor API to give access to both the connection and the > transport before the are bound together. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1669) 0.19.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313401#comment-16313401 ] ASF subversion and git services commented on PROTON-1669: - Commit f3054e391218a20c88ecd803f39e325388f45d82 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f3054e3 ] PROTON-1722, PROTON-1669: update versions for 0.20.0-SNAPSHOT > 0.19.0 release tasks > > > Key: PROTON-1669 > URL: https://issues.apache.org/jira/browse/PROTON-1669 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: proton-c-0.19.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1724) [ruby] early error in Container#listen is not handled correctly
[ https://issues.apache.org/jira/browse/PROTON-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313402#comment-16313402 ] ASF subversion and git services commented on PROTON-1724: - Commit cd06716a08c936f5e7db053355a033b4af45529f in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=cd06716 ] PROTON-1724: Revert "PROTON-1721 [ruby] resovler errors are not handled correctly" This reverts commit c4d5fde71d925f3f44b0e29d672de7b039ee709f. In the context of Ruby it is better to raise these exceptions immediately than to bury them as events. > [ruby] early error in Container#listen is not handled correctly > --- > > Key: PROTON-1724 > URL: https://issues.apache.org/jira/browse/PROTON-1724 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: proton-c-0.18.1 >Reporter: Alan Conway >Assignee: Alan Conway > > Errors on listener are not handled correctly: > on_open is called when it should not be - on an error only on_error should be > called. > errors before creation of the socket (e.g. DNS lookup error) are not reported. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1717) [C proactor] Allow initialization of transport and connection before binding
[ https://issues.apache.org/jira/browse/PROTON-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313395#comment-16313395 ] ASF subversion and git services commented on PROTON-1717: - Commit 3311dd602d228e960019a54128e1e6674247778f in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3311dd6 ] PROTON-1717 [C proactor] Make changes backward compatible. Restore and deprecate original signatures for pn_proactor_connect and pn_listener_accept. Introduce pn_proactor_connect2 and pn_listener_accept2 taking a transport parameter. Update all examples & tests to use the un-deprecated functions. > [C proactor] Allow initialization of transport and connection before binding > > > Key: PROTON-1717 > URL: https://issues.apache.org/jira/browse/PROTON-1717 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.18.1 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > The C proactor allows the user to configure a connection before it is bound > to a transport, but does not allow configuring the transport before binding. > Some security configurations require this. > Modify the proactor API to give access to both the connection and the > transport before the are bound together. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1669) 0.19.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313396#comment-16313396 ] ASF subversion and git services commented on PROTON-1669: - Commit 5e4242c29663f2398219d1c21d93789ef2870c27 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5e4242c ] PROTON-1669: bump the .so minor versions > 0.19.0 release tasks > > > Key: PROTON-1669 > URL: https://issues.apache.org/jira/browse/PROTON-1669 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: proton-c-0.19.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1735) Clients do not use server's failover-server-list
[
https://issues.apache.org/jira/browse/PROTON-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated PROTON-1735:
Description:
See Advanced Message Queuing Protocol (AMQP)
Connection Failover Properties Version 1.0
https://www.google.com/url?sa=t=j==s=web=5=rja=8=0ahUKEwjPjJaUjMHYAhUONd8KHe4MCo0QFghJMAQ=https%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F60379%2Famqp-failover-v1.0-wd01.pdf=AOvVaw00Kcp8qXMmwP1pC-8QVU36
Some products such as Qpid Dispatch offer the failover-server-list
{noformat}
◊ open [0]
Length: 331
Doff: 2
Type: AMQP (0)
Channel: 0
Performative: open (16)
Arguments
Container-Id: Router.A
Max-Frame-Size: 16384
Channel-Max: 32767
Idle-Timeout: 8000
Offered-Capabilities: ANONYMOUS-RELAY
Properties (map of 3 elements)
product (str8-utf8): qpid-dispatch-router
version (str8-utf8): 1.0.0
failover-server-list (list of 3 elements)
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5700
scheme (str8-utf8): amqp
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5701
scheme (str8-utf8): amqp
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5702
scheme (str8-utf8): amqp
{noformat}
was:
See Advanced Message Queuing Protocol (AMQP)
Connection Failover Properties Version 1.0
https://www.google.com/url?sa=t=j==s=web=5=rja=8=0ahUKEwjPjJaUjMHYAhUONd8KHe4MCo0QFghJMAQ=https%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F60379%2Famqp-failover-v1.0-wd01.pdf=AOvVaw00Kcp8qXMmwP1pC-8QVU36
Some products such as Qpid Dispatch offer the server-failover-list
{noformat}
◊ open [0]
Length: 331
Doff: 2
Type: AMQP (0)
Channel: 0
Performative: open (16)
Arguments
Container-Id: Router.A
Max-Frame-Size: 16384
Channel-Max: 32767
Idle-Timeout: 8000
Offered-Capabilities: ANONYMOUS-RELAY
Properties (map of 3 elements)
product (str8-utf8): qpid-dispatch-router
version (str8-utf8): 1.0.0
failover-server-list (list of 3 elements)
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5700
scheme (str8-utf8): amqp
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5701
scheme (str8-utf8): amqp
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5702
scheme (str8-utf8): amqp
{noformat}
> Clients do not use server's failover-server-list
> -
>
> Key: PROTON-1735
> URL: https://issues.apache.org/jira/browse/PROTON-1735
> Project: Qpid Proton
> Issue Type: Bug
>Affects Versions: proton-c-0.19.0
>Reporter: Chuck Rolke
>
> See Advanced Message Queuing Protocol (AMQP)
> Connection Failover Properties Version 1.0
> https://www.google.com/url?sa=t=j==s=web=5=rja=8=0ahUKEwjPjJaUjMHYAhUONd8KHe4MCo0QFghJMAQ=https%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F60379%2Famqp-failover-v1.0-wd01.pdf=AOvVaw00Kcp8qXMmwP1pC-8QVU36
> Some products such as Qpid Dispatch offer the failover-server-list
> {noformat}
> ◊ open [0]
> Length: 331
> Doff: 2
> Type: AMQP (0)
> Channel: 0
> Performative: open (16)
> Arguments
> Container-Id: Router.A
> Max-Frame-Size: 16384
> Channel-Max: 32767
> Idle-Timeout: 8000
> Offered-Capabilities: ANONYMOUS-RELAY
> Properties (map of 3 elements)
> product (str8-utf8): qpid-dispatch-router
> version (str8-utf8): 1.0.0
> failover-server-list (list of 3 elements)
>list-item (map of 3 elements)
>network-host (str8-utf8): 127.0.0.1
>port (str8-utf8): 5700
>scheme (str8-utf8): amqp
>list-item (map of 3 elements)
>
[jira] [Created] (PROTON-1735) Clients do not use server's failover-server-list
Chuck Rolke created PROTON-1735:
---
Summary: Clients do not use server's failover-server-list
Key: PROTON-1735
URL: https://issues.apache.org/jira/browse/PROTON-1735
Project: Qpid Proton
Issue Type: Bug
Affects Versions: proton-c-0.19.0
Reporter: Chuck Rolke
See Advanced Message Queuing Protocol (AMQP)
Connection Failover Properties Version 1.0
https://www.google.com/url?sa=t=j==s=web=5=rja=8=0ahUKEwjPjJaUjMHYAhUONd8KHe4MCo0QFghJMAQ=https%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F60379%2Famqp-failover-v1.0-wd01.pdf=AOvVaw00Kcp8qXMmwP1pC-8QVU36
Some products such as Qpid Dispatch offer the server-failover-list
{noformat}
◊ open [0]
Length: 331
Doff: 2
Type: AMQP (0)
Channel: 0
Performative: open (16)
Arguments
Container-Id: Router.A
Max-Frame-Size: 16384
Channel-Max: 32767
Idle-Timeout: 8000
Offered-Capabilities: ANONYMOUS-RELAY
Properties (map of 3 elements)
product (str8-utf8): qpid-dispatch-router
version (str8-utf8): 1.0.0
failover-server-list (list of 3 elements)
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5700
scheme (str8-utf8): amqp
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5701
scheme (str8-utf8): amqp
list-item (map of 3 elements)
network-host (str8-utf8): 127.0.0.1
port (str8-utf8): 5702
scheme (str8-utf8): amqp
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312926#comment-16312926 ] ASF subversion and git services commented on QPID-6933: --- Commit b52830d5a6bf387a359a91aa00b360ac9b17aae4 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=b52830d ] QPID-6933: [System Tests] Switch to sync publishing in ConsumerPriorityTest > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8069) [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30 seconds on TLS handshake failure
[
https://issues.apache.org/jira/browse/QPID-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8069:
-
Description:
AMQTimeoutException is reported after waiting for "maximum state wait time",
when TLS hand shake fails.
The stack traces like below are reported
{noformat}
2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnection
Connection(27):amqp://guest:@clientid/?brokerlist='tcp://localhost:46879?trust_store='/tmp/test-profiles/test_resources/ssl/java_client_truststore.jks'_store_password=''='true''
2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnection AMQP version 0-9-1
2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.p.AMQProtocolSession Using
ProtocolVersion for Session:0-91
2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.h.ClientMethodDispatcherImpl New
Method Dispatcher:AMQProtocolSession[null]
2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnection Connecting with
ProtocolHandler Version:0-91
2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnectionDelegate_8_0
Connecting to
broker:tcp://localhost:46879?trust_store='/tmp/test-profiles/test_resources/ssl/java_client_truststore.jks'_store_password=''='true'
2018-01-04 21:59:33,961 DEBUG [main] o.a.q.t.n.i.IoNetworkTransport Socket
options SO_RCVBUF : 65535, SO_SNDBUF : 65535, TCP_NODELAY : true
2018-01-04 21:59:33,961 DEBUG [main] o.a.q.t.n.i.IoNetworkTransport Socket
connection from /127.0.0.1:48680 to localhost/127.0.0.1:46879 established
2018-01-04 21:59:33,961 DEBUG
[IO-pool-Port-testClientCertificateMissingWhilstNeedingTlsPort-5]
o.a.q.s.t.NonBlockingConnection Identified transport encryption as TLS
2018-01-04 21:59:33,962 DEBUG [main] o.a.q.c.s.StateWaiter New StateWaiter
:CONNECTION_NOT_STARTED:[CONNECTION_OPEN, CONNECTION_CLOSED]
2018-01-04 21:59:33,964 DEBUG [IO-/127.0.0.1:48680]
o.a.q.s.t.NonBlockingConnection Read 172 byte(s)
2018-01-04 21:59:33,973 DEBUG [IO-/127.0.0.1:48680]
o.a.q.s.t.NonBlockingConnection Written 1825 bytes
2018-01-04 21:59:33,974 DEBUG [IO-/127.0.0.1:48680]
o.a.q.s.t.NonBlockingConnection Read 0 byte(s)
2018-01-04 21:59:33,982 DEBUG [IO-/127.0.0.1:48680]
o.a.q.s.t.NonBlockingConnection Read 173 byte(s)
2018-01-04 21:59:33,984 DEBUG [IO-/127.0.0.1:48680]
o.a.q.s.t.NonBlockingConnection Exception performing I/O for connection
'/127.0.0.1:48680'
javax.net.ssl.SSLHandshakeException: null cert chain
at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1478)
at
sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:813)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.decryptSSL(QpidByteBufferFactory.java:197)
at
org.apache.qpid.server.bytebuffer.QpidByteBuffer.decryptSSL(QpidByteBuffer.java:68)
at
org.apache.qpid.server.transport.NonBlockingConnectionTLSDelegate.processData(NonBlockingConnectionTLSDelegate.java:125)
at
org.apache.qpid.server.transport.NonBlockingConnection.doRead(NonBlockingConnection.java:496)
at
org.apache.qpid.server.transport.NonBlockingConnection.doWork(NonBlockingConnection.java:270)
at
org.apache.qpid.server.transport.NetworkConnectionScheduler.processConnection(NetworkConnectionScheduler.java:134)
at
org.apache.qpid.server.transport.SelectorThread$ConnectionProcessor.processConnection(SelectorThread.java:580)
at
org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:371)
at
org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
at
org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:538)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: null cert chain
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:304)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:292)
at
sun.security.ssl.ServerHandshaker.clientCertificate(ServerHandshaker.java:1862)
at
sun.security.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:233)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:966)
at
[jira] [Updated] (QPID-8069) [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30 seconds on TLS handshake failure
[
https://issues.apache.org/jira/browse/QPID-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8069:
-
Summary: [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30
seconds on TLS handshake failure (was: [Qpid JMS AMQP 0-x] An establishment of
connection blocks for 30 seconds when TLS handshake failure)
> [Qpid JMS AMQP 0-x] An establishment of connection blocks for 30 seconds on
> TLS handshake failure
> -
>
> Key: QPID-8069
> URL: https://issues.apache.org/jira/browse/QPID-8069
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
>Affects Versions: qpid-java-client-0-x-6.3.0
>Reporter: Alex Rudyy
>
> AMQTimeoutException is reported after waiting for "maximum state wait time",
> when TLS hand shake fails.
> The stack traces like below are reported
> {noformat}
> 2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnection
> Connection(27):amqp://guest:@clientid/?brokerlist='tcp://localhost:46879?trust_store='/tmp/test-profiles/test_resources/ssl/java_client_truststore.jks'_store_password=''='true''
> 2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnection AMQP version 0-9-1
> 2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.p.AMQProtocolSession Using
> ProtocolVersion for Session:0-91
> 2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.h.ClientMethodDispatcherImpl New
> Method Dispatcher:AMQProtocolSession[null]
> 2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnection Connecting with
> ProtocolHandler Version:0-91
> 2018-01-04 21:59:33,960 DEBUG [main] o.a.q.c.AMQConnectionDelegate_8_0
> Connecting to
> broker:tcp://localhost:46879?trust_store='/tmp/test-profiles/test_resources/ssl/java_client_truststore.jks'_store_password=''='true'
> 2018-01-04 21:59:33,961 DEBUG [main] o.a.q.t.n.i.IoNetworkTransport Socket
> options SO_RCVBUF : 65535, SO_SNDBUF : 65535, TCP_NODELAY : true
> 2018-01-04 21:59:33,961 DEBUG [main] o.a.q.t.n.i.IoNetworkTransport Socket
> connection from /127.0.0.1:48680 to localhost/127.0.0.1:46879 established
> 2018-01-04 21:59:33,961 DEBUG
> [IO-pool-Port-testClientCertificateMissingWhilstNeedingTlsPort-5]
> o.a.q.s.t.NonBlockingConnection Identified transport encryption as TLS
> 2018-01-04 21:59:33,962 DEBUG [main] o.a.q.c.s.StateWaiter New StateWaiter
> :CONNECTION_NOT_STARTED:[CONNECTION_OPEN, CONNECTION_CLOSED]
> 2018-01-04 21:59:33,964 DEBUG [IO-/127.0.0.1:48680]
> o.a.q.s.t.NonBlockingConnection Read 172 byte(s)
> 2018-01-04 21:59:33,973 DEBUG [IO-/127.0.0.1:48680]
> o.a.q.s.t.NonBlockingConnection Written 1825 bytes
> 2018-01-04 21:59:33,974 DEBUG [IO-/127.0.0.1:48680]
> o.a.q.s.t.NonBlockingConnection Read 0 byte(s)
> 2018-01-04 21:59:33,982 DEBUG [IO-/127.0.0.1:48680]
> o.a.q.s.t.NonBlockingConnection Read 173 byte(s)
> 2018-01-04 21:59:33,984 DEBUG [IO-/127.0.0.1:48680]
> o.a.q.s.t.NonBlockingConnection Exception performing I/O for connection
> '/127.0.0.1:48680'
> javax.net.ssl.SSLHandshakeException: null cert chain
> at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1478)
> at
> sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
> at
> sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:813)
> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
> at
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.decryptSSL(QpidByteBufferFactory.java:197)
> at
> org.apache.qpid.server.bytebuffer.QpidByteBuffer.decryptSSL(QpidByteBuffer.java:68)
> at
> org.apache.qpid.server.transport.NonBlockingConnectionTLSDelegate.processData(NonBlockingConnectionTLSDelegate.java:125)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doRead(NonBlockingConnection.java:496)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doWork(NonBlockingConnection.java:270)
> at
> org.apache.qpid.server.transport.NetworkConnectionScheduler.processConnection(NetworkConnectionScheduler.java:134)
> at
> org.apache.qpid.server.transport.SelectorThread$ConnectionProcessor.processConnection(SelectorThread.java:580)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:371)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
> at
> org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:538)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
>
