[jira] [Resolved] (QPID-7286) [Java Broker] List of supported versions brought back by invoking Main class with -v is incorrect

[Rob Godfrey (JIRA)]

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

Rob Godfrey resolved QPID-7286.
---
Resolution: Fixed

> [Java Broker] List of supported versions brought back by invoking Main class 
> with -v is incorrect
> -
>
> Key: QPID-7286
> URL: https://issues.apache.org/jira/browse/QPID-7286
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1, 
> qpid-java-6.0.2, qpid-java-6.0.3
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>Priority: Trivial
>
> We are building the version String from a class that is primarily use by the 
> client.
> We should instead use the set of plugins which are installed to determine the 
> protocol support.  Ultimately maybe -v should probably show all installed 
> plugins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7281) Get the tests running on Windows

[ASF subversion and git services (JIRA)]

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

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

Commit 1746375 from [~justi9] in branch 'qpid/trunk'
[ https://svn.apache.org/r1746375 ]

QPID-7281: Various fixes for the tests on windows

 - Adjust environment script for windows paths
 - Pythonify the test runner for the windows store tests
 - Run the HA tests only on posix systems
 - Remove a finicky assertion in brokertest.py

> Get the tests running on Windows
> 
>
> Key: QPID-7281
> URL: https://issues.apache.org/jira/browse/QPID-7281
> Project: Qpid
>  Issue Type: Improvement
>  Components: C++ Broker, C++ Client
>Affects Versions: qpid-cpp-0.34
>Reporter: Justin Ross
>Assignee: Justin Ross
>  Labels: windows
> Fix For: qpid-cpp-next
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (PROTON-1216) c++: proton::coerce() should allow conversion from binary.

[ASF subversion and git services (JIRA)]

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

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

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

PROTON-1216: c++: cleanup to previous commit.

Removed file left behind in error, removed non standard cxxabi.h.


> c++: proton::coerce() should allow conversion from binary.
> ---
>
> Key: PROTON-1216
> URL: https://issues.apache.org/jira/browse/PROTON-1216
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.13.0
>
>
> proton::coerce should convert a binary value to a std::string. 
> The documentation also needs clarification: coerce should allow exactly those 
> conversions that are allowed as implicit C++ conversions.
> Issue raised in excellent bug report on the user list 
> http://qpid.2158936.n2.nabble.com/Proton-C-0-13-x-decode-binary-type-tp7644510p7644747.html
>  text follows:
> proton::coerce (both forms) currently throws the same
> exception as proton::get, as does value.as_string(), although that doesn't
> appear to be in the public API. Not sure what 'd' was in the d>>b  example,
> but got a version working using value.get() and an implicit
> cast to std::string.
> To reproduce...
> #include 
> #include 
> #include 
> #include 
> template
> void expect_exception ( Lambda f )
> {
>   try
>   {
> f();
> std::cout << "*** FAIL (expected conversion error) ***" << std::endl;
>   }
>   catch ( const proton::conversion_error& e )
>   {
> std::cout << "PASS" << std::endl;
>   }
> }
> template
> void expect_value ( const std::string& expected, Lambda f )
> {
>   try
>   {
> std::cout << (f() == expected ? "PASS" : "*** FAIL (wrong value) ***")
> << std::endl;
>   }
>   catch ( const proton::conversion_error& e )
>   {
> std::cout << "*** FAIL (conversion error) ***" << std::endl;
>   }
> }
> int main()
> {
>   std::string expected = "Hello World!";
>   proton::value value = proton::binary(expected);
>   expect_exception(  [=] { return value.get();   
>  
> });
>   expect_exception(  [=] { return proton::get(value);
>  
> });
>   expect_exception(  [=] { std::string result;
> proton::get(value); return result; });
>   expect_value(expected, [=] () -> std::string { return
> value.get(); } );
>   // The following currently fail under 0.13.x
>   expect_value(expected, [=] { return value.as_string();  
>  
> });
>   expect_value(expected, [=] { return proton::coerce(value); 
>  
> });
>   expect_value(expected, [=] { std::string result;
> proton::coerce(value, result); return result; });
>   
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (DISPATCH-343) Router stops accepting connections after load from parallel senders

[Vishal Sharda (JIRA)]

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

Vishal Sharda commented on DISPATCH-343:


The tracker used by sender is different than the one used by receiver.  Hence, 
receiver does get() followed by accept() and sender does settle().  We see that 
even if we do not call settle() at either end, the crash still occurs with 6 
senders and 1 receiver.


> Router stops accepting connections after load from parallel senders
> ---
>
> Key: DISPATCH-343
> URL: https://issues.apache.org/jira/browse/DISPATCH-343
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.6.0
>Reporter: Vishal Sharda
>Assignee: Ted Ross
>Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: Connection_aborted.png, Connection_aborted_1.png, 
> Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf, 
> Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png, 
> bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf, 
> drivers.tar.gz, resource-limit-exceeded.png
>
>
> We ran 2 parallel senders and 2 receivers with each sender sending 5 
> messages.  After a while we saw that router stopped accepting connections 
> even from qdstat.  We saw various errors in the logs (screenshots attached).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (PROTON-1217) Sporadic memory leak in C++ container_test

[Justin Ross (JIRA)]

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

Justin Ross commented on PROTON-1217:
-

Reviewed by Ken.  Approved for 0.13.0.

> Sporadic memory leak in C++ container_test
> --
>
> Key: PROTON-1217
> URL: https://issues.apache.org/jira/browse/PROTON-1217
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Blocker
> Fix For: 0.13.0
>
>
> There is a sporadic leak (I see it about every 3-4 test runs) in the C++ 
> unite tests, valgrind details below:
> {code}
>  8/10 Test #13: cpp_container_test ...***Failed2.45 sec
> ==30795== 1,200 (48 direct, 1,152 indirect) bytes in 3 blocks are definitely 
> lost in loss record 2 of 3
> ==30795==at 0x4C29216: operator new(unsigned long) 
> (vg_replace_malloc.c:334)
> ==30795==by 0x4E6EF32: 
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&, 
> proton::connection_options const&) (container.cpp:83)
> ==30795==by 0x4E6EFC3: 
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&) (container.cpp:87)
> ==30795==by 0x404313: (anonymous 
> namespace)::test_handler::on_container_start(proton::container&) 
> (container_test.cpp:67)
> ==30795==by 0x4E804AF: 
> proton::messaging_adapter::on_reactor_init(proton::proton_event&) 
> (messaging_adapter.cpp:63)
> ==30795==by 0x4E82D62: 
> proton::proton_event::dispatch(proton::proton_handler&) (proton_event.cpp:36)
> ==30795==by 0x4E71483: proton::handler_context::dispatch(pn_handler_t*, 
> pn_event_t*, pn_event_type_t) (container_impl.cpp:71)
> ==30795==by 0x50ED57D: pn_handler_dispatch (handler.c:102)
> ==30795==by 0x50ECE8C: pn_reactor_process (reactor.c:402)
> ==30795==by 0x50ED2A8: pn_reactor_run (reactor.c:480)
> ==30795==by 0x4E83F2D: proton::reactor::run() (reactor.cpp:38)
> ==30795==by 0x4E7091F: proton::container_impl::run() 
> (container_impl.cpp:258)
> ==30795== 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (PROTON-1217) Sporadic memory leak in C++ container_test

[Ken Giusti (JIRA)]

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

Ken Giusti commented on PROTON-1217:


Verified - no more leaks.
Approved for 0.13.0 release.

> Sporadic memory leak in C++ container_test
> --
>
> Key: PROTON-1217
> URL: https://issues.apache.org/jira/browse/PROTON-1217
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Blocker
> Fix For: 0.13.0
>
>
> There is a sporadic leak (I see it about every 3-4 test runs) in the C++ 
> unite tests, valgrind details below:
> {code}
>  8/10 Test #13: cpp_container_test ...***Failed2.45 sec
> ==30795== 1,200 (48 direct, 1,152 indirect) bytes in 3 blocks are definitely 
> lost in loss record 2 of 3
> ==30795==at 0x4C29216: operator new(unsigned long) 
> (vg_replace_malloc.c:334)
> ==30795==by 0x4E6EF32: 
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&, 
> proton::connection_options const&) (container.cpp:83)
> ==30795==by 0x4E6EFC3: 
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&) (container.cpp:87)
> ==30795==by 0x404313: (anonymous 
> namespace)::test_handler::on_container_start(proton::container&) 
> (container_test.cpp:67)
> ==30795==by 0x4E804AF: 
> proton::messaging_adapter::on_reactor_init(proton::proton_event&) 
> (messaging_adapter.cpp:63)
> ==30795==by 0x4E82D62: 
> proton::proton_event::dispatch(proton::proton_handler&) (proton_event.cpp:36)
> ==30795==by 0x4E71483: proton::handler_context::dispatch(pn_handler_t*, 
> pn_event_t*, pn_event_type_t) (container_impl.cpp:71)
> ==30795==by 0x50ED57D: pn_handler_dispatch (handler.c:102)
> ==30795==by 0x50ECE8C: pn_reactor_process (reactor.c:402)
> ==30795==by 0x50ED2A8: pn_reactor_run (reactor.c:480)
> ==30795==by 0x4E83F2D: proton::reactor::run() (reactor.cpp:38)
> ==30795==by 0x4E7091F: proton::container_impl::run() 
> (container_impl.cpp:258)
> ==30795== 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (PROTON-1217) Sporadic memory leak in C++ container_test

[ASF subversion and git services (JIRA)]

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

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

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

PROTON-1217: Sporadic memory leak in C++ container_test

Fixed missing call to listen_handler::on_closed in the event of an exception.


