[jira] [Commented] (DISPATCH-390) New pn_proactor-based IO driver
[ https://issues.apache.org/jira/browse/DISPATCH-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856850#comment-15856850 ] ASF subversion and git services commented on DISPATCH-390: -- Commit 9422a77d50d03327f886dc7a9103d34606723096 in qpid-dispatch's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=9422a77 ] DISPATCH-390 Remove dead code - unused qd_link_get/set_conn_context() > New pn_proactor-based IO driver > --- > > Key: DISPATCH-390 > URL: https://issues.apache.org/jira/browse/DISPATCH-390 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Container >Affects Versions: 0.6.0 >Reporter: Alan Conway >Assignee: Alan Conway > > Replace the current proton IO driver with a driver based on the pn_proactor > API. This will allow drop-in replacement of the IO layer for different > platforms. -- 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-1385) make proton-j independently releasable
[ https://issues.apache.org/jira/browse/PROTON-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856760#comment-15856760 ] ASF subversion and git services commented on PROTON-1385: - Commit e0ec0b61d970a95a21ff7ea53bec5ea3e82bbbab in qpid-proton's branch refs/heads/go1 from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e0ec0b6 ] PROTON-1385: remove stale scratch file > make proton-j independently releasable > -- > > Key: PROTON-1385 > URL: https://issues.apache.org/jira/browse/PROTON-1385 > Project: Qpid Proton > Issue Type: Task > Components: build, proton-j, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.17.0, proton-j-0.17.0 > > > As previously discussed on the mailing lists, we are moving proton-j to be an > independently released component. As part of this a new qpid-proton-j > repository was created in December as a copy of the existing proton repo, it > can be found at: > https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git > This JIRA will track the changes made to leave only proton-j in its new repo, > and also remove it from the original qpid-proton repository where proton-c > and its language bindings will remain. -- 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-1396) 0.17.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856766#comment-15856766 ] ASF subversion and git services commented on PROTON-1396: - Commit 4185261b7e43c221a1659d54cf35c871d99cfd9c in qpid-proton's branch refs/heads/go1 from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4185261 ] PROTON-1396: update version to 0.18.0-SNAPSHOT > 0.17.0 release tasks > > > Key: PROTON-1396 > URL: https://issues.apache.org/jira/browse/PROTON-1396 > Project: Qpid Proton > Issue Type: Task > Components: release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.17.0 > > -- 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-1396) 0.17.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856764#comment-15856764 ] ASF subversion and git services commented on PROTON-1396: - Commit 5445b6a255187cf18be6dffb3fa45d659467c502 in qpid-proton's branch refs/heads/go1 from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5445b6a ] PROTON-1396: update versions to 0.17.0 > 0.17.0 release tasks > > > Key: PROTON-1396 > URL: https://issues.apache.org/jira/browse/PROTON-1396 > Project: Qpid Proton > Issue Type: Task > Components: release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.17.0 > > -- 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-1344) Provide C "proactor" API for multi-threaded proton applications
[ https://issues.apache.org/jira/browse/PROTON-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856767#comment-15856767 ] ASF subversion and git services commented on PROTON-1344: - Commit 66d8f0e9c493419f27ff63f47dd7a707efc28e80 in qpid-proton's branch refs/heads/go1 from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=66d8f0e ] PROTON-1344: Added missed PN_LISTENER_ACCEPT event from pn_event_type_name() > Provide C "proactor" API for multi-threaded proton applications > --- > > Key: PROTON-1344 > URL: https://issues.apache.org/jira/browse/PROTON-1344 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > This work will pull together work that has been going on with the > experimental pn_connection_engine_t and work on a new C multi-threaded libuv > C driver. This work has matured to the point of putting together a coherent > and complete pn_proactor API to (eventually) replace the pn_reactor. > The big differences: > - proactive not reactive: e.g. void proactor_connect() does not return a > bound connection, it starts an asynchronous connection process. All results > are reported asynchronously as events, not as synchrouns return values. > - application controls threading: application thread(s) call wait() to block > for events. There are no callbacks to application code from unknown threading > contexts. > - enforces threading model to ensure that events from one connection engine > are only handled in one thread at a time. The application does not need locks > to or tables to manage this. > - provides simple inter-thread singalling - any thread can "wake" a > connection, causing the proactor to return an event in a thread-safe way for > application-triggered work. > The big similarities: > Same proton protocol engine API is unchanged - the pn_connection_engine will > dissappear as a separate entity but it's functions will be folded back into > pn_connection and pn_transport. > Same event model: existing code that processes events is unchanged, instead > of registering `void my_handler(pn_event_t *)` with the reactor, the > application calls my_handler(pn_driver_wait()) in its own threads. There will > be a handful of new proactor-related events. -- 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-1396) 0.17.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856762#comment-15856762 ] ASF subversion and git services commented on PROTON-1396: - Commit 99e516b5c3cc62090f5d69ea4a9af433014541de in qpid-proton's branch refs/heads/go1 from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=99e516b ] PROTON-1396: restore the so version to 10 on master for 0.17.0. Checking (thanks Andrew!) shows no ABI relevant change between 0.16.0 and now. This reverts commit 2389a2179e39fd53912a3e28369b1b409d94c996 for PROTON-1374 > 0.17.0 release tasks > > > Key: PROTON-1396 > URL: https://issues.apache.org/jira/browse/PROTON-1396 > Project: Qpid Proton > Issue Type: Task > Components: release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.17.0 > > -- 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-1395) go: testing with -race fails on some platforms
[ https://issues.apache.org/jira/browse/PROTON-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856761#comment-15856761 ] ASF subversion and git services commented on PROTON-1395: - Commit 6a235006808750454bdeb35a1bd3195a914b5a0d in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6a23500 ] PROTON-1395: go: testing with -race fails on some platforms Remove -race from the default GO_TEST_FLAGS as it causes problems on some platforms. You can enable it in cmake by adding -race to the GO_TEST_FLAGS value (and are encouraged to if your platform supports it) > go: testing with -race fails on some platforms > --- > > Key: PROTON-1395 > URL: https://issues.apache.org/jira/browse/PROTON-1395 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Affects Versions: 0.16.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.17.0 > > > There seems to be a problem with -race in some Go versions on Ubuntu: > https://bugs.launchpad.net/bugs/1487010 > https://bugs.launchpad.net/bugs/1496503 > Lack of -race is also a known limitation of gccgo > This is causing false failures for CI and other testing. -- 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-1392) SWIG doesn't define how to export symbols on Solaris
[ https://issues.apache.org/jira/browse/PROTON-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856759#comment-15856759 ] ASF subversion and git services commented on PROTON-1392: - Commit 2f4ccd56941fe5cd7c30c4696dbc60d2e598b13f in qpid-proton's branch refs/heads/go1 from [~adelbout...@live.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=2f4ccd5 ] PROTON-1392: properly export swig-generated API on SunStudio This closes #94 > SWIG doesn't define how to export symbols on Solaris > > > Key: PROTON-1392 > URL: https://issues.apache.org/jira/browse/PROTON-1392 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.16.0 >Reporter: Adel Boutros >Assignee: Ken Giusti > Fix For: 0.17.0 > > Attachments: > 0001-SWIG-doesn-t-define-how-to-export-symbols-on-Solaris.patch > > > Details are here: > http://qpid.2158936.n2.nabble.com/Proton-0-16-0-Compiling-Proton-Python-bindings-on-Solaris-is-failing-in-the-python-tests-tp7657976.html -- 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-1374) 0.16.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856763#comment-15856763 ] ASF subversion and git services commented on PROTON-1374: - Commit 99e516b5c3cc62090f5d69ea4a9af433014541de in qpid-proton's branch refs/heads/go1 from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=99e516b ] PROTON-1396: restore the so version to 10 on master for 0.17.0. Checking (thanks Andrew!) shows no ABI relevant change between 0.16.0 and now. This reverts commit 2389a2179e39fd53912a3e28369b1b409d94c996 for PROTON-1374 > 0.16.0 release tasks > > > Key: PROTON-1374 > URL: https://issues.apache.org/jira/browse/PROTON-1374 > Project: Qpid Proton > Issue Type: Task > Components: release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell > Fix For: 0.16.0 > > -- 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-608) Links not cleaned up when a close is sent without being preceeded by a detach and end
[ https://issues.apache.org/jira/browse/DISPATCH-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856705#comment-15856705 ] ASF GitHub Bot commented on DISPATCH-608: - Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/137 > Links not cleaned up when a close is sent without being preceeded by a detach > and end > - > > Key: DISPATCH-608 > URL: https://issues.apache.org/jira/browse/DISPATCH-608 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > There are memory leaks of qd_dispatch_t objects when close is sent without > being proceeded by a detach and end frames -- 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-608) Links not cleaned up when a close is sent without being preceeded by a detach and end
[ https://issues.apache.org/jira/browse/DISPATCH-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-608. Resolution: Fixed > Links not cleaned up when a close is sent without being preceeded by a detach > and end > - > > Key: DISPATCH-608 > URL: https://issues.apache.org/jira/browse/DISPATCH-608 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > There are memory leaks of qd_dispatch_t objects when close is sent without > being proceeded by a detach and end frames -- 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-dispatch pull request #137: DISPATCH-608 - Added calls to close links w...
Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/137 --- 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] (DISPATCH-608) Links not cleaned up when a close is sent without being preceeded by a detach and end
[ https://issues.apache.org/jira/browse/DISPATCH-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856701#comment-15856701 ] ASF subversion and git services commented on DISPATCH-608: -- Commit 4cb6e737a8df4d94079fbf94bb4385897c567168 in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=4cb6e73 ] DISPATCH-608 - Added calls to close links when a close frame is sent without being proceeded by a detach and end frames (cherry picked from commit 04cbf2878ec0a37405b96a30b840e30f723c39d3) > Links not cleaned up when a close is sent without being preceeded by a detach > and end > - > > Key: DISPATCH-608 > URL: https://issues.apache.org/jira/browse/DISPATCH-608 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > > There are memory leaks of qd_dispatch_t objects when close is sent without > being proceeded by a detach and end frames -- 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] (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=15856657#comment-15856657
]
ASF subversion and git services commented on QPID-7622:
---
Commit 1782067 from [~k-wall] in branch 'x/trunk'
[ https://svn.apache.org/r1782067 ]
QPID-7622: Correct test dependency in JCA module
> 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
[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=15856641#comment-15856641
]
ASF subversion and git services commented on QPID-7622:
---
Commit 1782062 from [~k-wall] in branch 'x/trunk'
[ https://svn.apache.org/r1782062 ]
QPID-7622: Move client version from 7.0.0-SNAPSHOT to 6.3.0-SNAPSHOT
> 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
[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=15856597#comment-15856597
]
ASF subversion and git services commented on QPID-7622:
---
Commit 1782057 from [~k-wall] in branch 'x/trunk'
[ https://svn.apache.org/r1782057 ]
QPID-7622: Correct maven parentage of the example module, fix generation of
docbook
> 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
[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=15856587#comment-15856587
]
ASF subversion and git services commented on QPID-7622:
---
Commit 1782055 from [~k-wall] in branch 'x/trunk'
[ https://svn.apache.org/r1782055 ]
QPID-7622: Correct maven parentage of the JCA modules
> 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
[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=15856551#comment-15856551
]
ASF subversion and git services commented on QPID-7622:
---
Commit 1782053 from [~k-wall] in branch 'x/trunk'
[ https://svn.apache.org/r1782053 ]
QPID-7622: Forgot the new client parent POM
> 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
[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=15856510#comment-15856510
]
ASF subversion and git services commented on QPID-7622:
---
Commit 1782048 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1782048 ]
QPID-7622: [Java Broker/0-x JMS Client] Separate Broker / Client; eliminate
common
For this initial commit:
* new root for 0-x client established qpid-jms-amqp-0-x with new parent POM
* client, jca and docs svn moved to qpid-jms-amqp-0-x
* common code svn copied to qpid-jms-amqp-0-x (package unchanged)
* common coded svn moved to broker-core (package refactored to o.a.q.server.*)
* POMs manually fixed up
* No elimination of client-only code from broker yet , or vice versa
> 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
[jira] [Updated] (PROTON-1393) Memory leak with delayed settlement
[
https://issues.apache.org/jira/browse/PROTON-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Kamke updated PROTON-1393:
---
Affects Version/s: 0.17.0
> Memory leak with delayed settlement
> ---
>
> Key: PROTON-1393
> URL: https://issues.apache.org/jira/browse/PROTON-1393
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
>Affects Versions: 0.16.0, 0.17.0
>Reporter: Jonathan Kamke
>
> {{DeliveryImpl}} manages several doubly linked lists (of links, work and
> transportWork). However it does not function properly if removal is done out
> of order. It leaves object references in the next/previous pointers which on
> a large scale inhibit the system from garbage collecting these object, namely
> the {{DeliveryImpl}} object graph.
> In practice this was discovered when message consumers delay settlement of
> messages until after a period of time elapses (i.e. some async work is done
> in another thread). This causes out of order settlement to occur, leaving
> object references. Eventually the JVM will run out of memory and the process
> will crash. The heap can be examined to discover a large number of
> {{settled}} {{DeliveryImpl}}(s) which are holding references to themselves.
--
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-257) Messages delivered from a consume in client acknowledge mode cannot be acknowledged after the consumer is closed
[
https://issues.apache.org/jira/browse/QPIDJMS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855766#comment-15855766
]
ASF subversion and git services commented on QPIDJMS-257:
-
Commit e348e935e762cdaba294ac6382136a15bccf4231 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=e348e93 ]
QPIDJMS-257: update tests to remove race between adding handler and expected
frame arriving
> Messages delivered from a consume in client acknowledge mode cannot be
> acknowledged after the consumer is closed
>
>
> Key: QPIDJMS-257
> URL: https://issues.apache.org/jira/browse/QPIDJMS-257
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.11.1, 0.20.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
> Fix For: 0.21.0
>
>
> The JMS specification defines that a closing a consumer is to have no effect
> on the acknowledgement of messages delivered to the application. Currently
> for client acknowledge consumers we don't support this and a call to
> acknowledge on a delivered message will fail if the consumer was previously
> closed.
> From section 8.8 of the spec.
> {quote}
> * If the session mode is CLIENT_ACKNOWLEDGE then any messages
> delivered to the application may be acknowledged by calling
> acknowledge in the normal way. It makes no difference whether this
> occurs before or after the consumer is closed.
> {quote}
--
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
