[jira] [Commented] (DISPATCH-834) Create config tool to create/read/update/delete router config files

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204324#comment-16204324
 ] 

ASF subversion and git services commented on DISPATCH-834:
--

Commit 6f7107d4229eda1754f5cabb723ece09ca3b84af in qpid-dispatch's branch 
refs/heads/config-read-write from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=6f7107d ]

DISPATCH-834 Fix for Firefox stylesheet insertion


> Create config tool to create/read/update/delete router config files
> ---
>
> Key: DISPATCH-834
> URL: https://issues.apache.org/jira/browse/DISPATCH-834
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Console
>Affects Versions: 0.8.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> Create a UI and supporting program that reads/updates/writes/deletes router 
> config files.
> It should at least:
> - read all config files in a directory and display a topology
> - create new directories to store config files
> - create connectors/listeners between routers with correct host:port
> - allow creating/editing/deleting of external 
> listeners/connectors/sslProfiles/log sections
>  



--
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] [Resolved] (PROTON-1543) Various improvements to the docs and examples

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross resolved PROTON-1543.
-
Resolution: Fixed

> Various improvements to the docs and examples
> -
>
> Key: PROTON-1543
> URL: https://issues.apache.org/jira/browse/PROTON-1543
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: examples, proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
>  Labels: documentation
> Fix For: proton-c-0.18.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-1543) Various improvements to the docs and examples

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204316#comment-16204316
 ] 

ASF subversion and git services commented on PROTON-1543:
-

Commit 55564c80b2ea41b3fc4e7be4394a9b280b0cca89 in qpid-proton's branch 
refs/heads/master from [~jr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=55564c8 ]

PROTON-1543: Another slate of doc improvements

 - Transition the message properties and annotations API from
   unsettled to settled
 - Cleanups for messaging_handler and the multithreading page
 - Fix doc warnings and add missing docs
 - Handle new macros in doxygen preprocessing
 - Hide the currently problematic work docs


> Various improvements to the docs and examples
> -
>
> Key: PROTON-1543
> URL: https://issues.apache.org/jira/browse/PROTON-1543
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: examples, proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
>  Labels: documentation
> Fix For: proton-c-0.18.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-1620) TLS / SSL thread safety with proactor

[Alan Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204194#comment-16204194
 ] 

Alan Conway commented on PROTON-1620:
-

Sketch of a plan to make openssl.c thread safe is here, comments welcome:
https://github.com/apache/qpid-proton/pull/125/commits/7f8a64b78f946a7752943201aa67eaa13fc2b282

> TLS / SSL thread safety with proactor
> -
>
> Key: PROTON-1620
> URL: https://issues.apache.org/jira/browse/PROTON-1620
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.18.0
>Reporter: Cliff Jansen
>Priority: Critical
> Fix For: proton-c-0.18.0
>
>
> ssl_domain objects are semi-global.
> For example two connections simultaneously creating or releasing their own 
> private pn_ssl_t objects may mess up the refcount of the shared 
> pn_ssl_domain_t object leading to memory corruption or leaks.
> Windows schannel is further complicated by the OS internal refcounting of its 
> security context thingies.  That may get automatically solved by the above, 
> or may require a separate JIRA to track.  The same may apply to openssl.



--
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 #125: Steps to make openssl.c thread safe, marked w...

[alanconway]

GitHub user alanconway opened a pull request:

https://github.com/apache/qpid-proton/pull/125

Steps to make openssl.c thread safe, marked with FIXME comments.

This is not a real PR, just for comments.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alanconway/qpid-proton openssl-thread-safe

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/125.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #125


commit 7f8a64b78f946a7752943201aa67eaa13fc2b282
Author: Alan Conway 
Date:   2017-10-13T20:46:35Z

WIP: Marked up steps with FIXME comments.




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (DISPATCH-580) Log stats should be graphable

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated DISPATCH-580:
--
Fix Version/s: 1.1.0

> Log stats should be graphable
> -
>
> Key: DISPATCH-580
> URL: https://issues.apache.org/jira/browse/DISPATCH-580
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.8.0
>Reporter: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> The log statistics added with DISPATCH-553 are integers that could be 
> graphed. However, in order to graph them the console needs a 'graph' property 
> present in the schema for each graphable attribute in the logStats entity.
> Add a graph property to the counts in logStats.



--
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] [Assigned] (DISPATCH-580) Log stats should be graphable

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross reassigned DISPATCH-580:
-

Assignee: Ernest Allen

> Log stats should be graphable
> -
>
> Key: DISPATCH-580
> URL: https://issues.apache.org/jira/browse/DISPATCH-580
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.8.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> The log statistics added with DISPATCH-553 are integers that could be 
> graphed. However, in order to graph them the console needs a 'graph' property 
> present in the schema for each graphable attribute in the logStats entity.
> Add a graph property to the counts in logStats.



--
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] [Assigned] (DISPATCH-856) Return router's hostname as a read-only attribute on the router entity

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross reassigned DISPATCH-856:
-

Assignee: Ted Ross

> Return router's hostname as a read-only attribute on the router entity
> --
>
> Key: DISPATCH-856
> URL: https://issues.apache.org/jira/browse/DISPATCH-856
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Management Agent
>Reporter: Ernest Allen
>Assignee: Ted Ross
>Priority: Minor
> Fix For: 1.1.0
>
>
> It would be useful for the console to have the hostname of the machine on 
> which a router is running. Rather than a separate management call, I'd prefer 
> this to be returned as an attribute in the router entity.
> The console could then show routers that are co-located on a machine in the 
> same color.
> Ideally, there would also be a separate management call to return more 
> information about the router's host machine such as:
> - OS name and version
> - OS x86 or x64
> - machine date-time
> - machine timezone
> - memory installed
> - number of cpus
> - ipv4 and ipv6 addresses
> - geo location info (country/city or lon. lat.) (set in router's config file)
> I imagine there would be a policy that determines which of these are returned.



--
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] [Assigned] (DISPATCH-856) Return router's hostname as a read-only attribute on the router entity

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross reassigned DISPATCH-856:
-

Assignee: Ernest Allen  (was: Ted Ross)

> Return router's hostname as a read-only attribute on the router entity
> --
>
> Key: DISPATCH-856
> URL: https://issues.apache.org/jira/browse/DISPATCH-856
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Management Agent
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> It would be useful for the console to have the hostname of the machine on 
> which a router is running. Rather than a separate management call, I'd prefer 
> this to be returned as an attribute in the router entity.
> The console could then show routers that are co-located on a machine in the 
> same color.
> Ideally, there would also be a separate management call to return more 
> information about the router's host machine such as:
> - OS name and version
> - OS x86 or x64
> - machine date-time
> - machine timezone
> - memory installed
> - number of cpus
> - ipv4 and ipv6 addresses
> - geo location info (country/city or lon. lat.) (set in router's config file)
> I imagine there would be a policy that determines which of these are returned.



--
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] (DISPATCH-856) Return router's hostname as a read-only attribute on the router entity

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated DISPATCH-856:
--
Affects Version/s: (was: 1.1.0)

> Return router's hostname as a read-only attribute on the router entity
> --
>
> Key: DISPATCH-856
> URL: https://issues.apache.org/jira/browse/DISPATCH-856
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Management Agent
>Reporter: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> It would be useful for the console to have the hostname of the machine on 
> which a router is running. Rather than a separate management call, I'd prefer 
> this to be returned as an attribute in the router entity.
> The console could then show routers that are co-located on a machine in the 
> same color.
> Ideally, there would also be a separate management call to return more 
> information about the router's host machine such as:
> - OS name and version
> - OS x86 or x64
> - machine date-time
> - machine timezone
> - memory installed
> - number of cpus
> - ipv4 and ipv6 addresses
> - geo location info (country/city or lon. lat.) (set in router's config file)
> I imagine there would be a policy that determines which of these are returned.



--
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] (DISPATCH-856) Return router's hostname as a read-only attribute on the router entity

[Ted Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DISPATCH-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross updated DISPATCH-856:
--
Fix Version/s: 1.1.0

> Return router's hostname as a read-only attribute on the router entity
> --
>
> Key: DISPATCH-856
> URL: https://issues.apache.org/jira/browse/DISPATCH-856
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Management Agent
>Reporter: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> It would be useful for the console to have the hostname of the machine on 
> which a router is running. Rather than a separate management call, I'd prefer 
> this to be returned as an attribute in the router entity.
> The console could then show routers that are co-located on a machine in the 
> same color.
> Ideally, there would also be a separate management call to return more 
> information about the router's host machine such as:
> - OS name and version
> - OS x86 or x64
> - machine date-time
> - machine timezone
> - memory installed
> - number of cpus
> - ipv4 and ipv6 addresses
> - geo location info (country/city or lon. lat.) (set in router's config file)
> I imagine there would be a policy that determines which of these are returned.



--
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] [Resolved] (PROTON-1621) Enable C++11 example testing for C++11 build environments

[Alan Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway resolved PROTON-1621.
-
   Resolution: Fixed
Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.18.0

> Enable C++11 example testing for C++11 build environments
> -
>
> Key: PROTON-1621
> URL: https://issues.apache.org/jira/browse/PROTON-1621
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Justin Ross
>Assignee: Alan Conway
> Fix For: proton-c-0.18.0
>
>
> I have a C++11 Proton build, but the C++11 examples aren't exercised in the 
> tests.
> {noformat}
> [jross@localhost bld (ssorj-deprecations)]$ ctest -VV -R cpp-example-container
> UpdateCTestConfiguration  from 
> :/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Parse Config file:/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Parse Config file:/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Test project /home/jross/code/qpid-proton-ssorj/bld
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 25
> Start 25: cpp-example-container
> 25: Test command: /usr/bin/python 
> "/home/jross/code/qpid-proton-ssorj/proton-c/env.py" 
> "PYTHONPATH=/home/jross/code/qpid-proton-ssorj/tools/py" 
> "PATH=/home/jross/code/qpid-proton-ssorj/bld/examples/cpp:/home/jross/bin:/home/jross/.local/bin:/home/jross/.local/sbin:/home/jross/.local/node_modules/.bin:/usr/libexec/python2-sphinx:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin"
>  "--" "/usr/bin/python" 
> "/home/jross/code/qpid-proton-ssorj/examples/cpp/example_test.py" "-v" 
> "ContainerExampleTest"
> 25: Test timeout computed to be: 1500
> 25: test_encode_decode (__main__.ContainerExampleTest) ... ok
> 25: test_flow_control (__main__.ContainerExampleTest) ... ok
> 25: test_helloworld (__main__.ContainerExampleTest) ... ok
> 25: test_helloworld_direct (__main__.ContainerExampleTest) ... ok
> 25: test_message_properties (__main__.ContainerExampleTest) ... ok
> 25: test_multithreaded_client (__main__.ContainerExampleTest) ... skipped 
> 'not a  C++11 build'
> 25: test_multithreaded_client_flow_control (__main__.ContainerExampleTest) 
> ... skipped 'not a  C++11 build'
> 25: test_request_response (__main__.ContainerExampleTest) ... ok
> 25: test_request_response_direct (__main__.ContainerExampleTest) ... ok
> 25: test_scheduled_send (__main__.ContainerExampleTest) ... skipped 'not a  
> C++11 build'
> 25: test_scheduled_send_03 (__main__.ContainerExampleTest) ... ok
> 25: test_simple_recv_direct_send (__main__.ContainerExampleTest) ... ok
> 25: test_simple_recv_send (__main__.ContainerExampleTest) ... ok
> 25: test_simple_send_direct_recv (__main__.ContainerExampleTest) ... ok
> 25: test_simple_send_recv (__main__.ContainerExampleTest) ... ok
> 25: 
> 25: --
> 25: Ran 15 tests in 0.366s
> 25: 
> 25: OK (skipped=3)
> 1/2 Test #25: cpp-example-container    Passed0.42 sec
> {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] (PROTON-1621) Enable C++11 example testing for C++11 build environments

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204079#comment-16204079
 ] 

ASF subversion and git services commented on PROTON-1621:
-

Commit 6b2e7dcdbee49947f2fdcfa2a8f5950a9b87fbd3 in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=6b2e7dc ]