> Sporadic memory leak in C++ container_test
> --
>
> Key: PROTON-1217
> URL: https://issues.apache.org/jira/browse/PROTON-1217
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Blocker
> Fix For: 0.13.0
>
>
> There is a sporadic leak (I see it about every 3-4 test runs) in the C++ 
> unite tests, valgrind details below:
> {code}
>  8/10 Test #13: cpp_container_test ...***Failed2.45 sec
> ==30795== 1,200 (48 direct, 1,152 indirect) bytes in 3 blocks are definitely 
> lost in loss record 2 of 3
> ==30795==at 0x4C29216: operator new(unsigned long) 
> (vg_replace_malloc.c:334)
> ==30795==by 0x4E6EF32: 
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&, 
> proton::connection_options const&) (container.cpp:83)
> ==30795==by 0x4E6EFC3: 
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&) (container.cpp:87)
> ==30795==by 0x404313: (anonymous 
> namespace)::test_handler::on_container_start(proton::container&) 
> (container_test.cpp:67)
> ==30795==by 0x4E804AF: 
> proton::messaging_adapter::on_reactor_init(proton::proton_event&) 
> (messaging_adapter.cpp:63)
> ==30795==by 0x4E82D62: 
> proton::proton_event::dispatch(proton::proton_handler&) (proton_event.cpp:36)
> ==30795==by 0x4E71483: proton::handler_context::dispatch(pn_handler_t*, 
> pn_event_t*, pn_event_type_t) (container_impl.cpp:71)
> ==30795==by 0x50ED57D: pn_handler_dispatch (handler.c:102)
> ==30795==by 0x50ECE8C: pn_reactor_process (reactor.c:402)
> ==30795==by 0x50ED2A8: pn_reactor_run (reactor.c:480)
> ==30795==by 0x4E83F2D: proton::reactor::run() (reactor.cpp:38)
> ==30795==by 0x4E7091F: proton::container_impl::run() 
> (container_impl.cpp:258)
> ==30795== 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Assigned] (DISPATCH-357) Address field is empty for link routed links in the qdstat "links" output

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-357:
--

Assignee: Ganesh Murthy

> Address field is empty for link routed links in the qdstat "links" output
> -
>
> Key: DISPATCH-357
> URL: https://issues.apache.org/jira/browse/DISPATCH-357
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Paolo Patierno
>Assignee: Ganesh Murthy
> Attachments: qdstat_links.txt
>
>
> I have a router with a link routed link for address "my_queue" configured (in 
> both directions in and out).
> Executing "qdstat -l", it doesn't show me the address name; the "addr" field 
> is empty.
> Attached you can find the file with output.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPIDIT-21) Add shims for C++ client

[Kim van der Riet (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPIDIT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308255#comment-15308255
 ] 

Kim van der Riet commented on QPIDIT-21:


Commit 69cb5a21371ef92b42406bcbaa5b49f7802c0b21 in qpid-interop-test's branch 
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=69cb5a2 ]

QPIDIT-22: Updates to match recent changes to the Proton C++ API. Minor fix to 
QUICKSTART file


> Add shims for C++ client
> 
>
> Key: QPIDIT-21
> URL: https://issues.apache.org/jira/browse/QPIDIT-21
> Project: Apache QPID IT
>  Issue Type: New Feature
>  Components: JmsMessageTest, ProtonCppShim, SimpleTypeTest
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> Add a set of shims for the Proton C++ client:
> * Sender for SimpeTypeTest
> * Receiver for SimpleTypeTest
> * Sender for JmsMessageTest
> * Receiver for JmsMessageTest



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Issue Comment Deleted] (QPIDIT-22) Add ability to run on Jenkins CI

[Kim van der Riet (JIRA)]

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

Kim van der Riet updated QPIDIT-22:
---
Comment: was deleted

(was: Commit 69cb5a21371ef92b42406bcbaa5b49f7802c0b21 in qpid-interop-test's 
branch refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=69cb5a2 ]

QPIDIT-22: Updates to match recent changes to the Proton C++ API. Minor fix to 
QUICKSTART file
)

> Add ability to run on Jenkins CI
> 
>
> Key: QPIDIT-22
> URL: https://issues.apache.org/jira/browse/QPIDIT-22
> Project: Apache QPID IT
>  Issue Type: Improvement
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> Run the tests on Jenkins continuous integration system.  For this to be 
> realized, the location of dependent components needs to be parameterized, as 
> they can no longer be in the usual installed locations.  This includes:
> * qpid-proton
> * qpid-jms



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (DISPATCH-155) Allow multiple connectors to the same broker

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy commented on DISPATCH-155:


You are allowed to have multiple connectors from a router to a broker if these 
connectors have different 'name's

The connectors have the host:port:name as the unique identifier. 

> Allow multiple connectors to the same broker
> 
>
> Key: DISPATCH-155
> URL: https://issues.apache.org/jira/browse/DISPATCH-155
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.4
>Reporter: Jakub Scholz
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: DISPATCH-155.patch
>
>
> In some use cases it might make sense to have multiple connectors configured, 
> which connect to the same broker. This makes sense for example when each 
> connection is using different credentials, where each set of credentials has 
> different access rights on the broker.
> Unfortunately, after DISPATCH-95, the identity of connectors is always 
> generated only using the address and port. As a result, you cannot have two 
> connectors to the same broker.
> It would be great if the identity of connectors could be based not only on 
> address and port but also include something more unique. Either a counter as 
> it was before or for example the connector name, which has to be unique 
> anyway.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (DISPATCH-155) Allow multiple connectors to the same broker

[ASF subversion and git services (JIRA)]

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

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

Commit 07acd8e1ba0eab421f1be7528891d49c73af2975 in qpid-dispatch's branch 
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=07acd8e ]

DISPATCH-155 - Additional fix. Don't show None in the listener or connector name


> Allow multiple connectors to the same broker
> 
>
> Key: DISPATCH-155
> URL: https://issues.apache.org/jira/browse/DISPATCH-155
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.4
>Reporter: Jakub Scholz
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
> Attachments: DISPATCH-155.patch
>
>
> In some use cases it might make sense to have multiple connectors configured, 
> which connect to the same broker. This makes sense for example when each 
> connection is using different credentials, where each set of credentials has 
> different access rights on the broker.
> Unfortunately, after DISPATCH-95, the identity of connectors is always 
> generated only using the address and port. As a result, you cannot have two 
> connectors to the same broker.
> It would be great if the identity of connectors could be based not only on 
> address and port but also include something more unique. Either a counter as 
> it was before or for example the connector name, which has to be unique 
> anyway.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (DISPATCH-357) Address field is empty for link routed links in the qdstat "links" output

[Paolo Patierno (JIRA)]

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

Paolo Patierno updated DISPATCH-357:

Description: 
I have a router with a link routed link for address "my_queue" configured (in 
both directions in and out).
Executing "qdstat -l", it doesn't show me the address name; the "addr" field is 
empty.

Attached you can find the file with output.

  was:
I have a router with a link routed link for address "my_queue" configured (in 
both directions in and out).
Executing "qdstat -l", it doesn't show me the address name; the "addr" field is 
empty.

Router Links
  typedir  conn id  id  peer  class   addr  phs  
cap  undel  unsettled  deliveries  adminoper
  
=
  router-control  in   27
250  0  0  2876enabled  up
  router-control  out  28 local   qdhello
250  0  0  2716enabled  up
  inter-routerin   29
250  0  0  1   enabled  up
  inter-routerout  210   
250  0  0  1   enabled  up
  endpointin   111mobile  my_queue_wp   1
250  0  0  3   enabled  up
  endpointout  112mobile  my_queue_wp   0
250  0  0  3   enabled  up
  endpointout  415mobile  my_address0
250  0  0  0   enabled  up
  endpointout  618  19   
250  0  0  1   enabled  up
  endpointin   119  18   0  
  0  0  1   enabled  up
  endpointout  19   40mobile  my_queue_wp   1
250  0  0  1   enabled  up
  endpointin   24   48mobile  $management   0
250  0  0  1   enabled  up
  endpointout  24   49local   temp.mx5HxzUe2Eddw_s   
250  0  0  0   enabled  up


> Address field is empty for link routed links in the qdstat "links" output
> -
>
> Key: DISPATCH-357
> URL: https://issues.apache.org/jira/browse/DISPATCH-357
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Paolo Patierno
> Attachments: qdstat_links.txt
>
>
> I have a router with a link routed link for address "my_queue" configured (in 
> both directions in and out).
> Executing "qdstat -l", it doesn't show me the address name; the "addr" field 
> is empty.
> Attached you can find the file with output.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (DISPATCH-357) Address field is empty for link routed links in the qdstat "links" output

[Paolo Patierno (JIRA)]

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

Paolo Patierno updated DISPATCH-357:

Attachment: qdstat_links.txt

> Address field is empty for link routed links in the qdstat "links" output
> -
>
> Key: DISPATCH-357
> URL: https://issues.apache.org/jira/browse/DISPATCH-357
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Paolo Patierno
> Attachments: qdstat_links.txt
>
>
> I have a router with a link routed link for address "my_queue" configured (in 
> both directions in and out).
> Executing "qdstat -l", it doesn't show me the address name; the "addr" field 
> is empty.
> Router Links
>   typedir  conn id  id  peer  class   addr  phs  
> cap  undel  unsettled  deliveries  adminoper
>   
> =
>   router-control  in   27
> 250  0  0  2876enabled  up
>   router-control  out  28 local   qdhello
> 250  0  0  2716enabled  up
>   inter-routerin   29
> 250  0  0  1   enabled  up
>   inter-routerout  210   
> 250  0  0  1   enabled  up
>   endpointin   111mobile  my_queue_wp   1
> 250  0  0  3   enabled  up
>   endpointout  112mobile  my_queue_wp   0
> 250  0  0  3   enabled  up
>   endpointout  415mobile  my_address0
> 250  0  0  0   enabled  up
>   endpointout  618  19   
> 250  0  0  1   enabled  up
>   endpointin   119  18   
> 00  0  1   enabled  up
>   endpointout  19   40mobile  my_queue_wp   1
> 250  0  0  1   enabled  up
>   endpointin   24   48mobile  $management   0
> 250  0  0  1   enabled  up
>   endpointout  24   49local   temp.mx5HxzUe2Eddw_s   
> 250  0  0  0   enabled  up



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (DISPATCH-357) Address field is empty for link routed links in the qdstat "links" output

[Paolo Patierno (JIRA)]

Paolo Patierno created DISPATCH-357:
---

 Summary: Address field is empty for link routed links in the 
qdstat "links" output
 Key: DISPATCH-357
 URL: https://issues.apache.org/jira/browse/DISPATCH-357
 Project: Qpid Dispatch
  Issue Type: Bug
Affects Versions: 0.6.0
Reporter: Paolo Patierno
 Attachments: qdstat_links.txt

I have a router with a link routed link for address "my_queue" configured (in 
both directions in and out).
Executing "qdstat -l", it doesn't show me the address name; the "addr" field is 
empty.

Router Links
  typedir  conn id  id  peer  class   addr  phs  
cap  undel  unsettled  deliveries  adminoper
  
=
  router-control  in   27
250  0  0  2876enabled  up
  router-control  out  28 local   qdhello
250  0  0  2716enabled  up
  inter-routerin   29
250  0  0  1   enabled  up
  inter-routerout  210   
250  0  0  1   enabled  up
  endpointin   111mobile  my_queue_wp   1
250  0  0  3   enabled  up
  endpointout  112mobile  my_queue_wp   0
