[jira] [Created] (QPIDJMS-183) JmsConnectionFactory cannot support setSSL and setSSLContext method in amqp 1.0
Steven created QPIDJMS-183: -- Summary: 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] (QPID-7281) Get the tests running on Windows
[ https://issues.apache.org/jira/browse/QPID-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303019#comment-15303019 ] ASF subversion and git services commented on QPID-7281: --- Commit 1745659 from [~justi9] in branch 'qpid/trunk' [ https://svn.apache.org/r1745659 ] QPID-7281: Prevent shlex.split from removing backslashes > 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] (QPID-7281) Get the tests running on Windows
[ https://issues.apache.org/jira/browse/QPID-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303016#comment-15303016 ] ASF subversion and git services commented on QPID-7281: --- Commit 1745657 from [~justi9] in branch 'qpid/trunk' [ https://svn.apache.org/r1745657 ] QPID-7281: Relocate the find_package invocation for python; use the resulting config to run the test-time dependency check > 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] [Created] (QPID-7281) Get the tests running on Windows
Justin Ross created QPID-7281: - Summary: 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 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] [Resolved] (QPIDJMS-177) Make the policy objects used in the client more extensable and give more control over their controlled behaviors
[ https://issues.apache.org/jira/browse/QPIDJMS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-177. -- Resolution: Fixed > Make the policy objects used in the client more extensable and give more > control over their controlled behaviors > - > > Key: QPIDJMS-177 > URL: https://issues.apache.org/jira/browse/QPIDJMS-177 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Affects Versions: 0.9.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.10.0 > > > 1. Enhance the various policy object in the client by making them interfaces > so that users can create their own custom policies more easily. > 2. Extract the current policies into a set of default implementations. > 3. Add some additional method hooks that allow the policies to be applied on > per destination basis, i.e. allow a prefetch policy to set the value for a > consumer based on it's destination 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
[jira] [Created] (DISPATCH-353) segfault in qd_entity_refresh_connection
Gordon Sim created DISPATCH-353:
---
Summary: 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
{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] [Resolved] (QPIDJMS-180) Add a JmsMessageIDPolicy that imrpoves the existing message ID type configuration
[ https://issues.apache.org/jira/browse/QPIDJMS-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-180. -- Resolution: Fixed > Add a JmsMessageIDPolicy that imrpoves the existing message ID type > configuration > - > > Key: QPIDJMS-180 > URL: https://issues.apache.org/jira/browse/QPIDJMS-180 > Project: Qpid JMS > Issue Type: Sub-task > Components: qpid-jms-client >Affects Versions: 0.9.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.10.0 > > > Add a new policy object JmsMessageIDPolicy that improves upon the existing > Message ID type configuration by allowing MessageProducer instances to be > configured with a Message ID Builder on a per destination basis or other > application specific criteria. -- 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-13) Submit patch to Proton for AMQP type support needed by ProtonPython shim
[
https://issues.apache.org/jira/browse/QPIDIT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302843#comment-15302843
]
Justin Ross commented on QPIDIT-13:
---
Found it: PROTON-1061
> Submit patch to Proton for AMQP type support needed by ProtonPython shim
>
>
> Key: QPIDIT-13
> URL: https://issues.apache.org/jira/browse/QPIDIT-13
> Project: Apache QPID IT
> Issue Type: Task
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> This is a tracker task, which will be considered completed when the patch
> referred to below is successfully submitted to the Proton project.
> The Proton Python binding needs to be patched with the file located in
> {{etc/proton-python-amqp-types.patch}} file in git before it can be used with
> the ProtonPython shims. This patch adds support for AMQP types not natively
> supported in Python, and allow a simple mechanism to force the use of a
> specific AMQP type.
> This patch needs to be proposed and submitted to the Qpid Proton sub-project.
--
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-13) Submit patch to Proton for AMQP type support needed by ProtonPython shim
[
https://issues.apache.org/jira/browse/QPIDIT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302808#comment-15302808
]
Justin Ross commented on QPIDIT-13:
---
Kim, just to confirm. This one is commited as well? Where's the QPID jira for
it?
> Submit patch to Proton for AMQP type support needed by ProtonPython shim
>
>
> Key: QPIDIT-13
> URL: https://issues.apache.org/jira/browse/QPIDIT-13
> Project: Apache QPID IT
> Issue Type: Task
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> This is a tracker task, which will be considered completed when the patch
> referred to below is successfully submitted to the Proton project.
> The Proton Python binding needs to be patched with the file located in
> {{etc/proton-python-amqp-types.patch}} file in git before it can be used with
> the ProtonPython shims. This patch adds support for AMQP types not natively
> supported in Python, and allow a simple mechanism to force the use of a
> specific AMQP type.
> This patch needs to be proposed and submitted to the Qpid Proton sub-project.
--
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] (QPIDIT-13) Submit patch to Proton for AMQP type support needed by ProtonPython shim
[
https://issues.apache.org/jira/browse/QPIDIT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-13.
Resolution: Fixed
Complete
> Submit patch to Proton for AMQP type support needed by ProtonPython shim
>
>
> Key: QPIDIT-13
> URL: https://issues.apache.org/jira/browse/QPIDIT-13
> Project: Apache QPID IT
> Issue Type: Task
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> This is a tracker task, which will be considered completed when the patch
> referred to below is successfully submitted to the Proton project.
> The Proton Python binding needs to be patched with the file located in
> {{etc/proton-python-amqp-types.patch}} file in git before it can be used with
> the ProtonPython shims. This patch adds support for AMQP types not natively
> supported in Python, and allow a simple mechanism to force the use of a
> specific AMQP type.
> This patch needs to be proposed and submitted to the Qpid Proton sub-project.
--
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] (QPIDIT-24) Broker identification failure blocks tests
[ https://issues.apache.org/jira/browse/QPIDIT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-24. Resolution: Fixed If the broker will not supply a broker name in the connection properties, then the name will default to "unknown". Tests will then run, and any tests that need to be skipped can be set to do so against this name (although it will only be valid for this broker - currently the Artemis broker falls into this category). > Broker identification failure blocks tests > -- > > Key: QPIDIT-24 > URL: https://issues.apache.org/jira/browse/QPIDIT-24 > Project: Apache QPID IT > Issue Type: Bug > Components: JmsMessageTest, SimpleTypeTest >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Both the AMQP type test and the JMS message test use a small Python script to > connect to the broker and retrieve the connection properties, among which are > the broker name and version. > The broker name is used to skip tests depending on the broker being used in > the test. The broker product name is used for this purpose. If the process > of retrieving the connection properties fails for any reason, then the test > does not run, but exits with an error message. This behavior needs to be > changed such that the test will run but no test skipping will take place. -- 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] (QPIDIT-25) Change shim architecture to accomodate non-queueing brokers
[ https://issues.apache.org/jira/browse/QPIDIT-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-25. Resolution: Not A Problem It seems that the Qpid dispatch router which was the center of this issue can now store messages, so this is no longer needed. > Change shim architecture to accomodate non-queueing brokers > --- > > Key: QPIDIT-25 > URL: https://issues.apache.org/jira/browse/QPIDIT-25 > Project: Apache QPID IT > Issue Type: Improvement > Components: Proton PythonShim, Qpid Jms Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Some brokers do not supply queuing capabilities. For such brokers, it is > necessary to first open a consumer or listener before sending test data. This > will allow messages to be buffered locally rather than on the broker. > Change the architecture of the shims such that the receiver is started first, > and then later processed for buffered messages. -- 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] (QPIDIT-21) Add shims for C++ client
[ https://issues.apache.org/jira/browse/QPIDIT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-21. Resolution: Fixed Shims for AMQP types and JMS messages complete. > 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] [Commented] (QPIDIT-33) Add JMS message properties to test suite
[ https://issues.apache.org/jira/browse/QPIDIT-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302735#comment-15302735 ] ASF subversion and git services commented on QPIDIT-33: --- Commit 422f55593a194c887eac6c659cb86d13039b7ee5 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=422f555 ] QPIDIT-33: WIP: Added JMS Message type (which has no body) to tests. Updates to QUICKSTART file. > Add JMS message properties to test suite > > > Key: QPIDIT-33 > URL: https://issues.apache.org/jira/browse/QPIDIT-33 > Project: Apache QPID IT > Issue Type: Improvement > Components: JmsMessageTest, Proton PythonShim, ProtonCppShim, Qpid > Jms Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Currently, the JMS message tests do not support message properties as a part > of the test, only message bodies are tested. This enhancement will add > combinations of message properties to the message bodies and check that these > are correctly sent and received. -- 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] (QPIDIT-21) Add shims for C++ client
[ https://issues.apache.org/jira/browse/QPIDIT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-21: --- Component/s: ProtonCppShim > 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] [Updated] (QPIDIT-33) Add JMS message properties to test suite
[ https://issues.apache.org/jira/browse/QPIDIT-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-33: --- Component/s: ProtonCppShim > Add JMS message properties to test suite > > > Key: QPIDIT-33 > URL: https://issues.apache.org/jira/browse/QPIDIT-33 > Project: Apache QPID IT > Issue Type: Improvement > Components: JmsMessageTest, Proton PythonShim, ProtonCppShim, Qpid > Jms Shim >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > Currently, the JMS message tests do not support message properties as a part > of the test, only message bodies are tested. This enhancement will add > combinations of message properties to the message bodies and check that these > are correctly sent and received. -- 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] (QPIDIT-33) Add JMS message properties to test suite
Kim van der Riet created QPIDIT-33: -- Summary: Add JMS message properties to test suite Key: QPIDIT-33 URL: https://issues.apache.org/jira/browse/QPIDIT-33 Project: Apache QPID IT Issue Type: Improvement Components: JmsMessageTest, Proton PythonShim, Qpid Jms Shim Reporter: Kim van der Riet Assignee: Kim van der Riet Currently, the JMS message tests do not support message properties as a part of the test, only message bodies are tested. This enhancement will add combinations of message properties to the message bodies and check that these are correctly sent and received. -- 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
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302388#comment-15302388 ] Ted Ross commented on DISPATCH-343: --- Your reproducer reproduces and we understand why the crash is occurring. We hope to have a fix today. > 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] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302363#comment-15302363 ] Vishal Sharda commented on DISPATCH-343: Ted, Do you have an ETA of the fix? > 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] [Updated] (QPID-7116) Ability to utilise group information from a LDAP compatible directory
[
https://issues.apache.org/jira/browse/QPID-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7116:
-
Attachment: ldap-auth-provider-changes.tar.gz
> 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
> Fix For: qpid-java-6.1
>
> Attachments: WIP-get-ldap-groups.diff,
> ldap-auth-provider-changes.tar.gz
>
>
> 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] [Updated] (PROTON-515) Port to OpenVMS
[ https://issues.apache.org/jira/browse/PROTON-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Soltys updated PROTON-515: Attachment: INSTALL.md Build instructions for proton-c on OpenVMS platform > Port to OpenVMS > --- > > Key: PROTON-515 > URL: https://issues.apache.org/jira/browse/PROTON-515 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Affects Versions: 0.11.1 > Environment: OpenVMS >Reporter: Tomas Soltys >Assignee: Andrew Stitcher > Labels: OpenVMS, patch > Attachments: > 0001-PROTON-515-Change-pn_handle_t-to-be-void-to-get-arou.patch, > CMakeLists.txt.patch, INSTALL.md, io.c.patch, pipe.c.patch > > > There is a need for proton-c port to OpenVMS platform. > To make proton-c functional on OpenVMS few changes in the source code are > required. > Here is list of files I have identified which require some attention: > proton-c/src/platform_fmt.h > proton-c/src/posix/driver.c > proton-c/src/object/object.c > proton-c/src/codec/codec.c -- 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-343) Router stops accepting connections after load from parallel senders
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-343: -- Fix Version/s: 0.6.0 > 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 >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] [Assigned] (DISPATCH-343) Router stops accepting connections after load from parallel senders
[ https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-343: - Assignee: Ted Ross > 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] [Updated] (DISPATCH-352) Crash with empty configuration file
[
https://issues.apache.org/jira/browse/DISPATCH-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-352:
Attachment: core.7166.backtrace
core.7166.bz2
> Crash with empty configuration file
> ---
>
> Key: DISPATCH-352
> URL: https://issues.apache.org/jira/browse/DISPATCH-352
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
> Environment: RHEL 6.8x
> Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly
> handle default values for host/addr."
>Reporter: Jiri Danek
> Attachments: core.7166.backtrace, core.7166.bz2
>
>
> {noformat}
> $ touch empty.conf
> $ local/sbin/qdrouterd -c empty.conf
> Thu May 26 13:34:19 2016 SERVER (info) Container Name: (null)
> Segmentation fault (core dumped)
> {noformat}
--
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-352) Crash with empty configuration file
Jiri Danek created DISPATCH-352:
---
Summary: Crash with empty configuration file
Key: DISPATCH-352
URL: https://issues.apache.org/jira/browse/DISPATCH-352
Project: Qpid Dispatch
Issue Type: Bug
Components: Router Node
Affects Versions: 0.6.0
Environment: RHEL 6.8x
Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly
handle default values for host/addr."
Reporter: Jiri Danek
{noformat}
$ touch empty.conf
$ local/sbin/qdrouterd -c empty.conf
Thu May 26 13:34:19 2016 SERVER (info) Container Name: (null)
Segmentation fault (core dumped)
{noformat}
--
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-351) Crash after a sequence of qdmanage operations creating and destroying listener and connector
[
https://issues.apache.org/jira/browse/DISPATCH-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301960#comment-15301960
]
Jiri Danek commented on DISPATCH-351:
-
{noformat}
$ bash commands.bash
+ qdmanage CREATE --type=connector --name=eaconn1 port=20021 host=0.0.0.0
{
"verifyHostName": true,
"stripAnnotations": "both",
"name": "eaconn1",
"allowRedirect": true,
"idleTimeoutSeconds": 16,
"maxFrameSize": 65536,
"host": "0.0.0.0",
"cost": 1,
"role": "normal",
"type": "org.apache.qpid.dispatch.connector",
"port": "20021",
"identity": "connector/0.0.0.0:20021:eaconn1",
"addr": "127.0.0.1"
}
+ qdmanage CREATE --type=listener --name=eaconn1 port=20021 host=0.0.0.0
BadRequestStatus: org.apache.qpid.dispatch.connector: Duplicate value 'eaconn1'
for unique attribute 'name'
+ qdmanage DELETE --type=connector --name=eaconn1
+ qdmanage CREATE --type=listener --name=eaconn1 port=20021 host=0.0.0.0
{
"stripAnnotations": "both",
"name": "eaconn1",
"requireSsl": false,
"idleTimeoutSeconds": 16,
"maxFrameSize": 16384,
"requireEncryption": false,
"host": "0.0.0.0",
"cost": 1,
"role": "normal",
"authenticatePeer": false,
"type": "org.apache.qpid.dispatch.listener",
"port": "20021",
"identity": "listener/0.0.0.0:20021:eaconn1",
"addr": "127.0.0.1"
}
+ qdmanage DELETE --type=listener --name=eaconn1
ConnectionException: Connection amqp://0.0.0.0:amqp/$management disconnected
{noformat}
> Crash after a sequence of qdmanage operations creating and destroying
> listener and connector
>
>
> Key: DISPATCH-351
> URL: https://issues.apache.org/jira/browse/DISPATCH-351
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
> Environment: RHEL 6.8x
> Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly
> handle default values for host/addr."
>Reporter: Jiri Danek
> Attachments: commands.bash, core.6635.backtrace, core.6635.bz2
>
>
> Start up {{qdrouterd}} with the default config and run the (uncommented)
> commands in {{commands.bash}}. Router crashes.
> {noformat}
> $ local/sbin/qdrouterd -c local/etc/qpid-dispatch/qdrouterd.conf
> Thu May 26 13:16:49 2016 SERVER (info) Container Name: Router.A
> Thu May 26 13:16:49 2016 ROUTER (info) Router started in Standalone mode
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) Router Core thread running.
> 0/Router.A
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> M/$management
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> L/$management
> Thu May 26 13:16:49 2016 AGENT (info) Activating management agent on
> $_management_internal
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> L/$_management_internal
> Thu May 26 13:16:49 2016 DISPLAYNAME (info) Activating DisplayNameService on
> $displayname
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> L/$displayname
> Thu May 26 13:16:49 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp
> proto=any role=normal
> Thu May 26 13:16:49 2016 POLICY (info) Policy configured maximumConnections:
> 0, policyFolder: '', access rules enabled: 'false'
> Thu May 26 13:16:49 2016 POLICY (info) Policy fallback defaultApplication is
> disabled
> Thu May 26 13:16:49 2016 SERVER (info) Operational, 4 Threads Running
> Thu May 26 13:16:58 2016 CONN_MGR (info) Configured Connector: 0.0.0.0:20021
> proto=any role=normal
> Thu May 26 13:16:59 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20021
> proto=any role=normal
> Thu May 26 13:16:59 2016 AGENT (error) Error dispatching
> Message(address=None, properties={'operation': 'CREATE', 'type':
> 'org.apache.qpid.dispatch.listener', 'name': 'eaconn1'}, body={'host':
> '0.0.0.0', 'type': 'org.apache.qpid.dispatch.listener', 'port': '20021',
> 'name': 'eaconn1'}, reply_to='amqp:/_topo/0/Router.A/temp.ozFLn7K3UkHpXm+',
> correlation_id=1L): org.apache.qpid.dispatch.connector: Duplicate value
> 'eaconn1' for unique attribute 'name'
> Traceback (most recent call last):
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 786, in receive
> status, body = self.handle(request)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 809, in handle
> return self.create(request)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 850, in create
> return (CREATED, self._create(attributes).attributes)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 825, in _create
>
[jira] [Updated] (DISPATCH-351) Crash after a sequence of qdmanage operations creating and destroying listener and connector
[
https://issues.apache.org/jira/browse/DISPATCH-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-351:
Description:
Start up {{qdrouterd}} with the default config and run the (uncommented)
commands in {{commands.bash}}. Router crashes.
{noformat}
$ local/sbin/qdrouterd -c local/etc/qpid-dispatch/qdrouterd.conf
Thu May 26 13:16:49 2016 SERVER (info) Container Name: Router.A
Thu May 26 13:16:49 2016 ROUTER (info) Router started in Standalone mode
Thu May 26 13:16:49 2016 ROUTER_CORE (info) Router Core thread running.
0/Router.A
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
M/$management
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$management
Thu May 26 13:16:49 2016 AGENT (info) Activating management agent on
$_management_internal
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$_management_internal
Thu May 26 13:16:49 2016 DISPLAYNAME (info) Activating DisplayNameService on
$displayname
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$displayname
Thu May 26 13:16:49 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp
proto=any role=normal
Thu May 26 13:16:49 2016 POLICY (info) Policy configured maximumConnections: 0,
policyFolder: '', access rules enabled: 'false'
Thu May 26 13:16:49 2016 POLICY (info) Policy fallback defaultApplication is
disabled
Thu May 26 13:16:49 2016 SERVER (info) Operational, 4 Threads Running
Thu May 26 13:16:58 2016 CONN_MGR (info) Configured Connector: 0.0.0.0:20021
proto=any role=normal
Thu May 26 13:16:59 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20021
proto=any role=normal
Thu May 26 13:16:59 2016 AGENT (error) Error dispatching Message(address=None,
properties={'operation': 'CREATE', 'type': 'org.apache.qpid.dispatch.listener',
'name': 'eaconn1'}, body={'host': '0.0.0.0', 'type':
'org.apache.qpid.dispatch.listener', 'port': '20021', 'name': 'eaconn1'},
reply_to='amqp:/_topo/0/Router.A/temp.ozFLn7K3UkHpXm+', correlation_id=1L):
org.apache.qpid.dispatch.connector: Duplicate value 'eaconn1' for unique
attribute 'name'
Traceback (most recent call last):
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 786, in receive
status, body = self.handle(request)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 809, in handle
return self.create(request)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 850, in create
return (CREATED, self._create(attributes).attributes)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 825, in _create
self.entities.add_implementation(cimplementation, entity)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 534, in add_implementation
self._add_implementation(implementation, adapter=adapter)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 531, in _add_implementation
self.add(adapter)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 520, in add
self.schema.validate_full(chain(iter([entity]), iter(self.entities)))
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/qdrouter.py",
line 59, in validate_full
super(QdSchema, self).validate_all(entities, **kwargs)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/schema.py",
line 597, in validate_all
check_singleton=check_singleton)
File "/home/vagrant/local/lib/qpid-dispatch/pytho
Thu May 26 13:16:59 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20021
proto=any role=normal
Thu May 26 13:16:59 2016 DRIVER (error) bind: Address already in use
Segmentation fault (core dumped)
{noformat}
was:
Start up {{qdrouterd}} with the default config and run the (uncommented)
commands in {{commands.bash}}. Router crashes.
{{noformat}}
$ local/sbin/qdrouterd -c local/etc/qpid-dispatch/qdrouterd.conf
Thu May 26 13:16:49 2016 SERVER (info) Container Name: Router.A
Thu May 26 13:16:49 2016 ROUTER (info) Router started in Standalone mode
Thu May 26 13:16:49 2016 ROUTER_CORE (info) Router Core thread running.
0/Router.A
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
M/$management
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$management
Thu May 26 13:16:49 2016 AGENT (info) Activating management agent on
$_management_internal
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$_management_internal
Thu May 26 13:16:49 2016 DISPLAYNAME (info) Activating DisplayNameService on
$displayname
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process
[jira] [Created] (DISPATCH-351) Crash after a sequence of qdmanage operations creating and destroying listener and connector
Jiri Danek created DISPATCH-351:
---
Summary: Crash after a sequence of qdmanage operations creating
and destroying listener and connector
Key: DISPATCH-351
URL: https://issues.apache.org/jira/browse/DISPATCH-351
Project: Qpid Dispatch
Issue Type: Bug
Components: Router Node
Affects Versions: 0.6.0
Environment: RHEL 6.8x
Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly
handle default values for host/addr."
Reporter: Jiri Danek
Attachments: commands.bash, core.6635.backtrace, core.6635.bz2
Start up {{qdrouterd}} with the default config and run the (uncommented)
commands in {{commands.bash}}. Router crashes.
{{noformat}}
$ local/sbin/qdrouterd -c local/etc/qpid-dispatch/qdrouterd.conf
Thu May 26 13:16:49 2016 SERVER (info) Container Name: Router.A
Thu May 26 13:16:49 2016 ROUTER (info) Router started in Standalone mode
Thu May 26 13:16:49 2016 ROUTER_CORE (info) Router Core thread running.
0/Router.A
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
M/$management
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$management
Thu May 26 13:16:49 2016 AGENT (info) Activating management agent on
$_management_internal
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$_management_internal
Thu May 26 13:16:49 2016 DISPLAYNAME (info) Activating DisplayNameService on
$displayname
Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
L/$displayname
Thu May 26 13:16:49 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp
proto=any role=normal
Thu May 26 13:16:49 2016 POLICY (info) Policy configured maximumConnections: 0,
policyFolder: '', access rules enabled: 'false'
Thu May 26 13:16:49 2016 POLICY (info) Policy fallback defaultApplication is
disabled
Thu May 26 13:16:49 2016 SERVER (info) Operational, 4 Threads Running
Thu May 26 13:16:58 2016 CONN_MGR (info) Configured Connector: 0.0.0.0:20021
proto=any role=normal
Thu May 26 13:16:59 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20021
proto=any role=normal
Thu May 26 13:16:59 2016 AGENT (error) Error dispatching Message(address=None,
properties={'operation': 'CREATE', 'type': 'org.apache.qpid.dispatch.listener',
'name': 'eaconn1'}, body={'host': '0.0.0.0', 'type':
'org.apache.qpid.dispatch.listener', 'port': '20021', 'name': 'eaconn1'},
reply_to='amqp:/_topo/0/Router.A/temp.ozFLn7K3UkHpXm+', correlation_id=1L):
org.apache.qpid.dispatch.connector: Duplicate value 'eaconn1' for unique
attribute 'name'
Traceback (most recent call last):
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 786, in receive
status, body = self.handle(request)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 809, in handle
return self.create(request)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 850, in create
return (CREATED, self._create(attributes).attributes)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 825, in _create
self.entities.add_implementation(cimplementation, entity)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 534, in add_implementation
self._add_implementation(implementation, adapter=adapter)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 531, in _add_implementation
self.add(adapter)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
line 520, in add
self.schema.validate_full(chain(iter([entity]), iter(self.entities)))
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/qdrouter.py",
line 59, in validate_full
super(QdSchema, self).validate_all(entities, **kwargs)
File
"/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/schema.py",
line 597, in validate_all
check_singleton=check_singleton)
File "/home/vagrant/local/lib/qpid-dispatch/pytho
Thu May 26 13:16:59 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20021
proto=any role=normal
Thu May 26 13:16:59 2016 DRIVER (error) bind: Address already in use
Segmentation fault (core dumped)
{{noformat}}
--
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-351) Crash after a sequence of qdmanage operations creating and destroying listener and connector
[
https://issues.apache.org/jira/browse/DISPATCH-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-351:
Attachment: core.6635.backtrace
core.6635.bz2
commands.bash
> Crash after a sequence of qdmanage operations creating and destroying
> listener and connector
>
>
> Key: DISPATCH-351
> URL: https://issues.apache.org/jira/browse/DISPATCH-351
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 0.6.0
> Environment: RHEL 6.8x
> Git tip at commit 87d0a406c6 "DISPATCH-339 - [From Ganesh Murthy] Properly
> handle default values for host/addr."
>Reporter: Jiri Danek
> Attachments: commands.bash, core.6635.backtrace, core.6635.bz2
>
>
> Start up {{qdrouterd}} with the default config and run the (uncommented)
> commands in {{commands.bash}}. Router crashes.
> {{noformat}}
> $ local/sbin/qdrouterd -c local/etc/qpid-dispatch/qdrouterd.conf
> Thu May 26 13:16:49 2016 SERVER (info) Container Name: Router.A
> Thu May 26 13:16:49 2016 ROUTER (info) Router started in Standalone mode
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) Router Core thread running.
> 0/Router.A
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> M/$management
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> L/$management
> Thu May 26 13:16:49 2016 AGENT (info) Activating management agent on
> $_management_internal
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> L/$_management_internal
> Thu May 26 13:16:49 2016 DISPLAYNAME (info) Activating DisplayNameService on
> $displayname
> Thu May 26 13:16:49 2016 ROUTER_CORE (info) In-process subscription
> L/$displayname
> Thu May 26 13:16:49 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:amqp
> proto=any role=normal
> Thu May 26 13:16:49 2016 POLICY (info) Policy configured maximumConnections:
> 0, policyFolder: '', access rules enabled: 'false'
> Thu May 26 13:16:49 2016 POLICY (info) Policy fallback defaultApplication is
> disabled
> Thu May 26 13:16:49 2016 SERVER (info) Operational, 4 Threads Running
> Thu May 26 13:16:58 2016 CONN_MGR (info) Configured Connector: 0.0.0.0:20021
> proto=any role=normal
> Thu May 26 13:16:59 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20021
> proto=any role=normal
> Thu May 26 13:16:59 2016 AGENT (error) Error dispatching
> Message(address=None, properties={'operation': 'CREATE', 'type':
> 'org.apache.qpid.dispatch.listener', 'name': 'eaconn1'}, body={'host':
> '0.0.0.0', 'type': 'org.apache.qpid.dispatch.listener', 'port': '20021',
> 'name': 'eaconn1'}, reply_to='amqp:/_topo/0/Router.A/temp.ozFLn7K3UkHpXm+',
> correlation_id=1L): org.apache.qpid.dispatch.connector: Duplicate value
> 'eaconn1' for unique attribute 'name'
> Traceback (most recent call last):
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 786, in receive
> status, body = self.handle(request)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 809, in handle
> return self.create(request)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 850, in create
> return (CREATED, self._create(attributes).attributes)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 825, in _create
> self.entities.add_implementation(cimplementation, entity)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 534, in add_implementation
> self._add_implementation(implementation, adapter=adapter)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 531, in _add_implementation
> self.add(adapter)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/agent.py",
> line 520, in add
> self.schema.validate_full(chain(iter([entity]), iter(self.entities)))
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/qdrouter.py",
> line 59, in validate_full
> super(QdSchema, self).validate_all(entities, **kwargs)
> File
> "/home/vagrant/local/lib/qpid-dispatch/python/qpid_dispatch_internal/management/schema.py",
> line 597, in validate_all
> check_singleton=check_singleton)
> File "/home/vagrant/local/lib/qpid-dispatch/pytho
> Thu May 26 13:16:59 2016 CONN_MGR (info) Configured Listener: 0.0.0.0:20021
> proto=any role=normal
> Thu May 26 13:16:59 2016 DRIVER (error) bind: Address already in use
> Segmentation fault (core dumped)
>
[jira] [Created] (DISPATCH-350) Display list of links for client connections. Allow acquiesce of links
Ernest Allen created DISPATCH-350: - Summary: Display list of links for client connections. Allow acquiesce of links Key: DISPATCH-350 URL: https://issues.apache.org/jira/browse/DISPATCH-350 Project: Qpid Dispatch Issue Type: Improvement Components: Console Affects Versions: 0.7.0 Reporter: Ernest Allen Assignee: Ernest Allen On the topology page when a client is clicked, a list of links should be displayed. The link direction, admin state, owning address, delivery count, etc. should be shown. There should be an option to send a request to acquiesce any or all of the links for a connection. -- 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-349) Modify the client icon on the topology page to indicate when there are multiple clients.
Ernest Allen created DISPATCH-349: - Summary: Modify the client icon on the topology page to indicate when there are multiple clients. Key: DISPATCH-349 URL: https://issues.apache.org/jira/browse/DISPATCH-349 Project: Qpid Dispatch Issue Type: Improvement Components: Console Affects Versions: 0.7.0 Reporter: Ernest Allen Assignee: Ernest Allen Priority: Minor On the topology page there is an icon that represents a client that is connected to a router. When there are multiple clients, the icon should change to give a visual indication that it represents multiple 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] [Created] (DISPATCH-348) Don't show deprecated entities and attributes
Ernest Allen created DISPATCH-348: - Summary: Don't show deprecated entities and attributes Key: DISPATCH-348 URL: https://issues.apache.org/jira/browse/DISPATCH-348 Project: Qpid Dispatch Issue Type: Improvement Components: Console Affects Versions: 0.7.0 Reporter: Ernest Allen Assignee: Ernest Allen Priority: Minor Filter out deprecated items from the schema before using them in the UI. The schema page should still list them, but the other pages should not. It's confusing to see the old connection.addr on the create new connection form since users should only fill in the new connection.host field. This is true for all deprecated entities and attributes. -- 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