PROTON-1621: Enable C++11 example testing for C++11 build environments

Run the C++ compilier feature checking from the top level Cmake file so
examples and the C++ binding are built consistently.

NOTE: This does not address the problem of building examples with partially
capable compilers (MSVC < 13), only compilers that advertize full C++11 support.


> Enable C++11 example testing for C++11 build environments
> -
>
> Key: PROTON-1621
> URL: https://issues.apache.org/jira/browse/PROTON-1621
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Justin Ross
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> I have a C++11 Proton build, but the C++11 examples aren't exercised in the 
> tests.
> {noformat}
> [jross@localhost bld (ssorj-deprecations)]$ ctest -VV -R cpp-example-container
> UpdateCTestConfiguration  from 
> :/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Parse Config file:/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Parse Config file:/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Test project /home/jross/code/qpid-proton-ssorj/bld
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 25
> Start 25: cpp-example-container
> 25: Test command: /usr/bin/python 
> "/home/jross/code/qpid-proton-ssorj/proton-c/env.py" 
> "PYTHONPATH=/home/jross/code/qpid-proton-ssorj/tools/py" 
> "PATH=/home/jross/code/qpid-proton-ssorj/bld/examples/cpp:/home/jross/bin:/home/jross/.local/bin:/home/jross/.local/sbin:/home/jross/.local/node_modules/.bin:/usr/libexec/python2-sphinx:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin"
>  "--" "/usr/bin/python" 
> "/home/jross/code/qpid-proton-ssorj/examples/cpp/example_test.py" "-v" 
> "ContainerExampleTest"
> 25: Test timeout computed to be: 1500
> 25: test_encode_decode (__main__.ContainerExampleTest) ... ok
> 25: test_flow_control (__main__.ContainerExampleTest) ... ok
> 25: test_helloworld (__main__.ContainerExampleTest) ... ok
> 25: test_helloworld_direct (__main__.ContainerExampleTest) ... ok
> 25: test_message_properties (__main__.ContainerExampleTest) ... ok
> 25: test_multithreaded_client (__main__.ContainerExampleTest) ... skipped 
> 'not a  C++11 build'
> 25: test_multithreaded_client_flow_control (__main__.ContainerExampleTest) 
> ... skipped 'not a  C++11 build'
> 25: test_request_response (__main__.ContainerExampleTest) ... ok
> 25: test_request_response_direct (__main__.ContainerExampleTest) ... ok
> 25: test_scheduled_send (__main__.ContainerExampleTest) ... skipped 'not a  
> C++11 build'
> 25: test_scheduled_send_03 (__main__.ContainerExampleTest) ... ok
> 25: test_simple_recv_direct_send (__main__.ContainerExampleTest) ... ok
> 25: test_simple_recv_send (__main__.ContainerExampleTest) ... ok
> 25: test_simple_send_direct_recv (__main__.ContainerExampleTest) ... ok
> 25: test_simple_send_recv (__main__.ContainerExampleTest) ... ok
> 25: 
> 25: --
> 25: Ran 15 tests in 0.366s
> 25: 
> 25: OK (skipped=3)
> 1/2 Test #25: cpp-example-container    Passed0.42 sec
> {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] (PROTON-1369) Add deprecation warnings to the C++ binding

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204078#comment-16204078
 ] 

ASF subversion and git services commented on PROTON-1369:
-

Commit 38019a68af2a6cb98284a55fdfc6fe736614fb73 in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=38019a6 ]

PROTON-1369: [c++] remove deprecation attribute on void_function0

Was causing a deprecation warning on #include of work_queue because the the
deprecated function `work_queue::add(void_function0)` refers to the deprecated
class.

void_function0 is still deprecated in documentation and cannot be used except 
via
the deprecated work_queue::add function so effectively it is still well 
deprecated.


> Add deprecation warnings to the C++ binding
> ---
>
> Key: PROTON-1369
> URL: https://issues.apache.org/jira/browse/PROTON-1369
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Ken Giusti
>Assignee: Justin Ross
>Priority: Trivial
>  Labels: api
> Fix For: proton-c-0.18.0
>
>
> Once PROTON-225 is implemented, we should eventually remove the old 
> interfaces after marking them deprecated.
> Example:
> #ifdef __GNUC__
> #define DEPRECATED(func) func __attribute__ ((deprecated))
> #elif defined(_MSC_VER)
> #define DEPRECATED(func) __declspec(deprecated) func
> #else
> #pragma message("WARNING: You need to implement DEPRECATED for this compiler")
> #define DEPRECATED(func) func
> #endif



--
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] (DISPATCH-834) Create config tool to create/read/update/delete router config files

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/DISPATCH-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204027#comment-16204027
 ] 

ASF subversion and git services commented on DISPATCH-834:
--

Commit 2f5ec0d8948d35c09deb4bcc7a02cfeb0a8341c4 in qpid-dispatch's branch 
refs/heads/config-read-write from [~eallen]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=2f5ec0d ]

DISPATCH-834 Now with ability to deploy with sudo password passed in


> Create config tool to create/read/update/delete router config files
> ---
>
> Key: DISPATCH-834
> URL: https://issues.apache.org/jira/browse/DISPATCH-834
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Console
>Affects Versions: 0.8.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>
> Create a UI and supporting program that reads/updates/writes/deletes router 
> config files.
> It should at least:
> - read all config files in a directory and display a topology
> - create new directories to store config files
> - create connectors/listeners between routers with correct host:port
> - allow creating/editing/deleting of external 
> listeners/connectors/sslProfiles/log sections
>  



--
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] [Resolved] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross resolved PROTON-1630.
-
Resolution: Fixed

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp"
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] (PROTON-1603) Windows C++ container does not compile multithreaded

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203904#comment-16203904
 ] 

Justin Ross commented on PROTON-1603:
-

This appears to be preventing the following examples from building on Windows:

 - scheduled_send
 - multithreaded_client
 - multithreaded_client_flow_control

Not that that is necessarily news.

> Windows C++ container does not compile multithreaded
> 
>
> Key: PROTON-1603
> URL: https://issues.apache.org/jira/browse/PROTON-1603
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
>Reporter: Cliff Jansen
>Assignee: Andrew Stitcher
> Fix For: proton-c-0.18.0
>
>
> For both VS2013 and VS2017 cmake proclaims:
>   HAS_STD_THREAD - Success
>   HAS_STD_MUTEX - Success
>   HAS_STD_ATOMIC - Success
> yet proactor_container_impl.cpp does not compile
> PN_CPP_SUPPORTS_THREADS sections.



--
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-1603) Windows C++ container does not compile multithreaded

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1603:

Fix Version/s: (was: proton-c-0.19.0)
   proton-c-0.18.0

> Windows C++ container does not compile multithreaded
> 
>
> Key: PROTON-1603
> URL: https://issues.apache.org/jira/browse/PROTON-1603
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
>Reporter: Cliff Jansen
>Assignee: Andrew Stitcher
> Fix For: proton-c-0.18.0
>
>
> For both VS2013 and VS2017 cmake proclaims:
>   HAS_STD_THREAD - Success
>   HAS_STD_MUTEX - Success
>   HAS_STD_ATOMIC - Success
> yet proactor_container_impl.cpp does not compile
> PN_CPP_SUPPORTS_THREADS sections.



--
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-1620) TLS / SSL thread safety with proactor

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1620:

Priority: Critical  (was: Major)

> TLS / SSL thread safety with proactor
> -
>
> Key: PROTON-1620
> URL: https://issues.apache.org/jira/browse/PROTON-1620
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.18.0
>Reporter: Cliff Jansen
>Priority: Critical
> Fix For: proton-c-0.18.0
>
>
> ssl_domain objects are semi-global.
> For example two connections simultaneously creating or releasing their own 
> private pn_ssl_t objects may mess up the refcount of the shared 
> pn_ssl_domain_t object leading to memory corruption or leaks.
> Windows schannel is further complicated by the OS internal refcounting of its 
> security context thingies.  That may get automatically solved by the above, 
> or may require a separate JIRA to track.  The same may apply to openssl.



--
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-1620) TLS / SSL thread safety with proactor

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1620:

Fix Version/s: proton-c-0.18.0

> TLS / SSL thread safety with proactor
> -
>
> Key: PROTON-1620
> URL: https://issues.apache.org/jira/browse/PROTON-1620
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.18.0
>Reporter: Cliff Jansen
> Fix For: proton-c-0.18.0
>
>
> ssl_domain objects are semi-global.
> For example two connections simultaneously creating or releasing their own 
> private pn_ssl_t objects may mess up the refcount of the shared 
> pn_ssl_domain_t object leading to memory corruption or leaks.
> Windows schannel is further complicated by the OS internal refcounting of its 
> security context thingies.  That may get automatically solved by the above, 
> or may require a separate JIRA to track.  The same may apply to openssl.



--
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] [Assigned] (PROTON-1621) Enable C++11 example testing for C++11 build environments