250  0  0  3   enabled  up
  endpointout  415mobile  my_address0
250  0  0  0   enabled  up
  endpointout  618  19   
250  0  0  1   enabled  up
  endpointin   119  18   0  
  0  0  1   enabled  up
  endpointout  19   40mobile  my_queue_wp   1
250  0  0  1   enabled  up
  endpointin   24   48mobile  $management   0
250  0  0  1   enabled  up
  endpointout  24   49local   temp.mx5HxzUe2Eddw_s   
250  0  0  0   enabled  up



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (PROTON-1216) c++: proton::coerce() should allow conversion from binary.

[Alan Conway (JIRA)]

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

Alan Conway commented on PROTON-1216:
-

Request to include the patch above in 0.13. Fully source compatible, fixes the 
reported bug and several others found by improved testing.

There will be one more commit on this JIRA to master only to remove deprecated 
and redundant code and tidy up, that will not be included in the next release. 

> c++: proton::coerce() should allow conversion from binary.
> ---
>
> Key: PROTON-1216
> URL: https://issues.apache.org/jira/browse/PROTON-1216
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.13.0
>
>
> proton::coerce should convert a binary value to a std::string. 
> The documentation also needs clarification: coerce should allow exactly those 
> conversions that are allowed as implicit C++ conversions.
> Issue raised in excellent bug report on the user list 
> http://qpid.2158936.n2.nabble.com/Proton-C-0-13-x-decode-binary-type-tp7644510p7644747.html
>  text follows:
> proton::coerce (both forms) currently throws the same
> exception as proton::get, as does value.as_string(), although that doesn't
> appear to be in the public API. Not sure what 'd' was in the d>>b  example,
> but got a version working using value.get() and an implicit
> cast to std::string.
> To reproduce...
> #include 
> #include 
> #include 
> #include 
> template
> void expect_exception ( Lambda f )
> {
>   try
>   {
> f();
> std::cout << "*** FAIL (expected conversion error) ***" << std::endl;
>   }
>   catch ( const proton::conversion_error& e )
>   {
> std::cout << "PASS" << std::endl;
>   }
> }
> template
> void expect_value ( const std::string& expected, Lambda f )
> {
>   try
>   {
> std::cout << (f() == expected ? "PASS" : "*** FAIL (wrong value) ***")
> << std::endl;
>   }
>   catch ( const proton::conversion_error& e )
>   {
> std::cout << "*** FAIL (conversion error) ***" << std::endl;
>   }
> }
> int main()
> {
>   std::string expected = "Hello World!";
>   proton::value value = proton::binary(expected);
>   expect_exception(  [=] { return value.get();   
>  
> });
>   expect_exception(  [=] { return proton::get(value);
>  
> });
>   expect_exception(  [=] { std::string result;
> proton::get(value); return result; });
>   expect_value(expected, [=] () -> std::string { return
> value.get(); } );
>   // The following currently fail under 0.13.x
>   expect_value(expected, [=] { return value.as_string();  
>  
> });
>   expect_value(expected, [=] { return proton::coerce(value); 
>  
> });
>   expect_value(expected, [=] { std::string result;
> proton::coerce(value, result); return result; });
>   
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (PROTON-1216) c++: proton::coerce() should allow conversion from binary.

[ASF subversion and git services (JIRA)]

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

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

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

PROTON-1216: c++: proton::coerce should convert binary to string.

Make scalar and value coerce<> consistent with C++ implicit conversions and 
each other.

- No source api change (still have deprecated functions)
- Better test coverage, consistent tests for value and scalar where applicable.
- Fixed unknown integer type conversions for scalar.
- Fixed examples using deprecated APIs (deprecated APIs are still in place)
- Consistent printing of scalar values, repect the std::ios::boolalpha flag for 
printing bool.


> c++: proton::coerce() should allow conversion from binary.
> ---
>
> Key: PROTON-1216
> URL: https://issues.apache.org/jira/browse/PROTON-1216
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.13.0
>
>
> proton::coerce should convert a binary value to a std::string. 
> The documentation also needs clarification: coerce should allow exactly those 
> conversions that are allowed as implicit C++ conversions.
> Issue raised in excellent bug report on the user list 
> http://qpid.2158936.n2.nabble.com/Proton-C-0-13-x-decode-binary-type-tp7644510p7644747.html
>  text follows:
> proton::coerce (both forms) currently throws the same
> exception as proton::get, as does value.as_string(), although that doesn't
> appear to be in the public API. Not sure what 'd' was in the d>>b  example,
> but got a version working using value.get() and an implicit
> cast to std::string.
> To reproduce...
> #include 
> #include 
> #include 
> #include 
> template
> void expect_exception ( Lambda f )
> {
>   try
>   {
> f();
> std::cout << "*** FAIL (expected conversion error) ***" << std::endl;
>   }
>   catch ( const proton::conversion_error& e )
>   {
> std::cout << "PASS" << std::endl;
>   }
> }
> template
> void expect_value ( const std::string& expected, Lambda f )
> {
>   try
>   {
> std::cout << (f() == expected ? "PASS" : "*** FAIL (wrong value) ***")
> << std::endl;
>   }
>   catch ( const proton::conversion_error& e )
>   {
> std::cout << "*** FAIL (conversion error) ***" << std::endl;
>   }
> }
> int main()
> {
>   std::string expected = "Hello World!";
>   proton::value value = proton::binary(expected);
>   expect_exception(  [=] { return value.get();   
>  
> });
>   expect_exception(  [=] { return proton::get(value);
>  
> });
>   expect_exception(  [=] { std::string result;
> proton::get(value); return result; });
>   expect_value(expected, [=] () -> std::string { return
> value.get(); } );
>   // The following currently fail under 0.13.x
>   expect_value(expected, [=] { return value.as_string();  
>  
> });
>   expect_value(expected, [=] { return proton::coerce(value); 
>  
> });
>   expect_value(expected, [=] { std::string result;
> proton::coerce(value, result); return result; });
>   
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (PROTON-1217) Sporadic memory leak in C++ container_test

[Alan Conway (JIRA)]

Alan Conway created PROTON-1217:
---

 Summary: Sporadic memory leak in C++ container_test
 Key: PROTON-1217
 URL: https://issues.apache.org/jira/browse/PROTON-1217
 Project: Qpid Proton
  Issue Type: Bug
  Components: cpp-binding
Affects Versions: 0.12.2
Reporter: Alan Conway
Assignee: Alan Conway
Priority: Blocker
 Fix For: 0.13.0


There is a sporadic leak (I see it about every 3-4 test runs) in the C++ unite 
tests, valgrind details below:

{code}
 8/10 Test #13: cpp_container_test ...***Failed2.45 sec
==30795== 1,200 (48 direct, 1,152 indirect) bytes in 3 blocks are definitely 
lost in loss record 2 of 3
==30795==at 0x4C29216: operator new(unsigned long) (vg_replace_malloc.c:334)
==30795==by 0x4E6EF32: 
proton::container::listen(std::__cxx11::basic_string const&, 
proton::connection_options const&) (container.cpp:83)
==30795==by 0x4E6EFC3: 
proton::container::listen(std::__cxx11::basic_string const&) (container.cpp:87)
==30795==by 0x404313: (anonymous 
namespace)::test_handler::on_container_start(proton::container&) 
(container_test.cpp:67)
==30795==by 0x4E804AF: 
proton::messaging_adapter::on_reactor_init(proton::proton_event&) 
(messaging_adapter.cpp:63)
==30795==by 0x4E82D62: 
proton::proton_event::dispatch(proton::proton_handler&) (proton_event.cpp:36)
==30795==by 0x4E71483: proton::handler_context::dispatch(pn_handler_t*, 
pn_event_t*, pn_event_type_t) (container_impl.cpp:71)
==30795==by 0x50ED57D: pn_handler_dispatch (handler.c:102)
==30795==by 0x50ECE8C: pn_reactor_process (reactor.c:402)
==30795==by 0x50ED2A8: pn_reactor_run (reactor.c:480)
==30795==by 0x4E83F2D: proton::reactor::run() (reactor.cpp:38)
==30795==by 0x4E7091F: proton::container_impl::run() 
(container_impl.cpp:258)
==30795== 
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[GitHub] qpid-proton pull request: proton-j : Upgrade BouncyCastle

[JemDay]

Github user JemDay commented on the pull request:

https://github.com/apache/qpid-proton/pull/74
  
I'm not sure what the CI build is doing to cause it to fail but i can 
confirm that "mvn clean test" works for me from the command line .. see attached

[build-log.txt](https://github.com/apache/qpid-proton/files/291766/build-log.txt)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] qpid-proton pull request: proton-j : Upgrade BouncyCastle

[JemDay]

GitHub user JemDay opened a pull request:

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

proton-j : Upgrade BouncyCastle

Changed to use a  dependency.
Removed 'reflective' constructs.
Verified correct test operations with BC 1.48 and 1.54

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

$ git pull https://github.com/JemDay/qpid-proton master

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

https://github.com/apache/qpid-proton/pull/74.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 #74


commit 1cdd0ff54af9b7c04696af259b842b785da9c862
Author: Jem Day 
Date:   2016-05-27T21:30:31Z

Update to support newer BouncyCastle Implementations.
Change to 'provided' dependency to simplify coding.
Full tests pass with BC 1.48 and 1.54

commit ed450edb35617ba813b9b3ec649bf53fe230cc01
Author: Day, Jeremy(jday) 
Date:   2016-05-31T15:44:46Z

Merge pull request #1 from jday/master

For Internal Review




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[jira] [Resolved] (DISPATCH-356) Creating and deleting a listener on already listening port causes router to crash

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy resolved DISPATCH-356.

   Resolution: Fixed
Fix Version/s: 0.6.0

> Creating and deleting a listener on already listening port causes router to 
> crash
> -
>
> Key: DISPATCH-356
> URL: https://issues.apache.org/jira/browse/DISPATCH-356
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 0.6.0
>
>
> Steps to reproduce - 
> 1. Start a router with listener listening on the standard amqp port 5672
> 2. qdmanage -b amqp://localhost:5672 create --type=listener addr=localhost 
> port=5672 name=localhost.5672.listener authenticatePeer=false
> 3. qdmanage -b amqp://localhost:5672 delete --type=listener --name 
> localhost.5672.listener
> Step #3 will cause the router to crash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (DISPATCH-356) Creating and deleting a listener on already listening port causes router to crash

[ASF subversion and git services (JIRA)]

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

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

Commit 724600022282fe23c3f27d0072906026bed48dd0 in qpid-dispatch's branch 
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7246000 ]

DISPATCH-356 - Added a null check in qd_server_listener_close


> Creating and deleting a listener on already listening port causes router to 
> crash
> -
>
> Key: DISPATCH-356
> URL: https://issues.apache.org/jira/browse/DISPATCH-356
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>
> Steps to reproduce - 
> 1. Start a router with listener listening on the standard amqp port 5672
> 2. qdmanage -b amqp://localhost:5672 create --type=listener addr=localhost 
> port=5672 name=localhost.5672.listener authenticatePeer=false
> 3. qdmanage -b amqp://localhost:5672 delete --type=listener --name 
> localhost.5672.listener
> Step #3 will cause the router to crash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (DISPATCH-356) Creating and deleting a listener on already listening port causes router to crash

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy updated DISPATCH-356:
---
Description: 
Steps to reproduce - 

1. Start a router with listener listening on the standard amqp port 5672
2. qdmanage -b amqp://localhost:5672 create --type=listener addr=localhost 
port=5672 name=localhost.5672.listener authenticatePeer=false
3. qdmanage -b amqp://localhost:5672 delete --type=listener --name 
localhost.5672.listener

Step #3 will cause the router to crash

> Creating and deleting a listener on already listening port causes router to 
> crash
> -
>
> Key: DISPATCH-356
> URL: https://issues.apache.org/jira/browse/DISPATCH-356
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>
> Steps to reproduce - 
> 1. Start a router with listener listening on the standard amqp port 5672
> 2. qdmanage -b amqp://localhost:5672 create --type=listener addr=localhost 
> port=5672 name=localhost.5672.listener authenticatePeer=false
> 3. qdmanage -b amqp://localhost:5672 delete --type=listener --name 
> localhost.5672.listener
> Step #3 will cause the router to crash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (DISPATCH-356) Creating and deleting a listener on already listening port causes router to crash

[Ganesh Murthy (JIRA)]

Ganesh Murthy created DISPATCH-356:
--

 Summary: Creating and deleting a listener on already listening 
port causes router to crash
 Key: DISPATCH-356
 URL: https://issues.apache.org/jira/browse/DISPATCH-356
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Container
Affects Versions: 0.6.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Resolved] (PROTON-1159) [C++ binding] Improvements and updates necessary for qpid-interop-test

[Kim van der Riet (JIRA)]

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

Kim van der Riet resolved PROTON-1159.
--
Resolution: Fixed

Completed

> [C++ binding] Improvements and updates necessary for qpid-interop-test
> --
>
> Key: PROTON-1159
> URL: https://issues.apache.org/jira/browse/PROTON-1159
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> A number of changes, additions and improvements which simplify the use of the 
> binding on qpid-interop-test (an interop test for AMQP clients).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7116) Ability to utilise group information from a LDAP compatible directory

