[jira] [Commented] (PROTON-1179) [C++ binding] Rework condition class
[ https://issues.apache.org/jira/browse/PROTON-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251251#comment-15251251 ] ASF subversion and git services commented on PROTON-1179: - Commit 4971ac573f8532b57b342fcc47972d07d0f29ca7 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4971ac5 ] PROTON-1179: Fix error_condition close tests to compile with older Linux headers > [C++ binding] Rework condition class > > > Key: PROTON-1179 > URL: https://issues.apache.org/jira/browse/PROTON-1179 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > * Rename condition to error_condition > * rename info member to properties > * change it from a pure wrapper of pn_condition_t to be a value type. > ** privately constructed from a pn_condition_t > ** API constructed from name [description [properties] ] -- 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-1179) [C++ binding] Rework condition class
[ https://issues.apache.org/jira/browse/PROTON-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250992#comment-15250992 ] ASF subversion and git services commented on PROTON-1179: - Commit 13364ad50e1f276def4487d8f54d6486619ec785 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=13364ad ] PROTON-1180, PROTON-1179: Finish endpoint work, most of the condition work - Renamed condition -> error_condition - renamed all accessors for error_condition to error() - Made error_condition a value class holding the same information as the pn_condition_t it is made from. - Added close(const error_condition&) to endpoint - Enabled tests for endpoint::close(const error_condition&) x Can't yet set the properties on an error_condition in a close() > [C++ binding] Rework condition class > > > Key: PROTON-1179 > URL: https://issues.apache.org/jira/browse/PROTON-1179 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > * Rename condition to error_condition > * rename info member to properties > * change it from a pure wrapper of pn_condition_t to be a value type. > ** privately constructed from a pn_condition_t > ** API constructed from name [description [properties] ] -- 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-1180) [C++ binding] Change endpoint API
[ https://issues.apache.org/jira/browse/PROTON-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250991#comment-15250991 ] ASF subversion and git services commented on PROTON-1180: - Commit 13364ad50e1f276def4487d8f54d6486619ec785 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=13364ad ] PROTON-1180, PROTON-1179: Finish endpoint work, most of the condition work - Renamed condition -> error_condition - renamed all accessors for error_condition to error() - Made error_condition a value class holding the same information as the pn_condition_t it is made from. - Added close(const error_condition&) to endpoint - Enabled tests for endpoint::close(const error_condition&) x Can't yet set the properties on an error_condition in a close() > [C++ binding] Change endpoint API > - > > Key: PROTON-1180 > URL: https://issues.apache.org/jira/browse/PROTON-1180 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > * Rename remote_condition to condition; remove local_condition (the remote > state is authoritative) > * Add boolean accessors for uninitialized, active, and closed; remove > endpoint.state bit field > * Lift close operation to endpoint from its descendents > * Add new close operation with condition arg -- 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-1180) [C++ binding] Change endpoint API
[ https://issues.apache.org/jira/browse/PROTON-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250949#comment-15250949 ] ASF subversion and git services commented on PROTON-1180: - Commit f1e2428ba2da7fbaa311aea7c7d86fba9033dd7c in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f1e2428 ] PROTON-1180: [C++ binding] Modified endpoint changes: - Only have active() boolean - this is local_active - Removed remote_active() and changed all of it's uses in the code. > [C++ binding] Change endpoint API > - > > Key: PROTON-1180 > URL: https://issues.apache.org/jira/browse/PROTON-1180 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > > * Rename remote_condition to condition; remove local_condition (the remote > state is authoritative) > * Add boolean accessors for uninitialized, active, and closed; remove > endpoint.state bit field > * Lift close operation to endpoint from its descendents > * Add new close operation with condition arg -- 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-1181) [reactor] Use the host passed to pn_reactor_connection_to_host as default hostname for open frame
Ken Giusti created PROTON-1181: -- Summary: [reactor] Use the host passed to pn_reactor_connection_to_host as default hostname for open frame Key: PROTON-1181 URL: https://issues.apache.org/jira/browse/PROTON-1181 Project: Qpid Proton Issue Type: Bug Components: proton-c, proton-j, python-binding Affects Versions: 0.13.0 Reporter: Ken Giusti Fix For: 0.13.0 Modify the 'connection_to_host' reactor interface to use the passed host parameter as the default for the connection's hostname sent in the open frame. This should only be done if the host parameter is NOT a numerical IP address (do it for DNS-like names). Modify the pn_connection_set_hostname() to take a NULL argument so the default can be reset (e.g. no hostname in open frame). The default can be overridden by setting the desired hostname via the connection's set_hostname method. -- 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] (PROTON-1181) [reactor] Use the host passed to pn_reactor_connection_to_host as default hostname for open frame
[ https://issues.apache.org/jira/browse/PROTON-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-1181: -- Assignee: Ken Giusti > [reactor] Use the host passed to pn_reactor_connection_to_host as default > hostname for open frame > - > > Key: PROTON-1181 > URL: https://issues.apache.org/jira/browse/PROTON-1181 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c, proton-j, python-binding >Affects Versions: 0.13.0 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: 0.13.0 > > > Modify the 'connection_to_host' reactor interface to use the passed host > parameter as the default for the connection's hostname sent in the open frame. > This should only be done if the host parameter is NOT a numerical IP address > (do it for DNS-like names). > Modify the pn_connection_set_hostname() to take a NULL argument so the > default can be reset (e.g. no hostname in open frame). > The default can be overridden by setting the desired hostname via the > connection's set_hostname method. -- 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-288) Driver - Wakeup pipe was seen to block on read, deadlocking the driver.
[ https://issues.apache.org/jira/browse/DISPATCH-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250734#comment-15250734 ] Ted Ross commented on DISPATCH-288: --- The pipe established in the driver for waking up the poll loop is not set to non-blocking. I believe that poll reported a spurious POLLIN for this FD when there was no data to read. This occurred during heavy traffic over multiple connections. > Driver - Wakeup pipe was seen to block on read, deadlocking the driver. > --- > > Key: DISPATCH-288 > URL: https://issues.apache.org/jira/browse/DISPATCH-288 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.6 >Reporter: Ted Ross >Priority: Blocker > Fix For: 0.6 > > > # pstack 14448 > Thread 5 (Thread 0x7f2015792700 (LWP 14449)): > #0 0x7f202225a6d5 in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib64/libpthread.so.0 > #1 0x7f20226e6cbf in sys_cond_wait (cond=, > held_mutex=0x183f570) at > /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:107 > #2 0x7f20226f1d3d in router_core_thread (arg=0x1820ca0) at > /usr/src/debug/qpid-dispatch-0.6.0/src/router_core/router_core_thread.c:54 > #3 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 > #4 0x7f20217b21cd in clone () from /lib64/libc.so.6 > Thread 4 (Thread 0x7f2014b76700 (LWP 14450)): > #0 0x7f202225cf4d in __lll_lock_wait () from /lib64/libpthread.so.0 > #1 0x7f2022258d02 in _L_lock_791 () from /lib64/libpthread.so.0 > #2 0x7f2022258c08 in pthread_mutex_lock () from /lib64/libpthread.so.0 > #3 0x7f20226e6bb9 in sys_mutex_lock (mutex=0x19c9e00) at > /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:70 > #4 0x7f20226fa11e in thread_run (arg=) at > /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:992 > #5 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 > #6 0x7f20217b21cd in clone () from /lib64/libc.so.6 > Thread 3 (Thread 0x7f200700 (LWP 14451)): > #0 0x7f202225d22d in read () from /lib64/libpthread.so.0 > #1 0x7f20226e67fb in read (__nbytes=512, __buf=0x7f200fffe1a0, > __fd=) at /usr/include/bits/unistd.h:44 > #2 qdpn_driver_wait_3 (d=0x18695e0) at > /usr/src/debug/qpid-dispatch-0.6.0/src/posix/driver.c:956 > #3 0x7f20226f99af in thread_run (arg=) at > /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:875 > #4 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 > #5 0x7f20217b21cd in clone () from /lib64/libc.so.6 > Thread 2 (Thread 0x7f200f7fe700 (LWP 14452)): > #0 0x7f202225a6d5 in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib64/libpthread.so.0 > #1 0x7f20226e6cbf in sys_cond_wait (cond=, > held_mutex=0x19c9e00) at > /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:107 > #2 0x7f20226f9ddc in thread_run (arg=) at > /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:840 > #3 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 > #4 0x7f20217b21cd in clone () from /lib64/libc.so.6 > Thread 1 (Thread 0x7f2022b1c1c0 (LWP 14448)): > #0 0x7f202225cf4d in __lll_lock_wait () from /lib64/libpthread.so.0 > #1 0x7f2022258d02 in _L_lock_791 () from /lib64/libpthread.so.0 > #2 0x7f2022258c08 in pthread_mutex_lock () from /lib64/libpthread.so.0 > #3 0x7f20226e6bb9 in sys_mutex_lock (mutex=0x19c9e00) at > /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:70 > #4 0x7f20226fa11e in thread_run (arg=) at > /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:992 > #5 0x7f20226fa630 in qd_server_run (qd=0x1516030) at > /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:1349 > #6 0x00401b38 in main_process > (config_path=config_path@entry=0x7ffd13763f2d > "/etc/qpid-dispatch/qdrouterd.conf", > python_pkgdir=python_pkgdir@entry=0x402261 "/usr/lib/qpid-dispatch/python", > fd=fd@entry=2) at /usr/src/debug/qpid-dispatch-0.6.0/router/src/main.c:135 > #7 0x004017b0 in main (argc=3, argv=0x7ffd13762338) at > /usr/src/debug/qpid-dispatch-0.6.0/router/src/main.c:335 -- 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-288) Driver - Wakeup pipe was seen to block on read, deadlocking the driver.
Ted Ross created DISPATCH-288: - Summary: Driver - Wakeup pipe was seen to block on read, deadlocking the driver. Key: DISPATCH-288 URL: https://issues.apache.org/jira/browse/DISPATCH-288 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 0.6 Reporter: Ted Ross Priority: Blocker Fix For: 0.6 # pstack 14448 Thread 5 (Thread 0x7f2015792700 (LWP 14449)): #0 0x7f202225a6d5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f20226e6cbf in sys_cond_wait (cond=, held_mutex=0x183f570) at /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:107 #2 0x7f20226f1d3d in router_core_thread (arg=0x1820ca0) at /usr/src/debug/qpid-dispatch-0.6.0/src/router_core/router_core_thread.c:54 #3 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 #4 0x7f20217b21cd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f2014b76700 (LWP 14450)): #0 0x7f202225cf4d in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x7f2022258d02 in _L_lock_791 () from /lib64/libpthread.so.0 #2 0x7f2022258c08 in pthread_mutex_lock () from /lib64/libpthread.so.0 #3 0x7f20226e6bb9 in sys_mutex_lock (mutex=0x19c9e00) at /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:70 #4 0x7f20226fa11e in thread_run (arg=) at /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:992 #5 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 #6 0x7f20217b21cd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f200700 (LWP 14451)): #0 0x7f202225d22d in read () from /lib64/libpthread.so.0 #1 0x7f20226e67fb in read (__nbytes=512, __buf=0x7f200fffe1a0, __fd=) at /usr/include/bits/unistd.h:44 #2 qdpn_driver_wait_3 (d=0x18695e0) at /usr/src/debug/qpid-dispatch-0.6.0/src/posix/driver.c:956 #3 0x7f20226f99af in thread_run (arg=) at /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:875 #4 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 #5 0x7f20217b21cd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f200f7fe700 (LWP 14452)): #0 0x7f202225a6d5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f20226e6cbf in sys_cond_wait (cond=, held_mutex=0x19c9e00) at /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:107 #2 0x7f20226f9ddc in thread_run (arg=) at /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:840 #3 0x7f2022256dc5 in start_thread () from /lib64/libpthread.so.0 #4 0x7f20217b21cd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2022b1c1c0 (LWP 14448)): #0 0x7f202225cf4d in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x7f2022258d02 in _L_lock_791 () from /lib64/libpthread.so.0 #2 0x7f2022258c08 in pthread_mutex_lock () from /lib64/libpthread.so.0 #3 0x7f20226e6bb9 in sys_mutex_lock (mutex=0x19c9e00) at /usr/src/debug/qpid-dispatch-0.6.0/src/posix/threading.c:70 #4 0x7f20226fa11e in thread_run (arg=) at /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:992 #5 0x7f20226fa630 in qd_server_run (qd=0x1516030) at /usr/src/debug/qpid-dispatch-0.6.0/src/server.c:1349 #6 0x00401b38 in main_process (config_path=config_path@entry=0x7ffd13763f2d "/etc/qpid-dispatch/qdrouterd.conf", python_pkgdir=python_pkgdir@entry=0x402261 "/usr/lib/qpid-dispatch/python", fd=fd@entry=2) at /usr/src/debug/qpid-dispatch-0.6.0/router/src/main.c:135 #7 0x004017b0 in main (argc=3, argv=0x7ffd13762338) at /usr/src/debug/qpid-dispatch-0.6.0/router/src/main.c:335 -- 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-287) Policy does not allow configuration for unspecified Open hostname
Chuck Rolke created DISPATCH-287: Summary: Policy does not allow configuration for unspecified Open hostname Key: DISPATCH-287 URL: https://issues.apache.org/jira/browse/DISPATCH-287 Project: Qpid Dispatch Issue Type: Bug Components: Policy Engine Affects Versions: 0.6 Reporter: Chuck Rolke Currently if the hostname is blank when policy is in force then the connection is automatically disallowed. An improvement in this case would be to allow for some policy to be assigned. Policy is normally assigned based on the incoming connection's (username, client-host-ip, Open.hostname) tuple. This issue could be solved by allowing for blank Open.hostname in the policy definitions and run time. -- 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] (DISPATCH-283) Start the overview page with the Router tree node expanded
[ https://issues.apache.org/jira/browse/DISPATCH-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-283. --- Resolution: Fixed Fix Version/s: 0.6 > Start the overview page with the Router tree node expanded > -- > > Key: DISPATCH-283 > URL: https://issues.apache.org/jira/browse/DISPATCH-283 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > Fix For: 0.6 > > > When the overview page is first displayed, the Routers tree node on the left > should be expanded and show the list of routers. -- 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-283) Start the overview page with the Router tree node expanded
[ https://issues.apache.org/jira/browse/DISPATCH-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250446#comment-15250446 ] ASF subversion and git services commented on DISPATCH-283: -- Commit 20a43f75c0a7226a4439aca3af9a0955ee353728 in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=20a43f7 ] DISPATCH-283: Fix typo that was preventing router nodes from being expanded in the tree > Start the overview page with the Router tree node expanded > -- > > Key: DISPATCH-283 > URL: https://issues.apache.org/jira/browse/DISPATCH-283 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > > When the overview page is first displayed, the Routers tree node on the left > should be expanded and show the list of routers. -- 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] (DISPATCH-282) Prevent topology updates when adding a new router node
[ https://issues.apache.org/jira/browse/DISPATCH-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-282. --- Resolution: Fixed Fix Version/s: 0.6 > Prevent topology updates when adding a new router node > -- > > Key: DISPATCH-282 > URL: https://issues.apache.org/jira/browse/DISPATCH-282 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > Fix For: 0.6 > > > When in the 'Add new router' mode, the topology page will reset if the > underlying topology changes. This causes all work on the new node to be lost. > When filling out the forms to add a new node, prevent the svg from updating. -- 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-282) Prevent topology updates when adding a new router node
[ https://issues.apache.org/jira/browse/DISPATCH-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250382#comment-15250382 ] ASF subversion and git services commented on DISPATCH-282: -- Commit c2ee7cb56b4424c2b675996815eaa31207366ef2 in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=c2ee7cb ] DISPATCH-282: Don't update topology when in 'Add' mode > Prevent topology updates when adding a new router node > -- > > Key: DISPATCH-282 > URL: https://issues.apache.org/jira/browse/DISPATCH-282 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > > When in the 'Add new router' mode, the topology page will reset if the > underlying topology changes. This causes all work on the new node to be lost. > When filling out the forms to add a new node, prevent the svg from updating. -- 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-282) Prevent topology updates when adding a new router node
[ https://issues.apache.org/jira/browse/DISPATCH-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250381#comment-15250381 ] ASF subversion and git services commented on DISPATCH-282: -- Commit fcd0bdf4c63c23203aef72f3960aa3cc246a51ca in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=fcd0bdf ] DISPATCH-282: Defer topology updates when adding a new node on topology page > Prevent topology updates when adding a new router node > -- > > Key: DISPATCH-282 > URL: https://issues.apache.org/jira/browse/DISPATCH-282 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.6 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > > When in the 'Add new router' mode, the topology page will reset if the > underlying topology changes. This causes all work on the new node to be lost. > When filling out the forms to add a new node, prevent the svg from updating. -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7206. -- Resolution: Fixed The changes look good to me > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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] (DISPATCH-286) Prefix delimiters: allow slashes as well as periods
[ https://issues.apache.org/jira/browse/DISPATCH-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-286. --- Resolution: Fixed > Prefix delimiters: allow slashes as well as periods > > > Key: DISPATCH-286 > URL: https://issues.apache.org/jira/browse/DISPATCH-286 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.6 > > > In 0.6.0-beta2, the only delimiter character available for address prefixes > is the "." character. It would be desirable to also allow slash (and > possibly backslash) as well. -- 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-286) Prefix delimiters: allow slashes as well as periods
[ https://issues.apache.org/jira/browse/DISPATCH-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250207#comment-15250207 ] ASF subversion and git services commented on DISPATCH-286: -- Commit 7eea3ff37e250eefe5cc29cf69137427f310c9f7 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7eea3ff ] DISPATCH-286 - Add delimiter support for slash and backslash in hash-prefix lookups. > Prefix delimiters: allow slashes as well as periods > > > Key: DISPATCH-286 > URL: https://issues.apache.org/jira/browse/DISPATCH-286 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.6 > > > In 0.6.0-beta2, the only delimiter character available for address prefixes > is the "." character. It would be desirable to also allow slash (and > possibly backslash) as well. -- 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-6983) [Web Management Console] Add UI support for queries
[ https://issues.apache.org/jira/browse/QPID-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250069#comment-15250069 ] ASF subversion and git services commented on QPID-6983: --- Commit 1740154 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1740154 ] QPID-6983: Fix criteria conjunction in WhereCriteria widget > [Web Management Console] Add UI support for queries > --- > > Key: QPID-6983 > URL: https://issues.apache.org/jira/browse/QPID-6983 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz > > > Add the ability to the Web Management Console to submit queries (using the > feature added by QPID-6969) and view the results. The results may need to be > paginated for display. -- 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-6983) [Web Management Console] Add UI support for queries
[ https://issues.apache.org/jira/browse/QPID-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-6983. > [Web Management Console] Add UI support for queries > --- > > Key: QPID-6983 > URL: https://issues.apache.org/jira/browse/QPID-6983 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz > > > Add the ability to the Web Management Console to submit queries (using the > feature added by QPID-6969) and view the results. The results may need to be > paginated for display. -- 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-6983) [Web Management Console] Add UI support for queries
[ https://issues.apache.org/jira/browse/QPID-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250061#comment-15250061 ] Keith Wall commented on QPID-6983: -- >From a user perspective, changes look good. > [Web Management Console] Add UI support for queries > --- > > Key: QPID-6983 > URL: https://issues.apache.org/jira/browse/QPID-6983 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz > > > Add the ability to the Web Management Console to submit queries (using the > feature added by QPID-6969) and view the results. The results may need to be > paginated for display. -- 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-6983) [Web Management Console] Add UI support for queries
[ https://issues.apache.org/jira/browse/QPID-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6983: - Fix Version/s: qpid-java-6.1 > [Web Management Console] Add UI support for queries > --- > > Key: QPID-6983 > URL: https://issues.apache.org/jira/browse/QPID-6983 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz > > > Add the ability to the Web Management Console to submit queries (using the > feature added by QPID-6969) and view the results. The results may need to be > paginated for display. -- 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-7174) [JavaBroker] Broker fails to open ManagedPeerCertificateTrustStore containing certificates added via port
[
https://issues.apache.org/jira/browse/QPID-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall closed QPID-7174.
Resolution: Fixed
Change looks reasonable to me.
> [JavaBroker] Broker fails to open ManagedPeerCertificateTrustStore containing
> certificates added via port
> -
>
> Key: QPID-7174
> URL: https://issues.apache.org/jira/browse/QPID-7174
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
> Attachments:
> QPID-7174-fix-conversion-of-certificates-represented-as-strings-in-PEM-format.diff
>
>
> After configuring of ManagedPeerCertificateTrustStore as port
> clientCertRecorder and capturing one or more certificates via open TLS
> connections, the following exception is reported on Broker restart:
> {noformat}
> ERROR [Broker-Config] (o.a.q.s.m.AbstractConfiguredObject) - Failed to open
> object with name 'managing'. Object will be put into ERROR state.
> java.lang.IllegalArgumentException: Cannot convert
> '[MIIC4TCCAkqgAwIBAgIFAKI1xCswDQYJKoZIhvcNAQEFBQAwQTELMAkGA1UEBhMCQ0ExEDAOBgNVBAgTB09udGFyaW8xDTALBgNVBAoTBEFDTUUxETAPBgNVBAMTCE15Um9vdENBMB4XDTE1MDMyMDAxMjEwNVoXDTIwMDMyMDAxMjEwNVowYTELMAkGA1UEBhMCQ0ExCzAJBgNVBAgTAk9OMRAwDgYDVQQHEwdUb3JvbnRvMQ0wCwYDVQQKEwRhY21lMQwwCgYDVQQLEwNhcnQxFjAUBgNVBAMMDWFwcDJAYWNtZS5vcmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCviLTH6Vl6gP3M6gmmm0sVlCcBFfo2czDTsr93D1cIQpnyY1r3znBdFT3cbXE2LtHeLpnlXc+dTo9/aoUuBCzRIpi4CeaGgD3ggIl9Ws5hUgfxJCWBg7nhzMUlBC2C+VgIUHWHqGPuaQ7VzXOEC7xF0mihMZ4bwvU6wxGK2uUoruXE/iti/+jtzxjq0PO7ZgJ7GUI2ZDqGMad5OnLur8jz+yKsVdetXlXsOyHmHi/47pRuA115pYiIaZKu1+vs6IBl4HnEUgw5JwIww6oyTDVvXc1kCw0QCtUZMcNSH2XGhh/zGM/M2Bt2lgEEW0xWTwQcT1J7wnngfbIYbzoupEkRAgMBAAGjQTA/MB0GA1UdDgQWBBRI+VUMRkfNYp/xngM9y720hvxmXTAJBgNVHRMEAjAAMBMGA1UdJQQMMAoGCCsGAQUFBwMCMA0GCSqGSIb3DQEBBQUAA4GBAJnedohhbqoY7O6oAm+hPScBCng/fl0erVjexL9W8l8g5NvIGgioUfjUDvGOnwB5LOoTnZUCRaLFhQFcGFMIjdHpg0qt/QkEFX/0m+849RK6muHT1CNlcXtCFXwPTJ+9h+1auTP+Yp/6ii9SU3W1dzYawy2p9IhkMZEpJaHCLnaC]'
> into a java.util.List for attribute
> storedCertificates (java.security.cert.CertificateException: Could not parse
> certificate: java.io.IOException: Empty input)
> at
> org.apache.qpid.server.model.ConfiguredObjectMethodAttribute.convert(ConfiguredObjectMethodAttribute.java:72)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.automatedSetValue(AbstractConfiguredObject.java:415)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.resolveAutomatedAttribute(AbstractConfiguredObject.java:1259)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.onResolve(AbstractConfiguredObject.java:1213)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doResolution(AbstractConfiguredObject.java:1025)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$11.performAction(AbstractConfiguredObject.java:1037)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.applyToChildren(AbstractConfiguredObject.java:1095)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doResolution(AbstractConfiguredObject.java:1027)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:510)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:500)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:561)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:554)
> [classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> [classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:154)
> [classes/:na]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:142)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doOnConfigThread(AbstractConfiguredObject.java:553)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.openAsync(AbstractConfiguredObject.java:499)
> [classes/:na]
> at
> org.apache.qpid.server.model.AbstractSystemConfig.activate(AbstractSystemConfig.java:238)
> [classes/:na]
>
[jira] [Commented] (DISPATCH-286) Prefix delimiters: allow slashes as well as periods
[ https://issues.apache.org/jira/browse/DISPATCH-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250030#comment-15250030 ] Ted Ross commented on DISPATCH-286: --- This is not so much a pattern-matching problem as it is a searching problem. We want to do an efficient search on an address such that the most specific matching prefix is returned. In this case, prefix is defined by segments delimited by delimiters. Currently the only delimiter is '.' but there's call for allowing '/' as well. The use of delimiters is simply an optimization. If we didn't use them, we could search every prefix character-by-character. But this would be quite a bit slower. I don't think it is too steep of a slippery slope to add a delimiter character. Doing a full regex-search is a huge change and will have significant performance implications that we don't want to deal with. > Prefix delimiters: allow slashes as well as periods > > > Key: DISPATCH-286 > URL: https://issues.apache.org/jira/browse/DISPATCH-286 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.6 > > > In 0.6.0-beta2, the only delimiter character available for address prefixes > is the "." character. It would be desirable to also allow slash (and > possibly backslash) as well. -- 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-286) Prefix delimiters: allow slashes as well as periods
[ https://issues.apache.org/jira/browse/DISPATCH-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249976#comment-15249976 ] Alan Conway commented on DISPATCH-286: -- At this point you are really talking about pattern matching. Beware of starting a simplistic solution that becomes unmanageably complex as new requirements are added willy-nilly. I suggest an extensible set of pattern types, you already have 3 - slash-separated, dot-separated, backslash-separated. That way you can keep the efficiency of simple char separators for now, but you will be ready for the day when someone wants "::" as a separator - just add a new pattern type "double-colon-separated". You will also be ready if/when there is a need for regexps or other more powerful patterns. Finally you will have explicit annotations so you know which type of separator is required on a per-prefix basis. Also beware that you will need escape syntax for when the separator pattern is not being used as a separator. We already see this in proton with Azure topic names containing "/", which proton's URL parser treats as a URL separator. We need to use URL hex escapes to work around this, dispatch will have the same problem and need a similar solution. > Prefix delimiters: allow slashes as well as periods > > > Key: DISPATCH-286 > URL: https://issues.apache.org/jira/browse/DISPATCH-286 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross > Fix For: 0.6 > > > In 0.6.0-beta2, the only delimiter character available for address prefixes > is the "." character. It would be desirable to also allow slash (and > possibly backslash) as well. -- 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-286) Prefix delimiters: allow slashes as well as periods
Ted Ross created DISPATCH-286: - Summary: Prefix delimiters: allow slashes as well as periods Key: DISPATCH-286 URL: https://issues.apache.org/jira/browse/DISPATCH-286 Project: Qpid Dispatch Issue Type: Improvement Components: Router Node Reporter: Ted Ross Assignee: Ted Ross Fix For: 0.6 In 0.6.0-beta2, the only delimiter character available for address prefixes is the "." character. It would be desirable to also allow slash (and possibly backslash) as well. -- 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-6983) [Web Management Console] Add UI support for queries
[ https://issues.apache.org/jira/browse/QPID-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249873#comment-15249873 ] ASF subversion and git services commented on QPID-6983: --- Commit 1740144 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1740144 ] QPID-6983: Fix Query UI related issues: fix datetime expression generation for UTC timezone fix selection of columns in standard mode widget on changes to select in advanced mode display warning about limitations of copying expressions form Adv Mode into Std Mode on changes in both select and where widgets align mode switching button to the right > [Web Management Console] Add UI support for queries > --- > > Key: QPID-6983 > URL: https://issues.apache.org/jira/browse/QPID-6983 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: query-ui-prototype.tar.gz, query-ui-prototype.tar.gz > > > Add the ability to the Web Management Console to submit queries (using the > feature added by QPID-6969) and view the results. The results may need to be > paginated for display. -- 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-7205) [Java Broker] Query API returns empty strings for headers representing expressions like $parent.name etc
[ https://issues.apache.org/jira/browse/QPID-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7205. -- Resolution: Invalid Query API generates empty header when alias is not provided in the expression. It is an expected behavior. If non-empty header is required, the alias should be provided. More over header is merely a label for the column data and it is acceptable to have multiple duplicate headers. The client application calling Query API should not make any assumption on header presence or uniqueness of headers. Instead, it should operate with indexes to fetch column data. > [Java Broker] Query API returns empty strings for headers representing > expressions like $parent.name etc > > > Key: QPID-7205 > URL: https://issues.apache.org/jira/browse/QPID-7205 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Priority: Minor > > Query API returns empty strings for headers representing expressions like > $parent.name 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] [Updated] (QPID-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7206: - Assignee: Alex Rudyy (was: Keith Wall) > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249728#comment-15249728 ] ASF subversion and git services commented on QPID-7206: --- Commit 1740129 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1740129 ] QPID-7206: [Java Broker] Query API - ensure that IN expressions with numbers consider all items within the Set > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249698#comment-15249698 ] ASF subversion and git services commented on QPID-7206: --- Commit 1740122 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1740122 ] QPID-7206: [Java Broker] Query API - allow enums to appear in the set of an IN expression too > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249437#comment-15249437 ] ASF subversion and git services commented on QPID-7206: --- Commit 1740063 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1740063 ] QPID-7206: [Java Broker] Query API - support enums on RHS of expression too > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249373#comment-15249373 ] Rob Godfrey commented on QPID-7206: --- Do we not also need to consider the case where the enum is the right hand side and the left hand side is a string? > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7086) [Java Broker, Web Management Console] Add ability to set context variables
[ https://issues.apache.org/jira/browse/QPID-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-7086. Resolution: Fixed > [Java Broker, Web Management Console] Add ability to set context variables > -- > > Key: QPID-7086 > URL: https://issues.apache.org/jira/browse/QPID-7086 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > Attachments: WIP-Add-context-editor-to-auth-provider-ui.diff > > > Currently the Web Management Console support viewing/setting context > variables on a few selected objects (e.g., broker and VH). > It should be possible to view/set the context variables of all > ConfiguredObjects. > One place where this is currently an issue is Port where the UI does not > support context variables but we might want to selectively enable/disable TLS > protocols. -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249350#comment-15249350 ] Keith Wall commented on QPID-7206: -- Support added for enums within equals, in, and not equals expressions where the LHS is an attribute of an enumerated type. Inequalities (myEnumAttr > 'DOG') (using an enum's ordinal value) remain unsupported because I think an enum's ordinal value is not part of the public API. > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7206: - Status: Reviewable (was: In Progress) > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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] (QPID-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7206: Assignee: Keith Wall > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy >Assignee: Keith Wall > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7206: - Fix Version/s: qpid-java-6.1 > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7206: - Issue Type: New Feature (was: Bug) > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy > Fix For: qpid-java-6.1 > > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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-7206) [Java Broker] Query API does not support conditions with fileds of enum type
[ https://issues.apache.org/jira/browse/QPID-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15249342#comment-15249342 ] ASF subversion and git services commented on QPID-7206: --- Commit 1740056 from [~k-wall] in branch 'java/trunk' [ https://svn.apache.org/r1740056 ] QPID-7206: [Java Broker] Query API - add support for enums within expressions. > [Java Broker] Query API does not support conditions with fileds of enum type > > > Key: QPID-7206 > URL: https://issues.apache.org/jira/browse/QPID-7206 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Alex Rudyy > > Query API returns empty results if where expression contains a condition for > enum attribute, for example desiredState='ACTIVE' -- 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