[Alan Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway reassigned PROTON-1621:
---

Assignee: Alan Conway  (was: Andrew Stitcher)

> Enable C++11 example testing for C++11 build environments
> -
>
> Key: PROTON-1621
> URL: https://issues.apache.org/jira/browse/PROTON-1621
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Justin Ross
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> I have a C++11 Proton build, but the C++11 examples aren't exercised in the 
> tests.
> {noformat}
> [jross@localhost bld (ssorj-deprecations)]$ ctest -VV -R cpp-example-container
> UpdateCTestConfiguration  from 
> :/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Parse Config file:/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
> :/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Parse Config file:/home/jross/code/qpid-proton-ssorj/bld/DartConfiguration.tcl
> Test project /home/jross/code/qpid-proton-ssorj/bld
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 25
> Start 25: cpp-example-container
> 25: Test command: /usr/bin/python 
> "/home/jross/code/qpid-proton-ssorj/proton-c/env.py" 
> "PYTHONPATH=/home/jross/code/qpid-proton-ssorj/tools/py" 
> "PATH=/home/jross/code/qpid-proton-ssorj/bld/examples/cpp:/home/jross/bin:/home/jross/.local/bin:/home/jross/.local/sbin:/home/jross/.local/node_modules/.bin:/usr/libexec/python2-sphinx:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin"
>  "--" "/usr/bin/python" 
> "/home/jross/code/qpid-proton-ssorj/examples/cpp/example_test.py" "-v" 
> "ContainerExampleTest"
> 25: Test timeout computed to be: 1500
> 25: test_encode_decode (__main__.ContainerExampleTest) ... ok
> 25: test_flow_control (__main__.ContainerExampleTest) ... ok
> 25: test_helloworld (__main__.ContainerExampleTest) ... ok
> 25: test_helloworld_direct (__main__.ContainerExampleTest) ... ok
> 25: test_message_properties (__main__.ContainerExampleTest) ... ok
> 25: test_multithreaded_client (__main__.ContainerExampleTest) ... skipped 
> 'not a  C++11 build'
> 25: test_multithreaded_client_flow_control (__main__.ContainerExampleTest) 
> ... skipped 'not a  C++11 build'
> 25: test_request_response (__main__.ContainerExampleTest) ... ok
> 25: test_request_response_direct (__main__.ContainerExampleTest) ... ok
> 25: test_scheduled_send (__main__.ContainerExampleTest) ... skipped 'not a  
> C++11 build'
> 25: test_scheduled_send_03 (__main__.ContainerExampleTest) ... ok
> 25: test_simple_recv_direct_send (__main__.ContainerExampleTest) ... ok
> 25: test_simple_recv_send (__main__.ContainerExampleTest) ... ok
> 25: test_simple_send_direct_recv (__main__.ContainerExampleTest) ... ok
> 25: test_simple_send_recv (__main__.ContainerExampleTest) ... ok
> 25: 
> 25: --
> 25: Ran 15 tests in 0.366s
> 25: 
> 25: OK (skipped=3)
> 1/2 Test #25: cpp-example-container    Passed0.42 sec
> {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] [Updated] (QPIDJMS-335) SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password during processing

[Robbie Gemmell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPIDJMS-335:
---
Fix Version/s: 0.27.0

> SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password 
> during processing
> --
>
> Key: QPIDJMS-335
> URL: https://issues.apache.org/jira/browse/QPIDJMS-335
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.27.0
>
>
> Per discussion on 
> http://mail-archives.apache.org/mod_mbox/qpid-users/201710.mbox/%3C1507290028737-0.post%40n2.nabble.com%3E
>  the client is erroneously escaping "=" and "," during password handling, 
> whereas the SCRAM mechanisms only require this for the username and some 
> other cases, causing authentication to fail when they are present as the 
> wrong value is used to compute the details sent to the server.



--
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] [Assigned] (QPIDJMS-335) SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password during processing

[Robbie Gemmell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell reassigned QPIDJMS-335:
--

Assignee: Robbie Gemmell

> SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password 
> during processing
> --
>
> Key: QPIDJMS-335
> URL: https://issues.apache.org/jira/browse/QPIDJMS-335
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.27.0
>
>
> Per discussion on 
> http://mail-archives.apache.org/mod_mbox/qpid-users/201710.mbox/%3C1507290028737-0.post%40n2.nabble.com%3E
>  the client is erroneously escaping "=" and "," during password handling, 
> whereas the SCRAM mechanisms only require this for the username and some 
> other cases, causing authentication to fail when they are present as the 
> wrong value is used to compute the details sent to the server.



--
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] [Resolved] (QPIDJMS-336) Refine failover reconnect behavior

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved QPIDJMS-336.
--
Resolution: Fixed

> Refine failover reconnect behavior
> --
>
> Key: QPIDJMS-336
> URL: https://issues.apache.org/jira/browse/QPIDJMS-336
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 0.27.0
>
>
> The current failover behavior attempt to connect to one URI from the possible 
> list of failover URIs when attempting to reestablish the connect before it 
> applies the configured reconnect delay.  Instead it should attempt the full 
> batch before performing delay and backoff handling.  
> Also the reconnect attempts are counted per URI instead of once for each 
> cycle though the batch of available URIs meaning that if the value is to low 
> it might not be able to try all of the configured URIs before reaching the 
> max attempts.  Track the attempts for the complete batch instead to allow all 
> to be tried at least once before giving up.



--
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-7913) [Java Broker] Improve message recovery logging

[Alex Rudyy (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203790#comment-16203790
 ] 

Alex Rudyy commented on QPID-7913:
--

I think that aggregation of warnings for unknown message instances per queue 
could be a bad idea.
With current implementation, the warning is issued per message instance before 
message  instance is deleted. Thus, in situation when Broker  runs out of 
memory, all the warnings will be logged. If we change the recoverers to issue 
warning  per queue for unknown message instances and OOM error is thrown in the 
middle of recovery, the information about deleted message instances might not 
be logged to the end users. I attached a patch which allow aggregation of the 
information about the deleted message instances per queue and logging warnings 
per each queue but I am not sure that we should commit the patch.

> [Java Broker] Improve message recovery logging
> --
>
> Key: QPID-7913
> URL: https://issues.apache.org/jira/browse/QPID-7913
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.0
>
> Attachments: 
> 0001-QPID-7913-Java-Broker-Log-a-single-warning-per-queue.patch
>
>
> Qpid broker message store recoverer generates a warning for every discarded 
> message as below
> {noformat}
> WARN  [VirtualHostNode-default-Config] 
> (o.a.q.s.v.SynchronousMessageStoreRecoverer) - Message id 1183 in log 
> references queue with id de12d20b-bf6c-4d7b-a216-f613ee0635ae which is not in 
> the configuration, entry will be discarded
> {noformat}
> Potentially, the logging can be improved to generate a single log entry per 
> queue rather that per each message, where a number of discarded messages and 
> their ids can be 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] [Updated] (PROTON-1631) [cpp] Stopping container in on_container_start after opening a socket will hang with libuv io

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1631:

Fix Version/s: proton-c-0.19.0

> [cpp] Stopping container in on_container_start after opening a socket will 
> hang with libuv io
> -
>
> Key: PROTON-1631
> URL: https://issues.apache.org/jira/browse/PROTON-1631
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, libuv-1.14.1, git tip at commit 
> 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master) PROTON-1592 : 
> [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Cliff Jansen
> Fix For: proton-c-0.19.0
>
>
> Make yourself a libuv build with
> {noformat}
> cmake .. -DBUILD_GO=OFF -DCMAKE_BUILD_TYPE=Release -GNinja -DPROACTOR=libuv
> {noformat}
> Run the following test
> {noformat}
> struct less_immediate_stop_tester : public proton::messaging_handler {
> listen_port port;
> proton::listener listener;
> bool done;
> int scheduled_work;
> less_immediate_stop_tester() : done(false), scheduled_work(0) {}
> void connect(proton::container* c) {
> }
> void on_container_start(proton::container& c) PN_CPP_OVERRIDE {
> listener = c.listen(port.url());
> c.connect(port.url("localhost"));
> c.stop();
> }
> };
> // FIXME: this test has some Invalid reads in Valgrind  // with 
> t.listener.stop() line commented out it doesn't
> int test_container_less_immediate_stop() {
> less_immediate_stop_tester t;
> proton::container c(t);
> c.run();
> //t.listener.stop(); // saw this done in another test...
> return 0;
> }
> {noformat}
> It will hang with the following output
> {nofornat}
> ninja && PN_TRACE_FRM=1 proton-c/bindings/cpp/container_test && echo pass
> [...]
> TEST: test_container_less_immediate_stop() 
> [0x17cc4c0]:  -> AMQP 
> [0x17cc4c0]:0 -> @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", hostname="localhost", 
> channel-max=32767] 
> [0x17c9110]:  <- AMQP 
> [0x17c9110]:0 <- @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", hostname="localhost", 
> channel-max=32767] 
> [0x17c9110]:  -> AMQP 
> [0x17c9110]:0 -> @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", channel-max=32767] 
> [0x17cc4c0]:  <- AMQP 
> [0x17cc4c0]:0 <- @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", channel-max=32767] 
> {nofornat}
> Now, this exact code does _not_ hang with epoll io.



--
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-1630) #include "proton/default_container.hpp" does not compile

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203786#comment-16203786
 ] 

ASF subversion and git services commented on PROTON-1630:
-

Commit 5c4962bf7a13dc99c2ae9941b4eea3ae644436f6 in qpid-proton's branch 
refs/heads/master from [~jr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5c4962b ]

PROTON-1630: Add a missing include


> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp"
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] (PROTON-1369) Add deprecation warnings to the C++ binding

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203787#comment-16203787
 ] 

ASF GitHub Bot commented on PROTON-1369:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/120


> Add deprecation warnings to the C++ binding
> ---
>
> Key: PROTON-1369
> URL: https://issues.apache.org/jira/browse/PROTON-1369
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Ken Giusti
>Assignee: Justin Ross
>Priority: Trivial
>  Labels: api
> Fix For: proton-c-0.18.0
>
>
> Once PROTON-225 is implemented, we should eventually remove the old 
> interfaces after marking them deprecated.
> Example:
> #ifdef __GNUC__
> #define DEPRECATED(func) func __attribute__ ((deprecated))
> #elif defined(_MSC_VER)
> #define DEPRECATED(func) __declspec(deprecated) func
> #else
> #pragma message("WARNING: You need to implement DEPRECATED for this compiler")
> #define DEPRECATED(func) func
> #endif



--
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 #120: PROTON-1369: Add deprecation warnings to the ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/120


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1630:

Fix Version/s: proton-c-0.18.0

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp"
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Updated] (QPID-7913) [Java Broker] Improve message recovery logging

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-7913:
-
Attachment: 0001-QPID-7913-Java-Broker-Log-a-single-warning-per-queue.patch

> [Java Broker] Improve message recovery logging
> --
>
> Key: QPID-7913
> URL: https://issues.apache.org/jira/browse/QPID-7913
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.0
>
> Attachments: 
> 0001-QPID-7913-Java-Broker-Log-a-single-warning-per-queue.patch
>
>
> Qpid broker message store recoverer generates a warning for every discarded 
> message as below
> {noformat}
> WARN  [VirtualHostNode-default-Config] 
> (o.a.q.s.v.SynchronousMessageStoreRecoverer) - Message id 1183 in log 
> references queue with id de12d20b-bf6c-4d7b-a216-f613ee0635ae which is not in 
> the configuration, entry will be discarded
> {noformat}
> Potentially, the logging can be improved to generate a single log entry per 
> queue rather that per each message, where a number of discarded messages and 
> their ids can be 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] [Assigned] (PROTON-1629) [cpp] proton::container is not move constructible

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reassigned PROTON-1629:
---