[ASF subversion and git services (JIRA)]

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

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

Commit 1746288 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1746288 ]

QPID-7116: [Java Broker] AMQP 1.0 and SaslServlet now use subjectCreator for 
authentication

before they were using saslServer directly.
This was going to be problamatic when we want to augment the subject with group 
principals.
All code paths should now be using the subjectCreator

> Ability to utilise group information from a LDAP compatible directory
> -
>
> Key: QPID-7116
> URL: https://issues.apache.org/jira/browse/QPID-7116
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
> Attachments: 0001-WIP-unification.patch, 0002-WIP-LDAP-groups.patch
>
>
> The Java Broker can already authenticate users against an LDAP compatible 
> directory.  It should also be able to use the same information source as a 
> source of group information too.
> The authentication provide needs to accept optional attributes governing 
> where the group information will be found:
> {{groupSearchContext}} - the base entry for the role search. If not 
> specified, the search base is the top-level directory context.
> {{groupSearchFilter}} - the LDAP search filter for selecting group entries.  
> A {0} token within the filter will be replaced by the distinguish name of the 
> authenticated user.
> {{groupAttributeName}} - the name of the attribute that contains the name of 
> the role.
> After the authentication provider has successfully bound (authenticated) the 
> user, it should perform a second query for the groups.  It should build a 
> {{GroupPrincipal}} for each group to which the user belongs and return this 
> as part of the AuthenticationResult.   If the group search attributes are not 
> found, the group search should be skipped.
> A future version if the LDAP Authentication Provider may offer the ability to 
> cache the group results for a DN period of time.  This would serve to avoid 
> hitting the Directory several times authentication (it already hits the 
> Directory twice if {{bindWithoutSearch}} is false, this will add a third).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Comment Edited] (QPIDJMS-183) JmsConnectionFactory cannot support setSSL and setSSLContext method in amqp 1.0

[Timothy Bish (JIRA)]

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

Timothy Bish edited comment on QPIDJMS-183 at 5/31/16 2:37 PM:
---

The SSL configuration is done via the URI or using the standard Java 
environment properties, there is no need to set an SSLContext to use SSL.

The documentation cover SSL configuration: 
http://qpid.apache.org/releases/qpid-jms-0.9.0/docs/index.html


was (Author: tabish121):
The SSL configuration is done via the URI or using the standard Java 
environment properties, there is no need to set an SSLContext to use SSL.

> JmsConnectionFactory cannot support setSSL and setSSLContext method in amqp 
> 1.0
> ---
>
> Key: QPIDJMS-183
> URL: https://issues.apache.org/jira/browse/QPIDJMS-183
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.9.0
>Reporter: Steven
>
> For AMQP 1.0 older API "qpid-amqp-1-0-client-jms-0.32",Its 
> ConnectionFactoryImpl class provided setSSL and setSSLContext method,and For 
> AMQP 1.0 new API  "qpid-jms-0.9.0",Its JmsConnectionFactory didn't have 
> setSSL and setSSLContext method,Why will it design this,Could you add these 
> method in new version connection factory



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPIDJMS-183) JmsConnectionFactory cannot support setSSL and setSSLContext method in amqp 1.0

[Timothy Bish (JIRA)]

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

Timothy Bish commented on QPIDJMS-183:
--

The SSL configuration is done via the URI or using the standard Java 
environment properties, there is no need to set an SSLContext to use SSL.

> JmsConnectionFactory cannot support setSSL and setSSLContext method in amqp 
> 1.0
> ---
>
> Key: QPIDJMS-183
> URL: https://issues.apache.org/jira/browse/QPIDJMS-183
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.9.0
>Reporter: Steven
>
> For AMQP 1.0 older API "qpid-amqp-1-0-client-jms-0.32",Its 
> ConnectionFactoryImpl class provided setSSL and setSSLContext method,and For 
> AMQP 1.0 new API  "qpid-jms-0.9.0",Its JmsConnectionFactory didn't have 
> setSSL and setSSLContext method,Why will it design this,Could you add these 
> method in new version connection factory



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7248:
-
Description: 
Extend the UI to allow the user to save a query so that it is available for use 
later on.  The user should be able to see a list of saved queries, pick one and 
rerun it or change it.  The user should be able to delete queries too.

The user should also be able to see queries that are visible to him.  He should 
be able to select these queries and execute them.

* When defining a query, the UI should offer a 'save as' button allowing the 
query to be named, visibility to be chosen, and saved.
* If the query has been saved already, the name should be filled in already.
* Saved queries and queries that are visible to the user will appear to the 
user as a list (expandable/collapsible widget)
* From the list the user will be able to delete queries that belong to him.
* Also from the list, the user will be able to recall queries (either queries 
that belong to him or ones that are visible).  The query will be recalled in 
the advanced
 view, even if the query is representable in standard view.

  was:
Extend the UI to allow the user to save a query so that it is available for use 
later on.  The user should be able to see a list of saved queries, pick one and 
rerun it or change it.  The user should be able to delete queries too.

The user should also be able to see queries that are visible to him.  He should 
be able to select these queries and execute them.

* When defining a query, the UI should offer a 'save as' button allowing the 
query to be named, visibility to be chosen, and saved.
* If the query has been saved already, the name should be filled in already.
* Saved queries and queries that are visible to the user will appear to the 
user as a list (expandable/collapsible widget)
* From the list the user will be able to delete queries that belong to him.
* Also from the list, the user will be able to recall queries (either queries 
that belong to him or ones that are visible).  The query will be recalled in 
advance view, even if the query is representable in standard view.


> Extend the UI to allow queries to be saved, retrieved and re-run
> 
>
> Key: QPID-7248
> URL: https://issues.apache.org/jira/browse/QPID-7248
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> Extend the UI to allow the user to save a query so that it is available for 
> use later on.  The user should be able to see a list of saved queries, pick 
> one and rerun it or change it.  The user should be able to delete queries too.
> The user should also be able to see queries that are visible to him.  He 
> should be able to select these queries and execute them.
> * When defining a query, the UI should offer a 'save as' button allowing the 
> query to be named, visibility to be chosen, and saved.
> * If the query has been saved already, the name should be filled in already.
> * Saved queries and queries that are visible to the user will appear to the 
> user as a list (expandable/collapsible widget)
> * From the list the user will be able to delete queries that belong to him.
> * Also from the list, the user will be able to recall queries (either queries 
> that belong to him or ones that are visible).  The query will be recalled in 
> the advanced
>  view, even if the query is representable in standard view.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7248) Extend the UI to allow queries to be saved, retrieved and re-run

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7248:
-
Fix Version/s: qpid-java-6.1

> Extend the UI to allow queries to be saved, retrieved and re-run
> 
>
> Key: QPID-7248
> URL: https://issues.apache.org/jira/browse/QPID-7248
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> Extend the UI to allow the user to save a query so that it is available for 
> use later on.  The user should be able to see a list of saved queries, pick 
> one and rerun it or change it.  The user should be able to delete queries too.
> The user should also be able to see queries that are visible to him.  He 
> should be able to select these queries and execute them.
> * When defining a query, the UI should offer a 'save as' button allowing the 
> query to be named, visibility to be chosen, and saved.
> * If the query has been saved already, the name should be filled in already.
> * Saved queries and queries that are visible to the user will appear to the 
> user as a list (expandable/collapsible widget)
> * From the list the user will be able to delete queries that belong to him.
> * Also from the list, the user will be able to recall queries (either queries 
> that belong to him or ones that are visible).  The query will be recalled in 
> advance view, even if the query is representable in standard view.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7282) Java Broker should always send server-final message (if required) to the client on succesful SASL negotiation

[ASF subversion and git services (JIRA)]

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

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

Commit 1746273 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1746273 ]

QPID-7282: [Java Broker] AMQP Protocol layer now detects final SASL challenge 
directly instead of relying on AuthenticationResultStatus