Assignee: Andrew Stitcher  (was: Cliff Jansen)

> [cpp] proton::container is not move constructible
> -
>
> Key: PROTON-1629
> URL: https://issues.apache.org/jira/browse/PROTON-1629
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at 
> commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)
>  PROTON-1592: [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: proton-c-0.19.0
>
>
> Following C++11 code does not compile
> {code}
> auto handler = proton::messaging_handler();
> auto container = proton::container(handler); // container is not move 
> constructible
> {code}
> Error from GCC is
> {noformat}
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:
>  In function ‘int {anonymous}::test_container_schedule_multithreaded()’:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:591:47:
>  error: use of deleted function ‘proton::container::container(const 
> proton::container&)’
>  auto container = proton::container(handler); // container is not move 
> constructible
>^
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:28:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:55:27:
>  note: ‘proton::container::container(const proton::container&)’ is implicitly 
> deleted because the default definition would be ill-formed:
>  class PN_CPP_CLASS_EXTERN container {
>^
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:55:27:
>  error: use of deleted function ‘constexpr 
> proton::internal::pn_unique_ptr::pn_unique_ptr(const 
> proton::internal::pn_unique_ptr&)’
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/connection_options.hpp:29:0,
>  from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:27:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/./internal/pn_unique_ptr.hpp:43:26:
>  note: ‘constexpr 
> proton::internal::pn_unique_ptr::pn_unique_ptr(const 
> proton::internal::pn_unique_ptr&)’ is implicitly 
> declared as deleted because 
> ‘proton::internal::pn_unique_ptr’ declares a move 
> constructor or move assignment operator
>  template  class pn_unique_ptr {
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> {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] [Updated] (PROTON-1629) [cpp] proton::container is not move constructible

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1629:

Fix Version/s: proton-c-0.19.0

> [cpp] proton::container is not move constructible
> -
>
> Key: PROTON-1629
> URL: https://issues.apache.org/jira/browse/PROTON-1629
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at 
> commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)
>  PROTON-1592: [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: proton-c-0.19.0
>
>
> Following C++11 code does not compile
> {code}
> auto handler = proton::messaging_handler();
> auto container = proton::container(handler); // container is not move 
> constructible
> {code}
> Error from GCC is
> {noformat}
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:
>  In function ‘int {anonymous}::test_container_schedule_multithreaded()’:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:591:47:
>  error: use of deleted function ‘proton::container::container(const 
> proton::container&)’
>  auto container = proton::container(handler); // container is not move 
> constructible
>^
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:28:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:55:27:
>  note: ‘proton::container::container(const proton::container&)’ is implicitly 
> deleted because the default definition would be ill-formed:
>  class PN_CPP_CLASS_EXTERN container {
>^
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:55:27:
>  error: use of deleted function ‘constexpr 
> proton::internal::pn_unique_ptr::pn_unique_ptr(const 
> proton::internal::pn_unique_ptr&)’
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/connection_options.hpp:29:0,
>  from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:27:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/./internal/pn_unique_ptr.hpp:43:26:
>  note: ‘constexpr 
> proton::internal::pn_unique_ptr::pn_unique_ptr(const 
> proton::internal::pn_unique_ptr&)’ is implicitly 
> declared as deleted because 
> ‘proton::internal::pn_unique_ptr’ declares a move 
> constructor or move assignment operator
>  template  class pn_unique_ptr {
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> {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] [Resolved] (QPID-7967) [Java Broker] Internal Oracle TLS classes leaked per connection when connecting the Qpid JMS Client

[Keith Wall (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall resolved QPID-7967.
--
Resolution: Fixed

Looks reasonable to me.

> [Java Broker] Internal Oracle TLS classes leaked per connection when 
> connecting the Qpid JMS Client
> ---
>
> Key: QPID-7967
> URL: https://issues.apache.org/jira/browse/QPID-7967
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
> Environment: Java version "1.8.0_144"
> Mac OS X 10.12.6
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Fix For: qpid-java-broker-7.0.0
>
>
> Performing leak analysis shows that the following internal TLS classes are 
> leaked, once per TLS connection, when connecting using the Qpid JMS Client 
> 0.26.0 over AMQP 1.0 with TLS. The same leak was not apparent when connecting 
> the older Qpid JMS AMQP 0-x client.
> The classes are:
> # sun.security.ssl.SessionId
> # sun.security.ssl.SSLSessionImpl
> The test is run with the following command:
> {code}
> mvn exec:java -pl tools  -Dstresstest=qpid-jms-client  
> -Dexec.args="jndiProperties=stress-test-client-qpid-jms-client.properties 
> jndiConnectionFactory=qpidConnectionFactoryTls connections=100" 
> -Djavax.net.ssl.trustStore=/Users/keith/Downloads/myks.jks 
> -Dqpid-jms-client-version=0.26.0
> {code}
> It seems there is session caching going on within the JDK.  The cache size 
> and timeout looks to be tuneable with 
> {{javax.net.ssl.SSLContext#getServerSessionContext}}.  The default timeout is 
> 86400s (1day) and a session cache size of 0 (unbounded). I suspect if Broker 
> had a sufficiently large number of TLS connections over a short time period, 
> memory may be exhausted.
> -I don't currently understand why the behaviour is different between the 
> old/new JMS client-.  Edit - see comment below.



--
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-1628) [cpp] Stopping container in on_container_start will hang

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1628:

Fix Version/s: proton-c-0.19.0

> [cpp] Stopping container in on_container_start will hang
> 
>
> Key: PROTON-1628
> URL: https://issues.apache.org/jira/browse/PROTON-1628
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, epoll io, master tip at 
> 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 PROTON-1592: [python] restore 
> original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Cliff Jansen
> Fix For: proton-c-0.19.0
>
>
> {code}
> class immediate_stop_tester : public proton::messaging_handler {
> public:
> void on_container_start(proton::container ) PN_CPP_OVERRIDE {
> c.stop();
> }
> };
> int test_container_immediate_stop() {
> immediate_stop_tester t;
> proton::container(t).run();  // will hang
> return 0;
> }
> {code}



--
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] [Assigned] (PROTON-1628) [cpp] Stopping container in on_container_start will hang

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reassigned PROTON-1628:
---

Assignee: Alan Conway  (was: Cliff Jansen)

> [cpp] Stopping container in on_container_start will hang
> 
>
> Key: PROTON-1628
> URL: https://issues.apache.org/jira/browse/PROTON-1628
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, epoll io, master tip at 
> 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 PROTON-1592: [python] restore 
> original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> {code}
> class immediate_stop_tester : public proton::messaging_handler {
> public:
> void on_container_start(proton::container ) PN_CPP_OVERRIDE {
> c.stop();
> }
> };
> int test_container_immediate_stop() {
> immediate_stop_tester t;
> proton::container(t).run();  // will hang
> return 0;
> }
> {code}



--
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-1630) #include "proton/default_container.hpp" does not compile

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203746#comment-16203746
 ] 

Justin Ross commented on PROTON-1630:
-

Reproduced on gcc 7.2 by putting the default_container import before any other 
imports.

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp"
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Updated] (QPID-7832) Refactor store/protocol API using Collection

[Lorenz Quack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lorenz Quack updated QPID-7832:
---
Attachment: 0001-QPID-7832-Java-Broker-Refactor-store-protocol-API-us.patch

> Refactor store/protocol API using Collection
> -
>
> Key: QPID-7832
> URL: https://issues.apache.org/jira/browse/QPID-7832
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.0
>
> Attachments: 
> 0001-QPID-7832-Java-Broker-Refactor-store-protocol-API-us.patch
>
>
> Store/protocol APIs have gradually been evolving to accept/return message 
> content/message metadata in terms of an ordered list of QBBs.  This has lead 
> to use of helper methods such as those in QBBUtils which read from a list of 
> buffers rather than a single one.
> This would be better refactored.   QpidByteBuffer should be an interface.  
> This would allow a concrete implementation CompositeQpidByteBuffer which is 
> backed by a list produced by the store or network IO.



--
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-7913) [Java Broker] Improve message recovery logging

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203742#comment-16203742
 ] 

ASF subversion and git services commented on QPID-7913:
---

Commit a0eccb5cf3f508fc7add59ff8785077c6c1da2a5 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=a0eccb5 ]

QPID-7913: [Java Broker] Log warning only for persistent unused messages


> [Java Broker] Improve message recovery logging
> --
>
> Key: QPID-7913
> URL: https://issues.apache.org/jira/browse/QPID-7913
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.0
>
>
> Qpid broker message store recoverer generates a warning for every discarded 
> message as below
> {noformat}
> WARN  [VirtualHostNode-default-Config] 
> (o.a.q.s.v.SynchronousMessageStoreRecoverer) - Message id 1183 in log 
> references queue with id de12d20b-bf6c-4d7b-a216-f613ee0635ae which is not in 
> the configuration, entry will be discarded
> {noformat}
> Potentially, the logging can be improved to generate a single log entry per 
> queue rather that per each message, where a number of discarded messages and 
> their ids can be 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] [Comment Edited] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[JIRA]

[ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203702#comment-16203702
 ] 

Jiri Daněk edited comment on PROTON-1630 at 10/13/17 3:55 PM:
--

[~justi9]] nixos, any problems with that version? It has approx 10 versions of 
gcc ranging from 4.5.4 to 7.2.0. Default is some 6.x.y, I think.

Anyways, happens with clang 4.0.1 too

{noformat}
/src/container_test.cpp.o.d -o 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o -c 
../proton-c/bindings/cpp/src/container_test.cpp
In file included from ../proton-c/bindings/cpp/src/container_test.cpp:20:
../proton-c/bindings/cpp/include/proton/default_container.hpp:31:43: error: 
expected parameter declarator
typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
default_container;
  ^
../proton-c/bindings/cpp/include/proton/default_container.hpp:31:43: error: 
expected ')'
../proton-c/bindings/cpp/include/proton/default_container.hpp:31:42: note: to 
match this '('
typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
default_container;
 ^
../proton-c/bindings/cpp/include/proton/default_container.hpp:31:70: error: 
expected function body after function declarator
typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
default_container;
 ^
3 errors generated
{noformat}


was (Author: jdanek):
[~justi9]] nixos, any problems with that version? It has approx 10 versions of 
gcc ranging from 4.5.4 to 7.2.0. Default is some 6.x.y, I think.

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp"
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Updated] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[JIRA]

 [ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jiri Daněk updated PROTON-1630:
---
Description: 
Add the following include to your application, or say {{container_test.cpp}} 
proton file.

{code}
#include "proton/default_container.hpp"
{code}

Attempt to compile and behold the error

{noformat}
In file included from 
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
 error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
instead)
 typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
default_container;
  ^