Before, AuthenticationResult status was set to CONTINUE if the SASL negotiation 
completed but there was a final challenge.
Now, AuthenticationResult status reflects the SASL negotiation status and the 
AMQP layer detects the presence of a final challenge and issues one more AMQP 
authentication negotiation

> Java Broker should always send server-final message (if required) to the 
> client on succesful SASL negotiation
> -
>
> Key: QPID-7282
> URL: https://issues.apache.org/jira/browse/QPID-7282
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1, 
> qpid-java-6.0.2, qpid-java-6.0.3, qpid-java-6.1
>Reporter: Alex Rudyy
> Fix For: qpid-java-6.1, qpid-java-6.0.4
>
>
> On Scram Sha SASL negotiation Broker does not send server-final challenge 
> (ServerSignature) with the following authentication providers:
> * Simple (SimpleAuthenticationManager)
> * PlainPasswordFile (PlainPasswordDatabaseAuthenticationManager)
> The sasl negotiation for Scram Sha SASL mechanisms should always include 
> sending of server-final message in order to give a chance to verify server 
> signature on a client as per  [RFC 
> 5802|https://tools.ietf.org/html/rfc5802#page-7]
> {quote}
>   The client then authenticates the server by computing the
>ServerSignature and comparing it to the value sent by the server.  If
>the two are different, the client MUST consider the authentication
>exchange to be unsuccessful, and it might have to drop the
>connection.
> {quote}
> We need to change all existing Authentication Provider to support sending of 
> final message



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (PROTON-1216) c++: proton::coerce() should allow conversion from binary.

[Alan Conway (JIRA)]

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

Alan Conway updated PROTON-1216:

Description: 
proton::coerce should convert a binary value to a std::string. The 
documentation also needs clarification: coerce should allow exactly those 
conversions that are allowed as implicit C++ conversions.

Issue raised in excellent bug report on the user list 
http://qpid.2158936.n2.nabble.com/Proton-C-0-13-x-decode-binary-type-tp7644510p7644747.html
 text follows:

proton::coerce (both forms) currently throws the same
exception as proton::get, as does value.as_string(), although that doesn't
appear to be in the public API. Not sure what 'd' was in the d>>b  example,
but got a version working using value.get() and an implicit
cast to std::string.

To reproduce...

#include 
#include 
#include 
#include 

template
void expect_exception ( Lambda f )
{
  try
  {
f();
std::cout << "*** FAIL (expected conversion error) ***" << std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "PASS" << std::endl;
  }
}

template
void expect_value ( const std::string& expected, Lambda f )
{
  try
  {
std::cout << (f() == expected ? "PASS" : "*** FAIL (wrong value) ***")
<< std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "*** FAIL (conversion error) ***" << std::endl;
  }

}

int main()
{

  std::string expected = "Hello World!";
  proton::value value = proton::binary(expected);

  expect_exception(  [=] { return value.get();
});
  expect_exception(  [=] { return proton::get(value); 
});
  expect_exception(  [=] { std::string result;
proton::get(value); return result; });

  expect_value(expected, [=] () -> std::string { return
value.get(); } );

  // The following currently fail under 0.13.x
  expect_value(expected, [=] { return value.as_string();   
});
  expect_value(expected, [=] { return proton::coerce(value);  
});
  expect_value(expected, [=] { std::string result;
proton::coerce(value, result); return result; });
  
}


  was:
proton::coerce should convert a binary value to a std::string. The 
documentation also needs clarification: coerce should allow exactly those 
conversions that are allowed as explicit or implicit C++ conversions.

Issue raised in excellent bug report on the user list 
http://qpid.2158936.n2.nabble.com/Proton-C-0-13-x-decode-binary-type-tp7644510p7644747.html
 text follows:

proton::coerce (both forms) currently throws the same
exception as proton::get, as does value.as_string(), although that doesn't
appear to be in the public API. Not sure what 'd' was in the d>>b  example,
but got a version working using value.get() and an implicit
cast to std::string.

To reproduce...

#include 
#include 
#include 
#include 

template
void expect_exception ( Lambda f )
{
  try
  {
f();
std::cout << "*** FAIL (expected conversion error) ***" << std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "PASS" << std::endl;
  }
}

template
void expect_value ( const std::string& expected, Lambda f )
{
  try
  {
std::cout << (f() == expected ? "PASS" : "*** FAIL (wrong value) ***")
<< std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "*** FAIL (conversion error) ***" << std::endl;
  }

}

int main()
{

  std::string expected = "Hello World!";
  proton::value value = proton::binary(expected);

  expect_exception(  [=] { return value.get();
});
  expect_exception(  [=] { return proton::get(value); 
});
  expect_exception(  [=] { std::string result;
proton::get(value); return result; });

  expect_value(expected, [=] () -> std::string { return
value.get(); } );

  // The following currently fail under 0.13.x
  expect_value(expected, [=] { return value.as_string();   
});
  expect_value(expected, [=] { return proton::coerce(value);  
});
  expect_value(expected, [=] { std::string result;
proton::coerce(value, result); return result; });
  
}



> c++: proton::coerce() should allow conversion from binary.
> ---
>
> Key: PROTON-1216
> URL: https://issues.apache.org/jira/browse/PROTON-1216
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.13.0
>
>
> proton::coerce should convert a binary value to a std::string. 
> The documentation also needs clarification: coerce should allow exactly those 
> conversions that are allowed as implicit C++ conversions.
> Issue raised in excellent bug report on the user list 
> 

[jira] [Created] (QPID-7287) Query parser fails silently with expression such as a + b

[Keith Wall (JIRA)]

Keith Wall created QPID-7287:


 Summary: Query parser fails silently with expression such as a + b
 Key: QPID-7287
 URL: https://issues.apache.org/jira/browse/QPID-7287
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Reporter: Keith Wall
 Fix For: qpid-java-6.1


There is a defect in the order-by (and select) parsing when the input is in the 
form a + b.  It seems the parser fails, but the exception is not reported back  
to the client, nor it is reported to the logs.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Comment Edited] (QPID-7165) Allow query results to be sorted and paginated

[Keith Wall (JIRA)]

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

Keith Wall edited comment on QPID-7165 at 5/31/16 1:18 PM:
---

There is a defect in the order-by (and select) parsing when the input is in the 
form {{a + b}}.  It seems the parser fails, but the exception is not reported 
(raised as separate JIRA  QPID-7287)


was (Author: k-wall):
There is a defect in the order-by (and select) parsing when the input is in the 
form {{a + b}}.  It seems the parser fails, but the exception is not reported.

> Allow query results to be sorted and paginated
> --
>
> Key: QPID-7165
> URL: https://issues.apache.org/jira/browse/QPID-7165
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments: 
> 0001-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0001-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0002-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0002-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0004-WIP.patch
>
>
> Extend the mechanism provided by QPID-6969 to allow for the results set to be 
> sorted by one or more columns and results set to be paginated.
> For the ordering clause, we could use SQL:2011 ORDER BY clause as a guide 
> e.g. {{orderBy='x ASC,y DESC,z'}}
> For the pagination, SQL standardisation does not include it. 
> https://en.wikipedia.org/wiki/Select_%28SQL%29#Result_limits We could opt for 
> {{limit=}} {{offset=}} like MySQL/Sybase.   We could also consider HTTP Range 
> headers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Resolved] (QPID-7165) Allow query results to be sorted and paginated

[Keith Wall (JIRA)]

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

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

> Allow query results to be sorted and paginated
> --
>
> Key: QPID-7165
> URL: https://issues.apache.org/jira/browse/QPID-7165
> Project: Qpid
>  Issue Type: New Feature
>  Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments: 
> 0001-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0001-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0002-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0002-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch, 
> 0004-WIP.patch
>
>
> Extend the mechanism provided by QPID-6969 to allow for the results set to be 
> sorted by one or more columns and results set to be paginated.
> For the ordering clause, we could use SQL:2011 ORDER BY clause as a guide 
> e.g. {{orderBy='x ASC,y DESC,z'}}
> For the pagination, SQL standardisation does not include it. 
> https://en.wikipedia.org/wiki/Select_%28SQL%29#Result_limits We could opt for 
> {{limit=}} {{offset=}} like MySQL/Sybase.   We could also consider HTTP Range 
> headers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (PROTON-1216) c++: proton::coerce() should allow conversion from binary.

[Alan Conway (JIRA)]

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

Alan Conway updated PROTON-1216:

Description: 
proton::coerce should convert a binary value to a std::string. The 
documentation also needs clarification: coerce should allow exactly those 
conversions that are allowed as explicit or implicit C++ conversions.

Issue raised in excellent bug report on the user list 
http://qpid.2158936.n2.nabble.com/Proton-C-0-13-x-decode-binary-type-tp7644510p7644747.html
 text follows:

proton::coerce (both forms) currently throws the same
exception as proton::get, as does value.as_string(), although that doesn't
appear to be in the public API. Not sure what 'd' was in the d>>b  example,
but got a version working using value.get() and an implicit
cast to std::string.

To reproduce...

#include 
#include 
#include 
#include 

template
void expect_exception ( Lambda f )
{
  try
  {
f();
std::cout << "*** FAIL (expected conversion error) ***" << std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "PASS" << std::endl;
  }
}

template
void expect_value ( const std::string& expected, Lambda f )
{
  try
  {
std::cout << (f() == expected ? "PASS" : "*** FAIL (wrong value) ***")
<< std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "*** FAIL (conversion error) ***" << std::endl;
  }

}

int main()
{

  std::string expected = "Hello World!";
  proton::value value = proton::binary(expected);

  expect_exception(  [=] { return value.get();
});
  expect_exception(  [=] { return proton::get(value); 
});
  expect_exception(  [=] { std::string result;
proton::get(value); return result; });

  expect_value(expected, [=] () -> std::string { return
value.get(); } );

  // The following currently fail under 0.13.x
  expect_value(expected, [=] { return value.as_string();   
});
  expect_value(expected, [=] { return proton::coerce(value);  
});
  expect_value(expected, [=] { std::string result;
proton::coerce(value, result); return result; });
  
}


  was:
proton::coerce should convert a binary value to a std::string. The 
documentation also needs clarification: coerce should allow exactly those 
conversions that are allowed as implicit C++ conversions.

Issue raised in excellent bug report on the user list 
http://qpid.2158936.n2.nabble.com/Proton-C-0-13-x-decode-binary-type-tp7644510p7644747.html
 text follows:

proton::coerce (both forms) currently throws the same
exception as proton::get, as does value.as_string(), although that doesn't
appear to be in the public API. Not sure what 'd' was in the d>>b  example,
but got a version working using value.get() and an implicit
cast to std::string.

To reproduce...

#include 
#include 
#include 
#include 

template
void expect_exception ( Lambda f )
{
  try
  {
f();
std::cout << "*** FAIL (expected conversion error) ***" << std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "PASS" << std::endl;
  }
}

template
void expect_value ( const std::string& expected, Lambda f )
{
  try
  {
std::cout << (f() == expected ? "PASS" : "*** FAIL (wrong value) ***")
<< std::endl;
  }
  catch ( const proton::conversion_error& e )
  {
std::cout << "*** FAIL (conversion error) ***" << std::endl;
  }

}

int main()
{

  std::string expected = "Hello World!";
  proton::value value = proton::binary(expected);

  expect_exception(  [=] { return value.get();
});
  expect_exception(  [=] { return proton::get(value); 
});
  expect_exception(  [=] { std::string result;
proton::get(value); return result; });

  expect_value(expected, [=] () -> std::string { return
value.get(); } );

  // The following currently fail under 0.13.x
  expect_value(expected, [=] { return value.as_string();   
});
  expect_value(expected, [=] { return proton::coerce(value);  
});
  expect_value(expected, [=] { std::string result;
proton::coerce(value, result); return result; });
  
}



> c++: proton::coerce() should allow conversion from binary.
> ---
>
> Key: PROTON-1216
> URL: https://issues.apache.org/jira/browse/PROTON-1216
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.12.2
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.13.0
>
>
> proton::coerce should convert a binary value to a std::string. 
> The documentation also needs clarification: coerce should allow exactly those 
> conversions that are allowed as explicit or implicit C++ conversions.
> Issue raised in excellent bug report on the user list 
> 

[jira] [Commented] (DISPATCH-353) segfault in qd_entity_refresh_connection

[Gordon Sim (JIRA)]

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

Gordon Sim commented on DISPATCH-353:
-

Not as yet, no. I think it is related to deleting a connector. However simply 
deleting a connector for which an active connection exists doesn't reproduce 
the crash. I think it is a race somewhere (possibly between deleting the 
connector and trying to connect?). I've seen it several times now, but can't 
reliably reproduce it.

> segfault in qd_entity_refresh_connection
> 
>
> Key: DISPATCH-353
> URL: https://issues.apache.org/jira/browse/DISPATCH-353
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Gordon Sim
>Assignee: Ganesh Murthy
>
> {noformat}
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x7fa9828c091c in qd_entity_refresh_connection 
> (entity=0x7fa97508eb40, impl=0x7fa960015480) at 
> /home/gordon/projects/dispatch/src/server.c:342
> 342   conn->connector ? conn->connector->config : 
> conn->listener->config;
> [Current thread is 1 (Thread 0x7fa96700 (LWP 31641))]
> Missing separate debuginfos, use: dnf debuginfo-install 
> cyrus-sasl-gssapi-2.1.26-25.2.fc23.x86_64 
> cyrus-sasl-lib-2.1.26-25.2.fc23.x86_64 cyrus-sasl-md5-2.1.26-25.2.fc23.x86_64 
> cyrus-sasl-plain-2.1.26-25.2.fc23.x86_64 
> cyrus-sasl-scram-2.1.26-25.2.fc23.x86_64 glibc-2.22-11.fc23.x86_64 
> keyutils-libs-1.5.9-7.fc23.x86_64 krb5-libs-1.14.1-3.fc23.x86_64 
> libcom_err-1.42.13-3.fc23.x86_64 libdb-5.3.28-13.fc23.x86_64 
> libffi-3.1-8.fc23.x86_64 libselinux-2.4-4.fc23.x86_64 
> nss-softokn-freebl-3.23.0-1.0.fc23.x86_64 openssl-libs-1.0.2g-2.fc23.x86_64 
> pcre-8.38-7.fc23.x86_64 python-libs-2.7.10-8.fc23.x86_64 
> sssd-client-1.13.3-5.fc23.x86_64 zlib-1.2.8-9.fc23.x86_64
> (gdb) bt
> #0  0x7fa9828c091c in qd_entity_refresh_connection 
> (entity=0x7fa97508eb40, impl=0x7fa960015480) at 
> /home/gordon/projects/dispatch/src/server.c:342
> #1  0x7fa977eaad30 in ffi_call_unix64 () from /lib64/libffi.so.6
> #2  0x7fa977eaa79b in ffi_call () from /lib64/libffi.so.6
> #3  0x7fa9780bddaf in _ctypes_callproc () from 
> /usr/lib64/python2.7/lib-dynload/_ctypes.so
> #4  0x7fa9780b79d4 in PyCFuncPtr_call () from 
> /usr/lib64/python2.7/lib-dynload/_ctypes.so
> #5  0x7fa981c92b03 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #6  0x7fa981d28a68 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #7  0x7fa981d2a666 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #8  0x7fa981d2a666 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #9  0x7fa981d2b6b4 in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
> #10 0x7fa981d2a5c6 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #11 0x7fa981d2b6b4 in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
> #12 0x7fa981cb75ac in function_call () from /lib64/libpython2.7.so.1.0
> #13 0x7fa981c92b03 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #14 0x7fa981ca195c in instancemethod_call () from 
> /lib64/libpython2.7.so.1.0
> #15 0x7fa981c92b03 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #16 0x7fa981c92be5 in call_function_tail () from 
> /lib64/libpython2.7.so.1.0
> #17 0x7fa981c92cce in PyObject_CallFunction () from 
> /lib64/libpython2.7.so.1.0
> #18 0x7fa9828b0917 in qd_io_rx_handler (context=0x7fa975026fc0, 
> msg=0x1a1e8c0, link_id=0) at 
> /home/gordon/projects/dispatch/src/python_embedded.c:516
> #19 0x7fa9828b6be2 in qdr_forward_on_message (core=, 
> work=0x7fa97004d7c0) at 
> /home/gordon/projects/dispatch/src/router_core/forwarder.c:121
> #20 0x7fa9828b8d34 in qdr_general_handler (context=0x199e180) at 
> /home/gordon/projects/dispatch/src/router_core/router_core.c:341
> #21 0x7fa9828c11e5 in thread_run (arg=0x19b79d0) at 
> /home/gordon/projects/dispatch/src/server.c:822
> #22 0x7fa98242460a in start_thread () from /lib64/libpthread.so.0
> #23 0x7fa981989a4d in clone () from /lib64/libc.so.6
> (gdb) frame 0
> #0  0x7fa9828c091c in qd_entity_refresh_connection 
> (entity=0x7fa97508eb40, impl=0x7fa960015480) at 
> /home/gordon/projects/dispatch/src/server.c:342
> 342   conn->connector ? conn->connector->config : 
> conn->listener->config;
> (gdb) print conn
> $1 = (qd_connection_t *) 0x7fa960015480
> (gdb) print conn->connector
> $2 = (qd_connector_t *) 0x0
> (gdb) print conn->listener
> $3 = (qd_listener_t *) 0x0
> (gdb) 
> {noformat}
> I don't have the exact steps that caused this yet, but core dump shows the 
> basic problem: neither connector nor listener is set and there is no check 
> for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (QPID-7044) [Java Broker] [AMQP0-9-1 ext] Publish confirm ack should be sent after performing a sync

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7044:
-
Fix Version/s: (was: qpid-java-6.1)

> [Java Broker] [AMQP0-9-1 ext] Publish confirm ack should be sent after 
> performing a sync
> 
>
> Key: QPID-7044
> URL: https://issues.apache.org/jira/browse/QPID-7044
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Keith Wall
>Priority: Minor
>
> When using publish confirms (the AMQP 0-9-1 extension), the Broker current 
> sends the Ack back to the client immediately after the message is received 
> completely.  It ought to sync (completing the unfinished commands) before 
> sending the Ack response.
> This defect does not affect use cases where messages are published in a 
> transaction. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Closed] (QPID-7044) [Java Broker] [AMQP0-9-1 ext] Publish confirm ack should be sent after performing a sync

[Keith Wall (JIRA)]

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

Keith Wall closed QPID-7044.

Resolution: Invalid

> [Java Broker] [AMQP0-9-1 ext] Publish confirm ack should be sent after 
> performing a sync
> 
>
> Key: QPID-7044
> URL: https://issues.apache.org/jira/browse/QPID-7044
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Keith Wall
>Priority: Minor
>
> When using publish confirms (the AMQP 0-9-1 extension), the Broker current 
> sends the Ack back to the client immediately after the message is received 
> completely.  It ought to sync (completing the unfinished commands) before 
> sending the Ack response.
> This defect does not affect use cases where messages are published in a 
> transaction. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7286) [Java Broker] List of supported versions brought back by invoking Main class with -v is incorrect

[ASF subversion and git services (JIRA)]

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

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

Commit 1746268 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1746268 ]

QPID-7286 : Fix the -v option to show the correct set of supported protocols

> [Java Broker] List of supported versions brought back by invoking Main class 
> with -v is incorrect
> -
>
> Key: QPID-7286
> URL: https://issues.apache.org/jira/browse/QPID-7286
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1, 
> qpid-java-6.0.2, qpid-java-6.0.3
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>Priority: Trivial
>
> We are building the version String from a class that is primarily use by the 
> client.
> We should instead use the set of plugins which are installed to determine the 
> protocol support.  Ultimately maybe -v should probably show all installed 
> plugins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (QPID-7286) [Java Broker] List of supported versions brought back by invoking Main class with -v is incorrect

[Rob Godfrey (JIRA)]

Rob Godfrey created QPID-7286:
-

 Summary: [Java Broker] List of supported versions brought back by 
invoking Main class with -v is incorrect
 Key: QPID-7286
 URL: https://issues.apache.org/jira/browse/QPID-7286
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: qpid-java-6.0.3, qpid-java-6.0.2, qpid-java-6.0.1, 
qpid-java-6.0, 0.32, 0.30, 0.28
Reporter: Rob Godfrey
Assignee: Rob Godfrey


We are building the version String from a class that is primarily use by the 
client.

We should instead use the set of plugins which are installed to determine the 
protocol support.  Ultimately maybe -v should probably show all installed 
plugins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7286) [Java Broker] List of supported versions brought back by invoking Main class with -v is incorrect

[Rob Godfrey (JIRA)]

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

Rob Godfrey updated QPID-7286:
--
Priority: Trivial  (was: Major)

> [Java Broker] List of supported versions brought back by invoking Main class 
> with -v is incorrect
> -
>
> Key: QPID-7286
> URL: https://issues.apache.org/jira/browse/QPID-7286
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1, 
> qpid-java-6.0.2, qpid-java-6.0.3
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
>Priority: Trivial
>
> We are building the version String from a class that is primarily use by the 
> client.
> We should instead use the set of plugins which are installed to determine the 
> protocol support.  Ultimately maybe -v should probably show all installed 
> plugins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7285) [Java Documentation] Documentation for legacy JMS client for AMQP 0.10 contains broken links