make[3]: *** 
[proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
Error 1
make[2]: *** [CMakeFiles/Makefile2:1609: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:1621: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
{noformat}

  was:
Add the following include to your application, or say {{container_test.cpp}} 
proton file.

{code}
#include "proton/default_container.hpp" does not compile
{code}

Attempt to compile and behold the error

{noformat}
In file included from 
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
 error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
instead)
 typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
default_container;
  ^
make[3]: *** 
[proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
Error 1
make[2]: *** [CMakeFiles/Makefile2:1609: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:1621: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
{noformat}


> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp"
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Updated] (PROTON-1631) [cpp] Stopping container in on_container_start after opening a socket will hang with libuv io

[JIRA]

 [ 
https://issues.apache.org/jira/browse/PROTON-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jiri Daněk updated PROTON-1631:
---
Issue Type: Bug  (was: Improvement)

> [cpp] Stopping container in on_container_start after opening a socket will 
> hang with libuv io
> -
>
> Key: PROTON-1631
> URL: https://issues.apache.org/jira/browse/PROTON-1631
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, libuv-1.14.1, git tip at commit 
> 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master) PROTON-1592 : 
> [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Cliff Jansen
>
> Make yourself a libuv build with
> {noformat}
> cmake .. -DBUILD_GO=OFF -DCMAKE_BUILD_TYPE=Release -GNinja -DPROACTOR=libuv
> {noformat}
> Run the following test
> {noformat}
> struct less_immediate_stop_tester : public proton::messaging_handler {
> listen_port port;
> proton::listener listener;
> bool done;
> int scheduled_work;
> less_immediate_stop_tester() : done(false), scheduled_work(0) {}
> void connect(proton::container* c) {
> }
> void on_container_start(proton::container& c) PN_CPP_OVERRIDE {
> listener = c.listen(port.url());
> c.connect(port.url("localhost"));
> c.stop();
> }
> };
> // FIXME: this test has some Invalid reads in Valgrind  // with 
> t.listener.stop() line commented out it doesn't
> int test_container_less_immediate_stop() {
> less_immediate_stop_tester t;
> proton::container c(t);
> c.run();
> //t.listener.stop(); // saw this done in another test...
> return 0;
> }
> {noformat}
> It will hang with the following output
> {nofornat}
> ninja && PN_TRACE_FRM=1 proton-c/bindings/cpp/container_test && echo pass
> [...]
> TEST: test_container_less_immediate_stop() 
> [0x17cc4c0]:  -> AMQP 
> [0x17cc4c0]:0 -> @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", hostname="localhost", 
> channel-max=32767] 
> [0x17c9110]:  <- AMQP 
> [0x17c9110]:0 <- @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", hostname="localhost", 
> channel-max=32767] 
> [0x17c9110]:  -> AMQP 
> [0x17c9110]:0 -> @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", channel-max=32767] 
> [0x17cc4c0]:  <- AMQP 
> [0x17cc4c0]:0 <- @open(16) 
> [container-id="e038fe4b-9996-4874-be7d-50274e1e193e", channel-max=32767] 
> {nofornat}
> Now, this exact code does _not_ hang with epoll io.



--
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] [Comment Edited] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[JIRA]

[ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203702#comment-16203702
 ] 

Jiri Daněk edited comment on PROTON-1630 at 10/13/17 3:30 PM:
--

[~justi9]] nixos, any problems with that version? It has approx 10 versions of 
gcc ranging from 4.5.4 to 7.2.0. Default is some 6.x.y, I think.


was (Author: jdanek):
[~justi9]] nixos, any problems with that? It has approx 10 versions of gcc 
ranging from 4.5.4 to 7.2.0. Default is some 6.x.y, I think.

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp" does not compile
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[JIRA]

[ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203702#comment-16203702
 ] 

Jiri Daněk commented on PROTON-1630:


[~justi9]] nixos, any problems with that? It has approx 10 versions of gcc 
ranging from 4.5.4 to 7.2.0. Default is some 6.x.y, I think.

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp" does not compile
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Updated] (QPIDJMS-340) Build fails with group id is too big error

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish updated QPIDJMS-340:
-
Fix Version/s: 0.27.0

> Build fails with group id is too big error
> --
>
> Key: QPIDJMS-340
> URL: https://issues.apache.org/jira/browse/QPIDJMS-340
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Christopher L. Shannon
>Priority: Minor
> Fix For: 0.27.0
>
>
> In my environment when I'm trying to build from source the maven-assembly 
> plugin fails because my group id is apparently too big.  The solution for 
> this is to configure the maven-assembly-plugin with 
> {{posix}}



--
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] [Resolved] (QPIDJMS-340) Build fails with group id is too big error

[Christopher L. Shannon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christopher L. Shannon resolved QPIDJMS-340.

Resolution: Fixed

> Build fails with group id is too big error
> --
>
> Key: QPIDJMS-340
> URL: https://issues.apache.org/jira/browse/QPIDJMS-340
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Christopher L. Shannon
>Priority: Minor
> Fix For: 0.27.0
>
>
> In my environment when I'm trying to build from source the maven-assembly 
> plugin fails because my group id is apparently too big.  The solution for 
> this is to configure the maven-assembly-plugin with 
> {{posix}}



--
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-1630) #include "proton/default_container.hpp" does not compile

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203695#comment-16203695
 ] 

Justin Ross commented on PROTON-1630:
-

[~jdanek], what OS version has gcc 7.0.1?

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp" does not compile
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Created] (PROTON-1631) [cpp] Stopping container in on_container_start after opening a socket will hang with libuv io

[JIRA]

Jiri Daněk created PROTON-1631:
--

 Summary: [cpp] Stopping container in on_container_start after 
opening a socket will hang with libuv io
 Key: PROTON-1631
 URL: https://issues.apache.org/jira/browse/PROTON-1631
 Project: Qpid Proton
  Issue Type: Improvement
  Components: cpp-binding
Affects Versions: proton-c-0.18.0
 Environment: Linux, libuv-1.14.1, git tip at commit 
72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master) PROTON-1592 : 
[python] restore original tx_recv.py example
Reporter: Jiri Daněk
Assignee: Cliff Jansen


Make yourself a libuv build with

{noformat}
cmake .. -DBUILD_GO=OFF -DCMAKE_BUILD_TYPE=Release -GNinja -DPROACTOR=libuv
{noformat}

Run the following test

{noformat}
struct less_immediate_stop_tester : public proton::messaging_handler {
listen_port port;
proton::listener listener;
bool done;
int scheduled_work;

less_immediate_stop_tester() : done(false), scheduled_work(0) {}

void connect(proton::container* c) {
}

void on_container_start(proton::container& c) PN_CPP_OVERRIDE {
listener = c.listen(port.url());
c.connect(port.url("localhost"));
c.stop();
}
};

// FIXME: this test has some Invalid reads in Valgrind  // with 
t.listener.stop() line commented out it doesn't
int test_container_less_immediate_stop() {
less_immediate_stop_tester t;
proton::container c(t);
c.run();
//t.listener.stop(); // saw this done in another test...
return 0;
}
{noformat}

It will hang with the following output

{nofornat}
ninja && PN_TRACE_FRM=1 proton-c/bindings/cpp/container_test && echo pass
[...]
TEST: test_container_less_immediate_stop() 
[0x17cc4c0]:  -> AMQP 
[0x17cc4c0]:0 -> @open(16) 
[container-id="e038fe4b-9996-4874-be7d-50274e1e193e", hostname="localhost", 
channel-max=32767] 
[0x17c9110]:  <- AMQP 
[0x17c9110]:0 <- @open(16) 
[container-id="e038fe4b-9996-4874-be7d-50274e1e193e", hostname="localhost", 
channel-max=32767] 
[0x17c9110]:  -> AMQP 
[0x17c9110]:0 -> @open(16) 
[container-id="e038fe4b-9996-4874-be7d-50274e1e193e", channel-max=32767] 
[0x17cc4c0]:  <- AMQP 
[0x17cc4c0]:0 <- @open(16) 
[container-id="e038fe4b-9996-4874-be7d-50274e1e193e", channel-max=32767] 
{nofornat}

Now, this exact code does _not_ hang with epoll io.



--
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-1630) #include "proton/default_container.hpp" does not compile

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1630:

Issue Type: Bug  (was: Improvement)

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp" does not compile
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Assigned] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross reassigned PROTON-1630:
---

Assignee: Justin Ross  (was: Cliff Jansen)

> #include "proton/default_container.hpp" does not compile
> 
>
> Key: PROTON-1630
> URL: https://issues.apache.org/jira/browse/PROTON-1630
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
> at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
> PROTON-1592 : [python] restore original tx_recv.py example
>Reporter: Jiri Daněk
>Assignee: Justin Ross
>
> Add the following include to your application, or say {{container_test.cpp}} 
> proton file.
> {code}
> #include "proton/default_container.hpp" does not compile
> {code}
> Attempt to compile and behold the error
> {noformat}
> In file included from 
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
> /home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
>  error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
> instead)
>  typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
> default_container;
>   ^
> make[3]: *** 
> [proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
> Error 1
> make[2]: *** [CMakeFiles/Makefile2:1609: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
> make[1]: *** [CMakeFiles/Makefile2:1621: 
> proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
> {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] [Created] (PROTON-1630) #include "proton/default_container.hpp" does not compile

[JIRA]

Jiri Daněk created PROTON-1630:
--

 Summary: #include "proton/default_container.hpp" does not compile
 Key: PROTON-1630
 URL: https://issues.apache.org/jira/browse/PROTON-1630
 Project: Qpid Proton
  Issue Type: Improvement
  Components: cpp-binding
Affects Versions: proton-c-0.18.0
 Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
at commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)   
PROTON-1592 : [python] restore original tx_recv.py example
Reporter: Jiri Daněk
Assignee: Cliff Jansen


Add the following include to your application, or say {{container_test.cpp}} 
proton file.

{code}
#include "proton/default_container.hpp" does not compile
{code}

Attempt to compile and behold the error

{noformat}
In file included from 
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:21:0:
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/default_container.hpp:31:42:
 error: typedef ‘proton::PN_CPP_DEPRECATED’ is initialized (use decltype 
instead)
 typedef class container PN_CPP_DEPRECATED("Use 'proton::container'") 
default_container;
  ^
make[3]: *** 
[proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
Error 1
make[2]: *** [CMakeFiles/Makefile2:1609: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:1621: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/rule] Error 2
{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] [Created] (PROTON-1629) [cpp] proton::container is not move constructible

[JIRA]

Jiri Daněk created PROTON-1629:
--

 Summary: [cpp] proton::container is not move constructible
 Key: PROTON-1629
 URL: https://issues.apache.org/jira/browse/PROTON-1629
 Project: Qpid Proton
  Issue Type: Improvement
  Components: cpp-binding
Affects Versions: proton-c-0.18.0
 Environment: Linux, gcc (GCC) 7.0.1 20170409 (experimental), git tip 
at 
commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 (upstream/master)
 PROTON-1592: [python] restore original tx_recv.py example
Reporter: Jiri Daněk
Assignee: Cliff Jansen
Priority: Minor


Following C++11 code does not compile

{code}
auto handler = proton::messaging_handler();
auto container = proton::container(handler); // container is not move 
constructible
{code}

Error from GCC is

{noformat}
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:
 In function ‘int {anonymous}::test_container_schedule_multithreaded()’:
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:591:47:
 error: use of deleted function ‘proton::container::container(const 
proton::container&)’
 auto container = proton::container(handler); // container is not move 
constructible
   ^
In file included from 
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:28:0:
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:55:27:
 note: ‘proton::container::container(const proton::container&)’ is implicitly 
deleted because the default definition would be ill-formed:
 class PN_CPP_CLASS_EXTERN container {
   ^
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:55:27:
 error: use of deleted function ‘constexpr 
proton::internal::pn_unique_ptr::pn_unique_ptr(const 
proton::internal::pn_unique_ptr&)’
In file included from 
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/connection_options.hpp:29:0,
 from 
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/src/container_test.cpp:27:
/home/jdanek/Work/repos/qpid-proton/proton-c/bindings/cpp/include/proton/./internal/pn_unique_ptr.hpp:43:26:
 note: ‘constexpr 
proton::internal::pn_unique_ptr::pn_unique_ptr(const 
proton::internal::pn_unique_ptr&)’ is implicitly 
declared as deleted because 
‘proton::internal::pn_unique_ptr’ declares a move 
constructor or move assignment operator
 template  class pn_unique_ptr {
  ^
make[3]: *** 
[proton-c/bindings/cpp/CMakeFiles/container_test.dir/build.make:63: 
proton-c/bindings/cpp/CMakeFiles/container_test.dir/src/container_test.cpp.o] 
Error 1
{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] [Created] (PROTON-1628) [cpp] Stopping container in on_container_start will hang

[JIRA]

Jiri Daněk created PROTON-1628:
--

 Summary: [cpp] Stopping container in on_container_start will hang
 Key: PROTON-1628
 URL: https://issues.apache.org/jira/browse/PROTON-1628
 Project: Qpid Proton
  Issue Type: Bug
  Components: cpp-binding
Affects Versions: proton-c-0.18.0
 Environment: Linux, epoll io, master tip at 
72b7ea0508e94aae3e5d9470293bc5c7e8250a45 PROTON-1592: [python] restore 
original tx_recv.py example

Reporter: Jiri Daněk
Assignee: Cliff Jansen


{code}
class immediate_stop_tester : public proton::messaging_handler {
public:
void on_container_start(proton::container ) PN_CPP_OVERRIDE {
c.stop();
}
};

int test_container_immediate_stop() {
immediate_stop_tester t;
proton::container(t).run();  // will hang
return 0;
}
{code}



--
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-1627) [cpp] on_*_open handlers require a super call

[JIRA]

 [ 
https://issues.apache.org/jira/browse/PROTON-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jiri Daněk updated PROTON-1627:
---
Description: 
User needs to implement the on_*_ handlers like this
{code}
void on_connection_open(proton::connection ) override {
proton::messaging_handler::on_connection_open(c);
[...]
{code}

The super implementation does

{code}
if (c.uninitialized()) {
pn_connection_open(unwrap(c));
}
{code}

There are issues with that.  The rule for handlers seems to be. 1) do not call 
super method in on_*_error, 2) call it everywhere else. This is complicated.

Next, hooks are generally expected not to require a super call. 
https://martinfowler.com/bliki/CallSuper.html

Finally, this is not documented on the {{on_connection_open}} method. I only 
went looking there when I figured what the problem was.


  was:
User needs to implement the on_*_ handlers like this
{code}
void on_connection_open(proton::connection ) override {
proton::messaging_handler::on_connection_open(c);
[...]
{code}

The super implementation does

{code}
if (c.uninitialized()) {
pn_connection_open(unwrap(c));
}
{code}

There are issues with that.  The rule for handlers seems to be. 1) do not call 
super method in on_*_error, 2) call it everywhere else. This is complicated.

Next, handlers are generally expected not to require a super call. 
https://martinfowler.com/bliki/CallSuper.html

Finally, this is not documented on the {{on_connection_open}} method. I only 
went looking there when I figured what the problem was.



> [cpp] on_*_open handlers require a super call
> -
>
> Key: PROTON-1627
> URL: https://issues.apache.org/jira/browse/PROTON-1627
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-j-0.18.0
>Reporter: Jiri Daněk
>Assignee: Cliff Jansen
>
> User needs to implement the on_*_ handlers like this
> {code}
> void on_connection_open(proton::connection ) override {
> proton::messaging_handler::on_connection_open(c);
> [...]
> {code}
> The super implementation does
> {code}
> if (c.uninitialized()) {
> pn_connection_open(unwrap(c));
> }
> {code}
> There are issues with that.  The rule for handlers seems to be. 1) do not 
> call super method in on_*_error, 2) call it everywhere else. This is 
> complicated.
> Next, hooks are generally expected not to require a super call. 
> https://martinfowler.com/bliki/CallSuper.html
> Finally, this is not documented on the {{on_connection_open}} method. I only 
> went looking there when I figured what the problem was.



--
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] (PROTON-1627) [cpp] on_*_open handlers require a super call

[JIRA]

Jiri Daněk created PROTON-1627:
--

 Summary: [cpp] on_*_open handlers require a super call
 Key: PROTON-1627
 URL: https://issues.apache.org/jira/browse/PROTON-1627
 Project: Qpid Proton
  Issue Type: Bug
  Components: cpp-binding
Affects Versions: proton-j-0.18.0
Reporter: Jiri Daněk
Assignee: Cliff Jansen


User needs to implement the on_*_ handlers like this
{code}
void on_connection_open(proton::connection ) override {
proton::messaging_handler::on_connection_open(c);
[...]
{code}

The super implementation does

{code}
if (c.uninitialized()) {
pn_connection_open(unwrap(c));
}
{code}

There are issues with that.  The rule for handlers seems to be. 1) do not call 
super method in on_*_error, 2) call it everywhere else. This is complicated.

Next, handlers are generally expected not to require a super call. 
https://martinfowler.com/bliki/CallSuper.html

Finally, this is not documented on the {{on_connection_open}} method. I only 
went looking there when I figured what the problem was.




--
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] (QPIDJMS-340) Build fails with group id is too big error

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203619#comment-16203619
 ] 

ASF subversion and git services commented on QPIDJMS-340:
-

Commit 5d17c95ae2ba0d9b6efbe07d3c7345ab59bbc40e in qpid-jms's branch 
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=5d17c95 ]

QPIDJMS-340 - fix maven-assembly-plugin compatibility

Set targLongFileMode to posix for handling long file names


> Build fails with group id is too big error
> --
>
> Key: QPIDJMS-340
> URL: https://issues.apache.org/jira/browse/QPIDJMS-340
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Christopher L. Shannon
>Priority: Minor
>
> In my environment when I'm trying to build from source the maven-assembly 
> plugin fails because my group id is apparently too big.  The solution for 
> this is to configure the maven-assembly-plugin with 
> {{posix}}



--
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] (QPIDJMS-340) Build fails with group id is too big error

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203621#comment-16203621
 ] 

ASF GitHub Bot commented on QPIDJMS-340:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-jms/pull/15


> Build fails with group id is too big error
> --
>
> Key: QPIDJMS-340
> URL: https://issues.apache.org/jira/browse/QPIDJMS-340
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Christopher L. Shannon
>Priority: Minor
>
> In my environment when I'm trying to build from source the maven-assembly 
> plugin fails because my group id is apparently too big.  The solution for 
> this is to configure the maven-assembly-plugin with 
> {{posix}}



--
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-jms pull request #15: QPIDJMS-340 - fix maven-assembly-plugin compatibi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-jms/pull/15


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1610) Intermittent self test fails

[Alan Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway resolved PROTON-1610.
-
Resolution: Fixed

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
> Fix For: proton-c-0.18.0
>
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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] (PROTON-1610) Intermittent self test fails

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203592#comment-16203592
 ] 

ASF subversion and git services commented on PROTON-1610:
-

Commit f76f28927e176b5b994d865a19e54f25d9708eb3 in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f76f289 ]

PROTON-1610: c++ intermittent self test fails

C++ scheduler was not checking for (next->time < now), negative timeout interval
converted to large unsigned value when passed to pn_proactor_set_time-out.


> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
> Fix For: proton-c-0.18.0
>
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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] (PROTON-1592) [proton-python] accessing properties of event.receiver in on_link_opened throws exception

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203593#comment-16203593
 ] 

ASF subversion and git services commented on PROTON-1592:
-

Commit 72b7ea0508e94aae3e5d9470293bc5c7e8250a45 in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=72b7ea0 ]

PROTON-1592: [python] restore original tx_recv.py example

Previous commit introduced reproducer code into the example by mistake.
The original example works as-is.


> [proton-python] accessing properties of event.receiver in on_link_opened 
> throws exception
> -
>
> Key: PROTON-1592
> URL: https://issues.apache.org/jira/browse/PROTON-1592
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: python-binding
>Reporter: Jiri Daněk
>Assignee: Alan Conway
>  Labels: regression
> Fix For: proton-c-0.18.0
>
>
> Apply the following patch to the {{tx-recv.py}} example
> {code}
> diff --git a/examples/python/tx_recv.py b/examples/python/tx_recv.py
> index 4baddcf5..54f3b489 100755
> --- a/examples/python/tx_recv.py
> +++ b/examples/python/tx_recv.py
> @@ -40,6 +40,9 @@ class TxRecv(MessagingHandler, TransactionHandler):
>  self.container.declare_transaction(self.conn, handler=self)
>  self.transaction = None
>  
> + def on_link_opened(self, event):
> + event.receiver.drain_mode = True
> +
>  def on_message(self, event):
>  print(event.message.body)
>  self.transaction.accept(event.delivery)
> {code}
> Now run first {{tx_send.py}}, then this {{tx_recv.py}}. The second command 
> throws exception
> {noformat}
> $ LD_LIBRARY_PATH=`pwd`/lib64 PYTHONPATH=`pwd`/lib64/proton/bindings/python 
> python ../examples/python/tx_recv.py
> Traceback (most recent call last):
>   File "../examples/python/tx_recv.py", line 79, in 
> Container(TxRecv(opts.address, opts.messages, opts.batch_size)).run()
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 148, in run
> while self.process(): pass
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 174, in process
> self._check_errors()
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 170, in _check_errors
> _compat.raise_(exc, value, tb)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 4068, in dispatch
> ev.dispatch(self.handler)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3977, in dispatch
> result = dispatch(handler, type.method, self)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3857, in dispatch
> return handler.on_unhandled(method, *args)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/reactor.py",
>  line 876, in on_unhandled
> event.dispatch(handler)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3980, in dispatch
> self.dispatch(h, type)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3977, in dispatch
> result = dispatch(handler, type.method, self)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3855, in dispatch
> return m(*args)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
>  line 298, in on_link_remote_open
> self.on_link_opened(event)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/handlers.py",
>  line 313, in on_link_opened
> dispatch(self.delegate, 'on_link_opened', event)
>   File 
> "/home/jdanek/Work/repos/qpid-proton/install/lib64/proton/bindings/python/proton/__init__.py",
>  line 3855, in dispatch
> return m(*args)
>   File "../examples/python/tx_recv.py", line 44, in on_link_opened
> event.receiver.drain_mode = True
> AttributeError: 'NoneType' object has no attribute 'drain_mode'
> {noformat}
> To see this is a regression, repeat now with python-qpid-proton 0.17.0 from 
> Pypi. With this previous release, there is success.