[Justin Ross (JIRA)]

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

Justin Ross commented on QPID-7285:
---

Indeed, see 
https://git-wip-us.apache.org/repos/asf?p=qpid-site.git;a=blob;f=input/_transom_ignore_links

Feel free to remove that file altogether when you're ready.


> [Java Documentation] Documentation for legacy JMS client for AMQP 0.10 
> contains broken links
> 
>
> Key: QPID-7285
> URL: https://issues.apache.org/jira/browse/QPID-7285
> Project: Qpid
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: qpid-java-6.0.3
>Reporter: Alex Rudyy
>
> Running site tool "make check-links"  reports a number of broken links in 
> documentation for legacy JMS client for AMQP 0.10
> {noformat}
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-trunk/jms-client-0-8/jms_client08-book.pdf
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-trunk/index.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/3.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/1.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/3.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/2.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/8.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/11.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/12.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/11.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/1.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/8.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/9.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/12.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/4.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> 

[jira] [Assigned] (DISPATCH-353) segfault in qd_entity_refresh_connection

[Ganesh Murthy (JIRA)]

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

Ganesh Murthy reassigned DISPATCH-353:
--

Assignee: Ganesh Murthy

> segfault in qd_entity_refresh_connection
> 
>
> Key: DISPATCH-353
> URL: https://issues.apache.org/jira/browse/DISPATCH-353
> Project: Qpid Dispatch
>  Issue Type: Bug
>Affects Versions: 0.6.0
>Reporter: Gordon Sim
>Assignee: Ganesh Murthy
>
> {noformat}
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x7fa9828c091c in qd_entity_refresh_connection 
> (entity=0x7fa97508eb40, impl=0x7fa960015480) at 
> /home/gordon/projects/dispatch/src/server.c:342
> 342   conn->connector ? conn->connector->config : 
> conn->listener->config;
> [Current thread is 1 (Thread 0x7fa96700 (LWP 31641))]
> Missing separate debuginfos, use: dnf debuginfo-install 
> cyrus-sasl-gssapi-2.1.26-25.2.fc23.x86_64 
> cyrus-sasl-lib-2.1.26-25.2.fc23.x86_64 cyrus-sasl-md5-2.1.26-25.2.fc23.x86_64 
> cyrus-sasl-plain-2.1.26-25.2.fc23.x86_64 
> cyrus-sasl-scram-2.1.26-25.2.fc23.x86_64 glibc-2.22-11.fc23.x86_64 
> keyutils-libs-1.5.9-7.fc23.x86_64 krb5-libs-1.14.1-3.fc23.x86_64 
> libcom_err-1.42.13-3.fc23.x86_64 libdb-5.3.28-13.fc23.x86_64 
> libffi-3.1-8.fc23.x86_64 libselinux-2.4-4.fc23.x86_64 
> nss-softokn-freebl-3.23.0-1.0.fc23.x86_64 openssl-libs-1.0.2g-2.fc23.x86_64 
> pcre-8.38-7.fc23.x86_64 python-libs-2.7.10-8.fc23.x86_64 
> sssd-client-1.13.3-5.fc23.x86_64 zlib-1.2.8-9.fc23.x86_64
> (gdb) bt
> #0  0x7fa9828c091c in qd_entity_refresh_connection 
> (entity=0x7fa97508eb40, impl=0x7fa960015480) at 
> /home/gordon/projects/dispatch/src/server.c:342
> #1  0x7fa977eaad30 in ffi_call_unix64 () from /lib64/libffi.so.6
> #2  0x7fa977eaa79b in ffi_call () from /lib64/libffi.so.6
> #3  0x7fa9780bddaf in _ctypes_callproc () from 
> /usr/lib64/python2.7/lib-dynload/_ctypes.so
> #4  0x7fa9780b79d4 in PyCFuncPtr_call () from 
> /usr/lib64/python2.7/lib-dynload/_ctypes.so
> #5  0x7fa981c92b03 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #6  0x7fa981d28a68 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #7  0x7fa981d2a666 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #8  0x7fa981d2a666 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #9  0x7fa981d2b6b4 in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
> #10 0x7fa981d2a5c6 in PyEval_EvalFrameEx () from 
> /lib64/libpython2.7.so.1.0
> #11 0x7fa981d2b6b4 in PyEval_EvalCodeEx () from /lib64/libpython2.7.so.1.0
> #12 0x7fa981cb75ac in function_call () from /lib64/libpython2.7.so.1.0
> #13 0x7fa981c92b03 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #14 0x7fa981ca195c in instancemethod_call () from 
> /lib64/libpython2.7.so.1.0
> #15 0x7fa981c92b03 in PyObject_Call () from /lib64/libpython2.7.so.1.0
> #16 0x7fa981c92be5 in call_function_tail () from 
> /lib64/libpython2.7.so.1.0
> #17 0x7fa981c92cce in PyObject_CallFunction () from 
> /lib64/libpython2.7.so.1.0
> #18 0x7fa9828b0917 in qd_io_rx_handler (context=0x7fa975026fc0, 
> msg=0x1a1e8c0, link_id=0) at 
> /home/gordon/projects/dispatch/src/python_embedded.c:516
> #19 0x7fa9828b6be2 in qdr_forward_on_message (core=, 
> work=0x7fa97004d7c0) at 
> /home/gordon/projects/dispatch/src/router_core/forwarder.c:121
> #20 0x7fa9828b8d34 in qdr_general_handler (context=0x199e180) at 
> /home/gordon/projects/dispatch/src/router_core/router_core.c:341
> #21 0x7fa9828c11e5 in thread_run (arg=0x19b79d0) at 
> /home/gordon/projects/dispatch/src/server.c:822
> #22 0x7fa98242460a in start_thread () from /lib64/libpthread.so.0
> #23 0x7fa981989a4d in clone () from /lib64/libc.so.6
> (gdb) frame 0
> #0  0x7fa9828c091c in qd_entity_refresh_connection 
> (entity=0x7fa97508eb40, impl=0x7fa960015480) at 
> /home/gordon/projects/dispatch/src/server.c:342
> 342   conn->connector ? conn->connector->config : 
> conn->listener->config;
> (gdb) print conn
> $1 = (qd_connection_t *) 0x7fa960015480
> (gdb) print conn->connector
> $2 = (qd_connector_t *) 0x0
> (gdb) print conn->listener
> $3 = (qd_listener_t *) 0x0
> (gdb) 
> {noformat}
> I don't have the exact steps that caused this yet, but core dump shows the 
> basic problem: neither connector nor listener is set and there is no check 
> for this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7279) [Java Broker] with config encryption creating a JDBC VirtualHost fails

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7279:
-
Fix Version/s: qpid-java-6.1

> [Java Broker] with config encryption creating a JDBC VirtualHost fails
> --
>
> Key: QPID-7279
> URL: https://issues.apache.org/jira/browse/QPID-7279
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-6.1
>
>
> If configuration encryption is enabled on the broker creating a JDBC 
> VirtualHost via the WMC fails with the following error:
> {{422 - Encrypted value is not valid Base 64 data: 'myPassword'}}
> Also we might not want to log the content of the invalid data due to its 
> potential sensitive nature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (DISPATCH-343) Router stops accepting connections after load from parallel senders

[Ted Ross (JIRA)]

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

Ted Ross commented on DISPATCH-343:
---

Quick status on this issue:
The thing about this test that causes the problem is that it uses 2-ack 
transfers.  The messages are sent by the sender, acknowledged (but not settled) 
by the receiver, then settled by the sender.  However, since it is built on 
Messenger with a limited windows size, sometimes the receiver will settle the 
deliveries (presumably because the window is full).  All of this should work 
fine of course, but it exposes a bug in the lifecycle management of deliveries 
in Dispatch Router.  A fix for this is imminent.
If this is a blocker for your project, you can probably work around it by 
switching away from 2-ack deliveries.  They are probably not providing any 
added value since Messenger doesn't support exactly-once delivery.

> Router stops accepting connections after load from parallel senders
> ---
>
> Key: DISPATCH-343
> URL: https://issues.apache.org/jira/browse/DISPATCH-343
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Routing Engine
>Affects Versions: 0.6.0
>Reporter: Vishal Sharda
>Assignee: Ted Ross
>Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: Connection_aborted.png, Connection_aborted_1.png, 
> Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf, 
> Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png, 
> bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf, 
> drivers.tar.gz, resource-limit-exceeded.png
>
>
> We ran 2 parallel senders and 2 receivers with each sender sending 5 
> messages.  After a while we saw that router stopped accepting connections 
> even from qdstat.  We saw various errors in the logs (screenshots attached).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7285) [Java Documentation] Documentation for legacy JMS client for AMQP 0.10 contains broken links

[Robbie Gemmell (JIRA)]

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

Robbie Gemmell commented on QPID-7285:
--

The docbook generation stuff is creating those links, for the callouts 
referenced on the example code. While the links do seem to work on the actual 
pages, it is presumably complaining about PNG files used as their src which 
dont actually exist, and using the alt-text instead. If you look at the 0-8 
client example pages youll find they have the same issue.

For whatever reason the check script is only identifying the problem for the 
new 0-10 relates bits. Perhaps there is a 'dont check these' flag 
tripped/not-tripped somewhere? [~justi9]?

I'd also note the couple of java-broker and 0-8 client links issues mentioned 
in the above output, for the qpid-trunk pages. Might be worth removing those 
bits.


> [Java Documentation] Documentation for legacy JMS client for AMQP 0.10 
> contains broken links
> 
>
> Key: QPID-7285
> URL: https://issues.apache.org/jira/browse/QPID-7285
> Project: Qpid
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: qpid-java-6.0.3
>Reporter: Alex Rudyy
>
> Running site tool "make check-links"  reports a number of broken links in 
> documentation for legacy JMS client for AMQP 0.10
> {noformat}
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-trunk/jms-client-0-8/jms_client08-book.pdf
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-trunk/index.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/3.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/1.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/3.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/2.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/8.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/11.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/12.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/11.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/1.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/8.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/9.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> 

[jira] [Resolved] (QPID-7284) [Java Performance Tests] json_config_tool should recursively descend into configuration

[Lorenz Quack (JIRA)]

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

Lorenz Quack resolved QPID-7284.

Resolution: Fixed