--
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] (QPIDJMS-340) Build fails with group id is too big error

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203587#comment-16203587
 ] 

ASF GitHub Bot commented on QPIDJMS-340:


GitHub user cshannon opened a pull request:

https://github.com/apache/qpid-jms/pull/15

QPIDJMS-340 - fix maven-assembly-plugin compatibility

Set targLongFileMode to posix for handling long file names

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cshannon/qpid-jms QPIDJMS-340

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-jms/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit 5d17c95ae2ba0d9b6efbe07d3c7345ab59bbc40e
Author: Christopher L. Shannon (cshannon) 
Date:   2017-10-13T13:49:13Z

QPIDJMS-340 - fix maven-assembly-plugin compatibility

Set targLongFileMode to posix for handling long file names




> Build fails with group id is too big error
> --
>
> Key: QPIDJMS-340
> URL: https://issues.apache.org/jira/browse/QPIDJMS-340
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Christopher L. Shannon
>Priority: Minor
>
> In my environment when I'm trying to build from source the maven-assembly 
> plugin fails because my group id is apparently too big.  The solution for 
> this is to configure the maven-assembly-plugin with 
> {{posix}}



--
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-jms pull request #15: QPIDJMS-340 - fix maven-assembly-plugin compatibi...

[cshannon]

GitHub user cshannon opened a pull request:

https://github.com/apache/qpid-jms/pull/15

QPIDJMS-340 - fix maven-assembly-plugin compatibility

Set targLongFileMode to posix for handling long file names

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cshannon/qpid-jms QPIDJMS-340

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-jms/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #15


commit 5d17c95ae2ba0d9b6efbe07d3c7345ab59bbc40e
Author: Christopher L. Shannon (cshannon) 
Date:   2017-10-13T13:49:13Z

QPIDJMS-340 - fix maven-assembly-plugin compatibility

Set targLongFileMode to posix for handling long file names




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDJMS-340) Build fails with group id is too big error

[Christopher L. Shannon (JIRA)]

Christopher L. Shannon created QPIDJMS-340:
--

 Summary: Build fails with group id is too big error
 Key: QPIDJMS-340
 URL: https://issues.apache.org/jira/browse/QPIDJMS-340
 Project: Qpid JMS
  Issue Type: Bug
  Components: qpid-jms-client
Affects Versions: 0.26.0
Reporter: Christopher L. Shannon
Priority: Minor


In my environment when I'm trying to build from source the maven-assembly 
plugin fails because my group id is apparently too big.  The solution for this 
is to configure the maven-assembly-plugin with 
{{posix}}



--
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] (QPIDJMS-339) Allow setting keystore and truststore type from system properties

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203581#comment-16203581
 ] 

ASF GitHub Bot commented on QPIDJMS-339:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-jms/pull/14


> Allow setting keystore and truststore type from system properties
> -
>
> Key: QPIDJMS-339
> URL: https://issues.apache.org/jira/browse/QPIDJMS-339
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Trivial
> Fix For: 0.27.0
>
>
> Read store type for key store and trust store from the java properties 
> *javax.net.ssl.keyStoreType* and *javax.net.ssl.trustStoreType* defaulting to 
> *JKS*



--
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] (QPIDJMS-339) Allow setting keystore and truststore type from system properties

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203580#comment-16203580
 ] 

ASF subversion and git services commented on QPIDJMS-339:
-

Commit 815ebe78d7df1fa47e2755db665e57889ea70b57 in qpid-jms's branch 
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=815ebe7 ]

QPIDJMS-339 - update documentation for new transport settings

Update documentation for keystore and truststore settings


> Allow setting keystore and truststore type from system properties
> -
>
> Key: QPIDJMS-339
> URL: https://issues.apache.org/jira/browse/QPIDJMS-339
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Trivial
> Fix For: 0.27.0
>
>
> Read store type for key store and trust store from the java properties 
> *javax.net.ssl.keyStoreType* and *javax.net.ssl.trustStoreType* defaulting to 
> *JKS*



--
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-jms pull request #14: QPIDJMS-339 - update documentation for new transp...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-jms/pull/14


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1618) Give unambiguous indication when server listen operation succeeds or fails

[Justin Ross (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203524#comment-16203524
 ] 

Justin Ross commented on PROTON-1618:
-

I targeted 1610 for 0.18.0.  Taking this back to resolved.

> Give unambiguous indication when server listen operation succeeds or fails
> --
>
> Key: PROTON-1618
> URL: https://issues.apache.org/jira/browse/PROTON-1618
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Alan Conway
>  Labels: api
> Fix For: proton-c-0.18.0
>
>
> The C proactor API provides events to indicate when an async listen operation 
> has succeeded or failed, but the semantics are a little unclear. The C++ API 
> lacks the required events.
> Simplify & clarify the C API, and add the missing events in C++.



--
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] [Resolved] (PROTON-1618) Give unambiguous indication when server listen operation succeeds or fails

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross resolved PROTON-1618.
-
Resolution: Fixed

> Give unambiguous indication when server listen operation succeeds or fails
> --
>
> Key: PROTON-1618
> URL: https://issues.apache.org/jira/browse/PROTON-1618
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Alan Conway
>  Labels: api
> Fix For: proton-c-0.18.0
>
>
> The C proactor API provides events to indicate when an async listen operation 
> has succeeded or failed, but the semantics are a little unclear. The C++ API 
> lacks the required events.
> Simplify & clarify the C API, and add the missing events in C++.



--
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-7970) [Java Broker] [AMQP 1.0] Session leaks closed link endpoints

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-7970:
-
Status: Reviewable  (was: In Progress)

> [Java Broker] [AMQP 1.0] Session leaks closed link endpoints
> 
>
> Key: QPID-7970
> URL: https://issues.apache.org/jira/browse/QPID-7970
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> Closed link endpoints are accumulated in 
> {{org.apache.qpid.server.protocol.v1_0.Session_1_0#_associatedLinkEndpoints}} 
> and might cause a memory leak on long lived sessions. Both sending and 
> receiving link endpoints are not removed from 
> {{org.apache.qpid.server.protocol.v1_0.Session_1_0#_associatedLinkEndpoints}} 
> on close



--
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] [Assigned] (QPID-7970) [Java Broker] [AMQP 1.0] Session leaks closed link endpoints

[Alex Rudyy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/QPID-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-7970:


Assignee: Alex Rudyy

> [Java Broker] [AMQP 1.0] Session leaks closed link endpoints
> 
>
> Key: QPID-7970
> URL: https://issues.apache.org/jira/browse/QPID-7970
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>
> Closed link endpoints are accumulated in 
> {{org.apache.qpid.server.protocol.v1_0.Session_1_0#_associatedLinkEndpoints}} 
> and might cause a memory leak on long lived sessions. Both sending and 
> receiving link endpoints are not removed from 
> {{org.apache.qpid.server.protocol.v1_0.Session_1_0#_associatedLinkEndpoints}} 
> on close



--
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-7970) [Java Broker] [AMQP 1.0] Session leaks closed link endpoints

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203508#comment-16203508
 ] 

ASF subversion and git services commented on QPID-7970:
---

Commit 8770d41ddb2ef1e92b00bf184b86ca5d075146f4 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=8770d41 ]

QPID-7970: [Java Broker] [AMQP 1.0] Remove closed link endpoint from session 
associated link endpoints on receiving link detach


> [Java Broker] [AMQP 1.0] Session leaks closed link endpoints
> 
>
> Key: QPID-7970
> URL: https://issues.apache.org/jira/browse/QPID-7970
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>
> Closed link endpoints are accumulated in 
> {{org.apache.qpid.server.protocol.v1_0.Session_1_0#_associatedLinkEndpoints}} 
> and might cause a memory leak on long lived sessions. Both sending and 
> receiving link endpoints are not removed from 
> {{org.apache.qpid.server.protocol.v1_0.Session_1_0#_associatedLinkEndpoints}} 
> on close



--
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] (QPIDJMS-339) Allow setting keystore and truststore type from system properties

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDJMS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203497#comment-16203497
 ] 

ASF GitHub Bot commented on QPIDJMS-339:


GitHub user cshannon opened a pull request:

https://github.com/apache/qpid-jms/pull/14

QPIDJMS-339 - update documentation for new transport settings

Update documentation for keystore and truststore settings

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cshannon/qpid-jms QPIDJMS-339-doc-update

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-jms/pull/14.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14


commit 815ebe78d7df1fa47e2755db665e57889ea70b57
Author: Christopher L. Shannon (cshannon) 
Date:   2017-10-13T12:33:41Z

QPIDJMS-339 - update documentation for new transport settings

Update documentation for keystore and truststore settings




> Allow setting keystore and truststore type from system properties
> -
>
> Key: QPIDJMS-339
> URL: https://issues.apache.org/jira/browse/QPIDJMS-339
> Project: Qpid JMS
>  Issue Type: Improvement
>  Components: qpid-jms-client
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Trivial
> Fix For: 0.27.0
>
>
> Read store type for key store and trust store from the java properties 
> *javax.net.ssl.keyStoreType* and *javax.net.ssl.trustStoreType* defaulting to 
> *JKS*



--
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-jms pull request #14: QPIDJMS-339 - update documentation for new transp...

[cshannon]

GitHub user cshannon opened a pull request:

https://github.com/apache/qpid-jms/pull/14

QPIDJMS-339 - update documentation for new transport settings

Update documentation for keystore and truststore settings

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cshannon/qpid-jms QPIDJMS-339-doc-update

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-jms/pull/14.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #14


commit 815ebe78d7df1fa47e2755db665e57889ea70b57
Author: Christopher L. Shannon (cshannon) 
Date:   2017-10-13T12:33:41Z

QPIDJMS-339 - update documentation for new transport settings

Update documentation for keystore and truststore settings




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1610) Intermittent self test fails

[Justin Ross (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated PROTON-1610:

Fix Version/s: proton-c-0.18.0

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
> Fix For: proton-c-0.18.0
>
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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-7955) Logback Stack overflow exception whilst reporting fatal BDB JE error

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203469#comment-16203469
 ] 

ASF subversion and git services commented on QPID-7955:
---

Commit a7121a65ff37204075a05e8f529cd47a9224e6c2 in qpid-broker-j's branch 
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=a7121a6 ]

QPID-7955: [Logback] Allow the logback module to find the exclusion files


> Logback Stack overflow exception whilst reporting fatal BDB JE error
> 
>
> Key: QPID-7955
> URL: https://issues.apache.org/jira/browse/QPID-7955
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> Running a test case that deliberately causes the Broker configured to use BDB 
> to run out of diskspace, the Broker shuts down with the following exception.  
> The exception exception was IOException reporting the absence of diskspace.   
> Problem occurs equally on all three AMQP protocols.
> {code}
> java.lang.StackOverflowError: null
> at 
> com.sleepycat.je.DatabaseException.getMessage(DatabaseException.java:156)
> at 
> com.sleepycat.je.EnvironmentFailureException.getMessage(EnvironmentFailureException.java:255)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:54)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:60)
> at 
> ch.qos.logback.classic.spi.ThrowableProxy.(ThrowableProxy.java:72)
> {code}



--
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] [Comment Edited] (PROTON-1610) Intermittent self test fails

[Alan Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203424#comment-16203424
 ] 

Alan Conway edited comment on PROTON-1610 at 10/13/17 12:01 PM:


There is a race condition in the scheduler implementation.

I was able to reproduce the hang under rr after running in a loop for about 5 
mins: the process hangs forever in pn_proactor_wait() after it has previously 
scheduled a callback in tick(), the proactor never wakes up to service the 
scheduled task. Not sure if the problem is in C++ or C at this point.


was (Author: aconway):
There is a race condition in the schedule_03 example. I have been able to 
reproduce the hanging after a couple minutes of running the example under 
valgrind with PN_TRACE_FRM=1 PN_TRACE_EVT=1 in a clang, -DBUILD_CPP=03,  
RelWIthDebugInfo build. I haven't got any useful info out of this yet - there's 
nothing unusual in the trace output at the point of the hang and the hung 
valgrind process are not yielding any useful info to gdb or pstack.

NOTE: this hang has been seen with gcc as well as clang. AFAIK it is always the 
schedule_03 test that hangs, and travis is always running valgrind.

Also note: building with -fsanitize=thread does not produce any 
errors/warnings, but I can't reporduce withtout valgrind and we can't run 
valigrind on stantized builds

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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] [Comment Edited] (PROTON-1610) Intermittent self test fails

[Alan Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203424#comment-16203424
 ] 

Alan Conway edited comment on PROTON-1610 at 10/13/17 11:48 AM:


There is a race condition in the schedule_03 example. I have been able to 
reproduce the hanging after a couple minutes of running the example under 
valgrind with PN_TRACE_FRM=1 PN_TRACE_EVT=1 in a clang, -DBUILD_CPP=03,  
RelWIthDebugInfo build. I haven't got any useful info out of this yet - there's 
nothing unusual in the trace output at the point of the hang and the hung 
valgrind process are not yielding any useful info to gdb or pstack.

NOTE: this hang has been seen with gcc as well as clang. AFAIK it is always the 
schedule_03 test that hangs, and travis is always running valgrind.

Also note: building with -fsanitize=thread does not produce any 
errors/warnings, but I can't reporduce withtout valgrind and we can't run 
valigrind on stantized builds


was (Author: aconway):
There is a race condition in the schedule_03 example. I have been able to 
reproduce the hanging after a couple minutes of running the example under 
valgrind with PN_TRACE_FRM=1 PN_TRACE_EVT=1 in a clang, -DBUILD_CPP=03,  
RelWIthDebugInfo build. I haven't got any useful info out of this yet - there's 
nothing unusual in the trace output at the point of the hang and the hung 
valgrind process are not yielding any useful info to gdb or pstack.

NOTE: this hang has been seen with gcc as well as clang. AFAIK it is always the 
schedule_03 test that hangs, and travis is always running valgrind.

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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] [Comment Edited] (PROTON-1610) Intermittent self test fails