> [Java Performance Tests] json_config_tool should recursively descend into 
> configuration
> ---
>
> Key: QPID-7284
> URL: https://issues.apache.org/jira/browse/QPID-7284
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Performance Tests
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments: perftest_tool.diff
>
>
> The json_config_tool allows offline modification of broker configuration 
> files. It is given an object name and an attribute name and value which 
> should be changed on the object.
> However it currently does not search the entire configuration for the object 
> name. It only descends into arrays but not into nested objects.
> It should search the entire config file to enable modification of object 
> deeply nested in the object hierarchy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7284) [Java Performance Tests] json_config_tool should recursively descend into configuration

[Lorenz Quack (JIRA)]

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

Lorenz Quack updated QPID-7284:
---
Fix Version/s: qpid-java-6.1

> [Java Performance Tests] json_config_tool should recursively descend into 
> configuration
> ---
>
> Key: QPID-7284
> URL: https://issues.apache.org/jira/browse/QPID-7284
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Performance Tests
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments: perftest_tool.diff
>
>
> The json_config_tool allows offline modification of broker configuration 
> files. It is given an object name and an attribute name and value which 
> should be changed on the object.
> However it currently does not search the entire configuration for the object 
> name. It only descends into arrays but not into nested objects.
> It should search the entire config file to enable modification of object 
> deeply nested in the object hierarchy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7284) [Java Performance Tests] json_config_tool should recursively descend into configuration

[ASF subversion and git services (JIRA)]

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

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

Commit 1746261 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1746261 ]

QPID-7284: [Java Performance Tests] json_config_tool should recursively descend 
into configuration

> [Java Performance Tests] json_config_tool should recursively descend into 
> configuration
> ---
>
> Key: QPID-7284
> URL: https://issues.apache.org/jira/browse/QPID-7284
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Performance Tests
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>Priority: Minor
> Attachments: perftest_tool.diff
>
>
> The json_config_tool allows offline modification of broker configuration 
> files. It is given an object name and an attribute name and value which 
> should be changed on the object.
> However it currently does not search the entire configuration for the object 
> name. It only descends into arrays but not into nested objects.
> It should search the entire config file to enable modification of object 
> deeply nested in the object hierarchy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7285) [Java Documentation] Documentation for legacy JMS client for AMQP 0.10 contains broken links

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-7285:
-
Summary: [Java Documentation] Documentation for legacy JMS client for AMQP 
0.10 contains broken links  (was: [Java Documentation] Documentation for legacy 
JMS client for AMQP 0.10 contains broker links)

> [Java Documentation] Documentation for legacy JMS client for AMQP 0.10 
> contains broken links
> 
>
> Key: QPID-7285
> URL: https://issues.apache.org/jira/browse/QPID-7285
> Project: Qpid
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: qpid-java-6.0.3
>Reporter: Alex Rudyy
>
> Running site tool "make check-links"  reports a number of broken links in 
> documentation for legacy JMS client for AMQP 0.10
> {noformat}
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-trunk/jms-client-0-8/jms_client08-book.pdf
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-trunk/index.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/3.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/1.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/3.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/2.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/8.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/11.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/12.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/11.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/1.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/8.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/9.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/12.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/4.png
>   Error: Link has no target
>   Source: 
> file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
> Link: 
> 

[jira] [Created] (QPID-7285) [Java Documentation] Documentation for legacy JMS client for AMQP 0.10 contains broker links

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-7285:


 Summary: [Java Documentation] Documentation for legacy JMS client 
for AMQP 0.10 contains broker links
 Key: QPID-7285
 URL: https://issues.apache.org/jira/browse/QPID-7285
 Project: Qpid
  Issue Type: Bug
  Components: Documentation
Affects Versions: qpid-java-6.0.3
Reporter: Alex Rudyy


Running site tool "make check-links"  reports a number of broken links in 
documentation for legacy JMS client for AMQP 0.10
{noformat}
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-trunk/jms-client-0-8/jms_client08-book.pdf
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-trunk/index.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/3.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/1.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/3.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/2.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/8.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/11.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/12.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/11.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/1.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/8.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/9.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/12.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/images/callouts/4.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.2/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/images/callouts/10.png
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-java-6.0.3/jms-client-0-10/book/JMS-Client-0-10-Example.html
Link: 
file:///home/alex/workspace/site-git/output/releases/qpid-trunk/java-broker/java-broker-book.pdf
  Error: Link has no target
  Source: 
file:///home/alex/workspace/site-git/output/releases/qpid-trunk/index.html
Link: 

[jira] [Updated] (QPID-7284) [Java Performance Tests] json_config_tool should recursively descend into configuration

[Lorenz Quack (JIRA)]

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

Lorenz Quack updated QPID-7284:
---
Attachment: perftest_tool.diff

> [Java Performance Tests] json_config_tool should recursively descend into 
> configuration
> ---
>
> Key: QPID-7284
> URL: https://issues.apache.org/jira/browse/QPID-7284
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Performance Tests
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>Priority: Minor
> Attachments: perftest_tool.diff
>
>
> The json_config_tool allows offline modification of broker configuration 
> files. It is given an object name and an attribute name and value which 
> should be changed on the object.
> However it currently does not search the entire configuration for the object 
> name. It only descends into arrays but not into nested objects.
> It should search the entire config file to enable modification of object 
> deeply nested in the object hierarchy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (QPID-7284) [Java Performance Tests] json_config_tool should recursively descend into configuration

[Lorenz Quack (JIRA)]

Lorenz Quack created QPID-7284:
--

 Summary: [Java Performance Tests] json_config_tool should 
recursively descend into configuration
 Key: QPID-7284
 URL: https://issues.apache.org/jira/browse/QPID-7284
 Project: Qpid
  Issue Type: Improvement
  Components: Java Performance Tests
Reporter: Lorenz Quack
Assignee: Lorenz Quack
Priority: Minor


The json_config_tool allows offline modification of broker configuration files. 
It is given an object name and an attribute name and value which should be 
changed on the object.

However it currently does not search the entire configuration for the object 
name. It only descends into arrays but not into nested objects.

It should search the entire config file to enable modification of object deeply 
nested in the object hierarchy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7283) [Java Broker] Simplify SASL authentication functionality accros broker AMQP layers

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-7283:
-
Description: At the moment SASL authentication functionality in existing 
AMQP layers uses SaslServer created with authentication provider and calls 
SaslServer directly to process client responses. We can encapsulate SaslServer 
server under special SASL authentication API and simplify the existing SASL 
functionality.   (was: At the moment SASL authentication  uses SaslServer 
created with authentication provider and calls SaslServer directly to process 
client responses. We can encapsulate SaslServer server under special SASL 
authentication API and simplify the existing SASL functionality. )

> [Java Broker] Simplify SASL authentication functionality accros broker AMQP 
> layers
> --
>
> Key: QPID-7283
> URL: https://issues.apache.org/jira/browse/QPID-7283
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Alex Rudyy
>
> At the moment SASL authentication functionality in existing AMQP layers uses 
> SaslServer created with authentication provider and calls SaslServer directly 
> to process client responses. We can encapsulate SaslServer server under 
> special SASL authentication API and simplify the existing SASL functionality. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7283) [Java Broker] Simplify SASL authentication accros broker AMQP layers

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-7283:
-
Description: At the moment SASL authentication  uses SaslServer created 
with authentication provider and calls SaslServer directly to process client 
responses. We can encapsulate SaslServer server under special SASL 
authentication API and simplify the existing SASL functionality.   (was: At the 
moment SASL authentication  uses SaslServer created with authentication 
provider and calls SaslServer directly to process client responses. We can 
encapsulate SaslServer server under special SASL authentication API and 
simplify the entire SASL negotiation. )

> [Java Broker] Simplify SASL authentication accros broker AMQP layers
> 
>
> Key: QPID-7283
> URL: https://issues.apache.org/jira/browse/QPID-7283
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Alex Rudyy
>
> At the moment SASL authentication  uses SaslServer created with 
> authentication provider and calls SaslServer directly to process client 
> responses. We can encapsulate SaslServer server under special SASL 
> authentication API and simplify the existing SASL functionality. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (QPID-7283) [Java Broker] Simplify SASL authentication functionality accros broker AMQP layers

[Alex Rudyy (JIRA)]

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

Alex Rudyy updated QPID-7283:
-
Summary: [Java Broker] Simplify SASL authentication functionality accros 
broker AMQP layers  (was: [Java Broker] Simplify SASL authentication accros 
broker AMQP layers)

> [Java Broker] Simplify SASL authentication functionality accros broker AMQP 
> layers
> --
>
> Key: QPID-7283
> URL: https://issues.apache.org/jira/browse/QPID-7283
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Reporter: Alex Rudyy
>
> At the moment SASL authentication  uses SaslServer created with 
> authentication provider and calls SaslServer directly to process client 
> responses. We can encapsulate SaslServer server under special SASL 
> authentication API and simplify the existing SASL functionality. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (QPID-7283) [Java Broker] Simplify SASL authentication accros broker AMQP layers

[Alex Rudyy (JIRA)]

Alex Rudyy created QPID-7283:


 Summary: [Java Broker] Simplify SASL authentication accros broker 
AMQP layers
 Key: QPID-7283
 URL: https://issues.apache.org/jira/browse/QPID-7283
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Reporter: Alex Rudyy


At the moment SASL authentication  uses SaslServer created with authentication 
provider and calls SaslServer directly to process client responses. We can 
encapsulate SaslServer server under special SASL authentication API and 
simplify the entire SASL negotiation. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Commented] (QPID-7118) Web Management Operator Dashboard

[Lorenz Quack (JIRA)]

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

Lorenz Quack commented on QPID-7118:


I don't see a reason for letting the user specify a limit rather than using a 
paginated gird with server-side pagination.

> Web Management Operator Dashboard
> -
>
> Key: QPID-7118
> URL: https://issues.apache.org/jira/browse/QPID-7118
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
>
> The operator UI is a proposed extension to the existing Web Management 
> Console.  It targets those in the Operator role.  These people are typically 
> concerned with monitoring a Qpid instance, rather than configuring.  This 
> features aims to put all the information that the Operator needs in order to 
> help to understand the health of the application.
> For the initial version, the dashboard be a single column of queries within a 
> tab.
> The user can populate a dashboard from a user's existing store queries or 
> other queries that are visible to him.  When adding a query to the dashboard, 
> the user can chose the refresh period and the query limit.  The user can 
> remove queries from the dashboard.  The user can also reorder queries on the 
> dashboard.
> There user will be able to have a single dashboard at broker level and a 
> dashboard at each virtualhost level.  Dashboards at virtualhost level will 
> automatically by replicated amongst the group.
> Later, the option will be added for multiple columns and other widget types 
> (charts etc).   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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