[Alan Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203424#comment-16203424
 ] 

Alan Conway edited comment on PROTON-1610 at 10/13/17 11:46 AM:


There is a race condition in the schedule_03 example. I have been able to 
reproduce the hanging after a couple minutes of running the example under 
valgrind with PN_TRACE_FRM=1 PN_TRACE_EVT=1 in a clang, -DBUILD_CPP=03,  
RelWIthDebugInfo build. I haven't got any useful info out of this yet - there's 
nothing unusual in the trace output at the point of the hang and the hung 
valgrind process are not yielding any useful info to gdb or pstack.

NOTE: this hang has been seen with gcc as well as clang. AFAIK it is always the 
schedule_03 test that hangs, and travis is always running valgrind.


was (Author: aconway):
There is a race condition in the schedule_03 example. I have been able to 
reproduce the hanging after a couple minutes of running the example under 
valgrind with PN_TRACE_FRM=1 PN_TRACE_EVT=1 in a clang, -DBUILD_CPP=03,  
RelWIthDebugInfo build. I haven't got any useful info out of this yet - there's 
nothing unusual in the trace output at the point of the hang and the hung 
valgrind process are not yielding any useful info to gdb or pstack.

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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] (PROTON-1610) Intermittent self test fails

[Alan Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203424#comment-16203424
 ] 

Alan Conway commented on PROTON-1610:
-

There is a race condition in the schedule_03 example. I have been able to 
reproduce the hanging after a couple minutes of running the example under 
valgrind with PN_TRACE_FRM=1 PN_TRACE_EVT=1 in a clang, -DBUILD_CPP=03,  
RelWIthDebugInfo build. I haven't got any useful info out of this yet - there's 
nothing unusual in the trace output at the point of the hang and the hung 
valgrind process are not yielding any useful info to gdb or pstack.

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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-7969) [Stress Test Tools] Add ability into StressTestClient to pause indefinitely after opening of test connection and before connection close

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203401#comment-16203401
 ] 

ASF subversion and git services commented on QPID-7969:
---

Commit 2c0b84746b56168ab1f7e3588283e3f6928ab22d 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=2c0b847 ]

QPID-7969: [Stress Test Tools] Add ability into StressTestClient to pause 
indefinitely before and after messaging operations


> [Stress Test Tools] Add ability into StressTestClient to pause indefinitely 
> after opening of test connection and before connection close
> 
>
> Key: QPID-7969
> URL: https://issues.apache.org/jira/browse/QPID-7969
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Tests, Java Tools
>Reporter: Alex Rudyy
>
> In order to detect memory leaks within connection lifecycle the 
> {{StressTestClient}} need to be improved to allow heapdump collection after 
> test connection establishing and before closing of the connection.



--
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-1626) Incompatibilty of fdlimit test on RHEL 6 x64

[Radim Kubis (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radim Kubis updated PROTON-1626:

Priority: Minor  (was: Major)

> Incompatibilty of fdlimit test on RHEL 6 x64
> 
>
> Key: PROTON-1626
> URL: https://issues.apache.org/jira/browse/PROTON-1626
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.18.0
> Environment: RHEL 6 x64
>Reporter: Radim Kubis
>Priority: Minor
>
> Test 
> [fdlimit|https://github.com/apache/qpid-proton/blob/master/proton-c/src/tests/fdlimit.py]
>  uses RHEL 6 x64 incompatible things:
> * _skipTest_ (added in Python 2.7, but RHEL 6 has Python 2.6.6)
> * _prlimit_ utility (unavailable on RHEL 6)



--
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] (PROTON-1626) Incompatibilty of fdlimit test on RHEL 6 x64

[Radim Kubis (JIRA)]

Radim Kubis created PROTON-1626:
---

 Summary: Incompatibilty of fdlimit test on RHEL 6 x64
 Key: PROTON-1626
 URL: https://issues.apache.org/jira/browse/PROTON-1626
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: proton-c-0.18.0
 Environment: RHEL 6 x64
Reporter: Radim Kubis


Test 
[fdlimit|https://github.com/apache/qpid-proton/blob/master/proton-c/src/tests/fdlimit.py]
 uses RHEL 6 x64 incompatible things:
* _skipTest_ (added in Python 2.7, but RHEL 6 has Python 2.6.6)
* _prlimit_ utility (unavailable on RHEL 6)



--
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-1610) Intermittent self test fails

[Alan Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203346#comment-16203346
 ] 

Alan Conway commented on PROTON-1610:
-

And another: https://travis-ci.org/apache/qpid-proton/builds/286822832

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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] [Assigned] (PROTON-1610) Intermittent self test fails

[Alan Conway (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PROTON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway reassigned PROTON-1610:
---

Assignee: Alan Conway  (was: Cliff Jansen)

> Intermittent self test fails
> 
>
> Key: PROTON-1610
> URL: https://issues.apache.org/jira/browse/PROTON-1610
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: proton-c-0.18.0
> Environment: Fedora 25
>Reporter: Chuck Rolke
>Assignee: Alan Conway
>
> Test cpp-example-container just started failing "a lot" since yesterday.
> Running 'make test' fails 3 times in a row.
> Running 'ctest -V -R cpp-example-container' it fails maybe 10% of the time.
> When it fails it shows:
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 202, in test_scheduled_send
> 24: out = self.proc(["scheduled_send", "-a", self.addr+"scheduled_send", 
> "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send -a localhost:41071/examplescheduled_send -t 
> 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> 24: --
> 24: Ran 15 tests in 39.234s
> 24: 
> 24: FAILED (errors=1)
> 1/2 Test #24: cpp-example-container ***Failed   39.29 sec
> {noformat}
> and
> {noformat}
> 24: ==
> 24: ERROR: test_scheduled_send_03 (__main__.ContainerExampleTest)
> 24: --
> 24: Traceback (most recent call last):
> 24:   File "/home/chug/git/qpid-proton/examples/cpp/example_test.py", line 
> 196, in test_scheduled_send_03
> 24: out = self.proc(["scheduled_send_03", "-a", 
> self.addr+"scheduled_send", "-t", "0.1", "-i", "0.001"]).wait_exit().split()
> 24:   File "/home/chug/git/qpid-proton/tools/py/proctest.py", line 125, in 
> wait_exit
> 24: raise ProcError(self, "still running after %ss" % timeout)
> 24: ProcError: still running after 10s (exit=None) command:
> 24: /usr/bin/valgrind --quiet --error-exitcode=42 --tool=memcheck 
> --leak-check=full scheduled_send_03 -a localhost:33951/examplescheduled_send 
> -t 0.1 -i 0.001
> 24: 
> 24: send
> 24: send
> 24: 
> 24: 
> {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] (PROTON-1618) Give unambiguous indication when server listen operation succeeds or fails

[Alan Conway (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203336#comment-16203336
 ] 

Alan Conway commented on PROTON-1618:
-

[~jdanek] this is a long-standing sporadic failure - PROTON-1610 . We need to 
get it fixed as it's making the travis results hard to interpret.

> Give unambiguous indication when server listen operation succeeds or fails
> --
>
> Key: PROTON-1618
> URL: https://issues.apache.org/jira/browse/PROTON-1618
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Alan Conway
>  Labels: api
> Fix For: proton-c-0.18.0
>
>
> The C proactor API provides events to indicate when an async listen operation 
> has succeeded or failed, but the semantics are a little unclear. The C++ API 
> lacks the required events.
> Simplify & clarify the C API, and add the missing events in C++.



--
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