[jira] [Updated] (DISPATCH-890) Multi tenancy doesn't work over a websockets listener
[
https://issues.apache.org/jira/browse/DISPATCH-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-890:
--
Fix Version/s: 1.1.0
> Multi tenancy doesn't work over a websockets listener
> -
>
> Key: DISPATCH-890
> URL: https://issues.apache.org/jira/browse/DISPATCH-890
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
> Fix For: 1.1.0
>
>
> When a listener has http: true and multiTenant: true, the connection isn't
> multi-tenant
> - add bob.com to /etc/hosts and map to 127.0.0.1
> - setup listeners like:
> listener {
> host: bob.com
> port: 5674
> multiTenant: true
> http: true
> saslMechanisms: ANONYMOUS
> }
> listener {
> host: 0.0.0.0
> port: 5672
> role: normal
> saslMechanisms: ANONYMOUS
> }
> - serve the stand-alone console from http://bob.com:5674/
> - The console will connect to the router via bob.com:5674
> - qdstat -c or just use the console's Entities tab and look at the
> connections
> In theory, there should be a connection that has a tenant of bob.com, but
> there isn't.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-890) Multi tenancy doesn't work over a websockets listener
Ernest Allen created DISPATCH-890:
-
Summary: Multi tenancy doesn't work over a websockets listener
Key: DISPATCH-890
URL: https://issues.apache.org/jira/browse/DISPATCH-890
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 1.0.0
Reporter: Ernest Allen
When a listener has http: true and multiTenant: true, the connection isn't
multi-tenant
- add bob.com to /etc/hosts and map to 127.0.0.1
- setup listeners like:
listener {
host: bob.com
port: 5674
multiTenant: true
http: true
saslMechanisms: ANONYMOUS
}
listener {
host: 0.0.0.0
port: 5672
role: normal
saslMechanisms: ANONYMOUS
}
- serve the stand-alone console from http://bob.com:5674/
- The console will connect to the router via bob.com:5674
- qdstat -c or just use the console's Entities tab and look at the
connections
In theory, there should be a connection that has a tenant of bob.com, but there
isn't.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-874) unable to load .json or .woff2 files from local file system from http port
[ https://issues.apache.org/jira/browse/DISPATCH-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-874: -- Fix Version/s: 1.1.0 > unable to load .json or .woff2 files from local file system from http port > -- > > Key: DISPATCH-874 > URL: https://issues.apache.org/jira/browse/DISPATCH-874 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.8.0, 1.0.0 >Reporter: Ernest Allen >Assignee: Alan Conway > Fix For: 1.1.0 > > > When serving the console from a router with a listener that has http: true, > files with extensions of .json and .woff2 fail to load. > To reproduce: > - setup a router with an http listener (ie. on port 5673) > - load the console from a browser using that port (localhost:5673/) > - attempt to load the file localhost:5673/plugin/data/world-110m.json > What you get: > a 404 page > What you should get: > the contents of the file > Just to verify: > - copy a .js file to the plugin/data/ directory where the console is installed > - attempt to load localhost:5673/plugin/data/name_of_js_file.js > - you should see the .js file in the browser. It's just .json and .woff2 > files that won't load > - also to verify: if you load the console from an apache web server, the > plugin/data/world-110m.json loads just fine. > The .woff2 files are fonts. You can see that they fail to load in the > browser's debugging console -> Network tab. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1693) [ruby] Replace C-reactor based code with new Container
[ https://issues.apache.org/jira/browse/PROTON-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1693. - Resolution: Fixed Fix Version/s: proton-c-0.19.0 The later against 1064 should really be against this bug, they are very closely related. > [ruby] Replace C-reactor based code with new Container > -- > > Key: PROTON-1693 > URL: https://issues.apache.org/jira/browse/PROTON-1693 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: proton-c-0.19.0 > > > Remove the C reactor-based container and related code. > Replace with a backward-compatibility shim based on the new native Ruby > Container > Mark deprecated features in doc and with Kernel#warn [DEPRECATION] -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1654) Windows build does not compile the examples that require C++11
[ https://issues.apache.org/jira/browse/PROTON-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1654. - Resolution: Fixed > Windows build does not compile the examples that require C++11 > -- > > Key: PROTON-1654 > URL: https://issues.apache.org/jira/browse/PROTON-1654 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.19.0 > > > * scheduled_send > * multithreaded_client > * multithreaded_client_flow_control > Do not get built on Windows because C++11 examples are explicitly excluded > there. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1710) Proton C++ will crash if told to run 0 threads
[ https://issues.apache.org/jira/browse/PROTON-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1710. - Resolution: Fixed > Proton C++ will crash if told to run 0 threads > -- > > Key: PROTON-1710 > URL: https://issues.apache.org/jira/browse/PROTON-1710 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.19.0 > > > If you call container::run(0) - i.e. tell it to run 0 threads it will crash. > I think the correct thing to do here is just ignore all values less than 1 > and treat them as if they were 1. > Another possibility would be to treat 0 as a "default" value - and run a > "good" number of threads for the circumstances. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1707) Remove extraneous directories in C++ binding source
[ https://issues.apache.org/jira/browse/PROTON-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1707. - Resolution: Fixed > Remove extraneous directories in C++ binding source > --- > > Key: PROTON-1707 > URL: https://issues.apache.org/jira/browse/PROTON-1707 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.19.0 > > > The include and io directories in the C++ binding/src directory are > unnecessary -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-874) unable to load .json or .woff2 files from local file system from http port
[ https://issues.apache.org/jira/browse/DISPATCH-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277465#comment-16277465 ] ASF subversion and git services commented on DISPATCH-874: -- Commit 611f8b70628d65067129a639e8df693ecde8244a in qpid-dispatch's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=611f8b7 ] DISPATCH-874: allow .json and .woff2 files to be served by console. Added .json and .woff2 mime-types to the recognized list. Added a default rule to serve unrecognized files as "application/octet-stream" New file types required by the console should be added explicitly as browsers may restrict what can be done with application/octet-stream files. > unable to load .json or .woff2 files from local file system from http port > -- > > Key: DISPATCH-874 > URL: https://issues.apache.org/jira/browse/DISPATCH-874 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.8.0, 1.0.0 >Reporter: Ernest Allen >Assignee: Alan Conway > > When serving the console from a router with a listener that has http: true, > files with extensions of .json and .woff2 fail to load. > To reproduce: > - setup a router with an http listener (ie. on port 5673) > - load the console from a browser using that port (localhost:5673/) > - attempt to load the file localhost:5673/plugin/data/world-110m.json > What you get: > a 404 page > What you should get: > the contents of the file > Just to verify: > - copy a .js file to the plugin/data/ directory where the console is installed > - attempt to load localhost:5673/plugin/data/name_of_js_file.js > - you should see the .js file in the browser. It's just .json and .woff2 > files that won't load > - also to verify: if you load the console from an apache web server, the > plugin/data/world-110m.json loads just fine. > The .woff2 files are fonts. You can see that they fail to load in the > browser's debugging console -> Network tab. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-874) unable to load .json or .woff2 files from local file system from http port
[ https://issues.apache.org/jira/browse/DISPATCH-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved DISPATCH-874. -- Resolution: Fixed > unable to load .json or .woff2 files from local file system from http port > -- > > Key: DISPATCH-874 > URL: https://issues.apache.org/jira/browse/DISPATCH-874 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.8.0, 1.0.0 >Reporter: Ernest Allen >Assignee: Alan Conway > > When serving the console from a router with a listener that has http: true, > files with extensions of .json and .woff2 fail to load. > To reproduce: > - setup a router with an http listener (ie. on port 5673) > - load the console from a browser using that port (localhost:5673/) > - attempt to load the file localhost:5673/plugin/data/world-110m.json > What you get: > a 404 page > What you should get: > the contents of the file > Just to verify: > - copy a .js file to the plugin/data/ directory where the console is installed > - attempt to load localhost:5673/plugin/data/name_of_js_file.js > - you should see the .js file in the browser. It's just .json and .woff2 > files that won't load > - also to verify: if you load the console from an apache web server, the > plugin/data/world-110m.json loads just fine. > The .woff2 files are fonts. You can see that they fail to load in the > browser's debugging console -> Network tab. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-874) unable to load .json or .woff2 files from local file system from http port
[ https://issues.apache.org/jira/browse/DISPATCH-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned DISPATCH-874: Assignee: Alan Conway > unable to load .json or .woff2 files from local file system from http port > -- > > Key: DISPATCH-874 > URL: https://issues.apache.org/jira/browse/DISPATCH-874 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.8.0, 1.0.0 >Reporter: Ernest Allen >Assignee: Alan Conway > > When serving the console from a router with a listener that has http: true, > files with extensions of .json and .woff2 fail to load. > To reproduce: > - setup a router with an http listener (ie. on port 5673) > - load the console from a browser using that port (localhost:5673/) > - attempt to load the file localhost:5673/plugin/data/world-110m.json > What you get: > a 404 page > What you should get: > the contents of the file > Just to verify: > - copy a .js file to the plugin/data/ directory where the console is installed > - attempt to load localhost:5673/plugin/data/name_of_js_file.js > - you should see the .js file in the browser. It's just .json and .woff2 > files that won't load > - also to verify: if you load the console from an apache web server, the > plugin/data/world-110m.json loads just fine. > The .woff2 files are fonts. You can see that they fail to load in the > browser's debugging console -> Network tab. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1708) [proton-j] Improve performance of proton-j codec
[ https://issues.apache.org/jira/browse/PROTON-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277273#comment-16277273 ] ASF subversion and git services commented on PROTON-1708: - Commit 972dddc99f21eb70ce7cc371b2a50c9be260b18d in qpid-proton-j's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=972dddc ] PROTON-1708 Reduce overhead of reading zero sized values For types that carry no payload for the value, reduce the call tree by returing the type directly instead of looking up the encoding and calling into it for the default value. This also remove some auto-boxing that was being done in the readBoolean case for the decoder. > [proton-j] Improve performance of proton-j codec > > > Key: PROTON-1708 > URL: https://issues.apache.org/jira/browse/PROTON-1708 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.23.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: proton-j-0.24.0 > > > Several areas in the proton-j codec can be improved to provide overall > improvements in both the encode and decode of AMQP types as well as reduce GC > overhead with reduction in allocations of intermediate and helper objects. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1710) Proton C++ will crash if told to run 0 threads
[ https://issues.apache.org/jira/browse/PROTON-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277267#comment-16277267 ] ASF subversion and git services commented on PROTON-1710: - Commit 25025e9b3dee948f60656c88002a59be598a206d in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=25025e9 ] PROTON-1710: [C++ binding] Can't run container with less than 1 thread > Proton C++ will crash if told to run 0 threads > -- > > Key: PROTON-1710 > URL: https://issues.apache.org/jira/browse/PROTON-1710 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.19.0 > > > If you call container::run(0) - i.e. tell it to run 0 threads it will crash. > I think the correct thing to do here is just ignore all values less than 1 > and treat them as if they were 1. > Another possibility would be to treat 0 as a "default" value - and run a > "good" number of threads for the circumstances. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1707) Remove extraneous directories in C++ binding source
[ https://issues.apache.org/jira/browse/PROTON-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277265#comment-16277265 ] ASF subversion and git services commented on PROTON-1707: - Commit 5199e8c2abdb4cc0e42e4235dc44ed55dcd0abd9 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5199e8c ] PROTON-1707: [C++ binding] Simplify source directory structure - Remove pointless extra directories > Remove extraneous directories in C++ binding source > --- > > Key: PROTON-1707 > URL: https://issues.apache.org/jira/browse/PROTON-1707 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.19.0 > > > The include and io directories in the C++ binding/src directory are > unnecessary -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1654) Windows build does not compile the examples that require C++11
[ https://issues.apache.org/jira/browse/PROTON-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277266#comment-16277266 ] ASF subversion and git services commented on PROTON-1654: - Commit f88c826c62f7aa624e1388131f4042e88f6a32ff in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f88c826 ] PROTON-1654: [C++ binding] Improve turning C++ features on/off - Specifically for gcc 4.4 and Visual Studio compilers where this is a problem > Windows build does not compile the examples that require C++11 > -- > > Key: PROTON-1654 > URL: https://issues.apache.org/jira/browse/PROTON-1654 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.19.0 > > > * scheduled_send > * multithreaded_client > * multithreaded_client_flow_control > Do not get built on Windows because C++11 examples are explicitly excluded > there. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1710) Proton C++ will crash if told to run 0 threads
Andrew Stitcher created PROTON-1710: --- Summary: Proton C++ will crash if told to run 0 threads Key: PROTON-1710 URL: https://issues.apache.org/jira/browse/PROTON-1710 Project: Qpid Proton Issue Type: Bug Components: cpp-binding Affects Versions: proton-c-0.18.0 Reporter: Andrew Stitcher Assignee: Andrew Stitcher Fix For: proton-c-0.19.0 If you call container::run(0) - i.e. tell it to run 0 threads it will crash. I think the correct thing to do here is just ignore all values less than 1 and treat them as if they were 1. Another possibility would be to treat 0 as a "default" value - and run a "good" number of threads for the circumstances. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-889) linkRoute patterns beginning with #/string match substrings after the /
[
https://issues.apache.org/jira/browse/DISPATCH-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277173#comment-16277173
]
ASF subversion and git services commented on DISPATCH-889:
--
Commit e531e1cff723702952836d369d5d731679f121b9 in qpid-dispatch's branch
refs/heads/master from Kenneth Giusti
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=e531e1c ]
DISPATCH-889: fix the parse tree token string comparison
> linkRoute patterns beginning with #/string match substrings after the /
>
>
> Key: DISPATCH-889
> URL: https://issues.apache.org/jira/browse/DISPATCH-889
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ken Giusti
> Fix For: 1.1.0
>
>
> linkRoutes with a pattern of #/policy match substrings of the word policy
> - 1. setup a router
> router {
> mode: standalone
> id: A
> }
> listener {
> host: 0.0.0.0
> port: 2
> role: normal
> saslMechanisms: ANONYMOUS
> }
> connector {
> name: policy-connector
> role: route-container
> host: 0.0.0.0
> port:
> saslMechanisms: ANONYMOUS
> }
> linkRoute {
>pattern: #/policy
>dir: in
> connection: policy-connector
> }
> - 2. start an acceptor on that host:port
> qpid-proton/examples/python/server_direct.py
> - 3. verify linkRoute is established
> qdstat -b 0.0.0.0:2 --linkroutes
> Link Routes
> address dir distrib status
> =
> #/policy in linkBalanced active
> - 4. send some messages through the router
> addresses that should match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/policy -m 1
> -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/ken-is-great/policy
> -m 1
> -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/policy -m 1
> -> message received at server_direct.py
> addresses that should not match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/a -m 1
> -> message NOT sent - this is the correct behavior
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/p -m 1
> -> message received at server_direct.py - this is a bug
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/poli -m 1
> -> message received at server_direct.py - this is a bug
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-889) linkRoute patterns beginning with #/string match substrings after the /
[
https://issues.apache.org/jira/browse/DISPATCH-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved DISPATCH-889.
-
Resolution: Fixed
> linkRoute patterns beginning with #/string match substrings after the /
>
>
> Key: DISPATCH-889
> URL: https://issues.apache.org/jira/browse/DISPATCH-889
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ken Giusti
>
> linkRoutes with a pattern of #/policy match substrings of the word policy
> - 1. setup a router
> router {
> mode: standalone
> id: A
> }
> listener {
> host: 0.0.0.0
> port: 2
> role: normal
> saslMechanisms: ANONYMOUS
> }
> connector {
> name: policy-connector
> role: route-container
> host: 0.0.0.0
> port:
> saslMechanisms: ANONYMOUS
> }
> linkRoute {
>pattern: #/policy
>dir: in
> connection: policy-connector
> }
> - 2. start an acceptor on that host:port
> qpid-proton/examples/python/server_direct.py
> - 3. verify linkRoute is established
> qdstat -b 0.0.0.0:2 --linkroutes
> Link Routes
> address dir distrib status
> =
> #/policy in linkBalanced active
> - 4. send some messages through the router
> addresses that should match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/policy -m 1
> -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/ken-is-great/policy
> -m 1
> -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/policy -m 1
> -> message received at server_direct.py
> addresses that should not match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/a -m 1
> -> message NOT sent - this is the correct behavior
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/p -m 1
> -> message received at server_direct.py - this is a bug
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/poli -m 1
> -> message received at server_direct.py - this is a bug
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-889) linkRoute patterns beginning with #/string match substrings after the /
[
https://issues.apache.org/jira/browse/DISPATCH-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated DISPATCH-889:
Fix Version/s: 1.1.0
> linkRoute patterns beginning with #/string match substrings after the /
>
>
> Key: DISPATCH-889
> URL: https://issues.apache.org/jira/browse/DISPATCH-889
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ken Giusti
> Fix For: 1.1.0
>
>
> linkRoutes with a pattern of #/policy match substrings of the word policy
> - 1. setup a router
> router {
> mode: standalone
> id: A
> }
> listener {
> host: 0.0.0.0
> port: 2
> role: normal
> saslMechanisms: ANONYMOUS
> }
> connector {
> name: policy-connector
> role: route-container
> host: 0.0.0.0
> port:
> saslMechanisms: ANONYMOUS
> }
> linkRoute {
>pattern: #/policy
>dir: in
> connection: policy-connector
> }
> - 2. start an acceptor on that host:port
> qpid-proton/examples/python/server_direct.py
> - 3. verify linkRoute is established
> qdstat -b 0.0.0.0:2 --linkroutes
> Link Routes
> address dir distrib status
> =
> #/policy in linkBalanced active
> - 4. send some messages through the router
> addresses that should match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/policy -m 1
> -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/ken-is-great/policy
> -m 1
> -> message received at server_direct.py
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/policy -m 1
> -> message received at server_direct.py
> addresses that should not match
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/a -m 1
> -> message NOT sent - this is the correct behavior
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/p -m 1
> -> message received at server_direct.py - this is a bug
> qpid-proton/examples/python/simple_send -a 0.0.0.0:2/poli -m 1
> -> message received at server_direct.py - this is a bug
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests
[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277131#comment-16277131 ] ASF subversion and git services commented on QPID-6933: --- Commit 5b07dbf6bcda6ab306904cfdfb6d92e03c676133 in qpid-broker-j's branch refs/heads/master from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=5b07dbf ] QPID-6933: [System Tests] Add MaxDeliveryTest into JMS 1.1 system tests > Factor out a JMS client neutral messaging test suite from system tests > -- > > Key: QPID-6933 > URL: https://issues.apache.org/jira/browse/QPID-6933 > Project: Qpid > Issue Type: Improvement > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > > The existing system testsuite is in a poor state. > * It is poorly structured > * Mixes different types of test. i.e. messaging behaviour with those that > test features of the Java Broker (e.g. REST). > * Many of the tests refer directly to the implementation classes of the Qpid > Client 0-8..0-10 client meaning the tests cannot be run using the new client. > As a first step, we want to factor out a separate messaging system test suite: > * The tests in this suite will be JMS client neutral. > * Written in terms of JNDI/JMS client > * Configurations/Broker observations will be performed via a clean > Broker-neutral facade. For instance > ** a mechanism to cause the queue to be created of a particular type. > ** a mechanism to observe a queue depth. > * The tests will be classified by feature (to be defined) > * The classification system will be used to drive an exclusion feature (to be > defined). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1540) Add options to enable Sanitizers to CMake build
[ https://issues.apache.org/jira/browse/PROTON-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277031#comment-16277031 ] ASF subversion and git services commented on PROTON-1540: - Commit 25efd103a84a666c9da5e05cad5fbd2d12edf6f4 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=25efd10 ] PROTON-1540: [go] disabled race detection by default (again) NOTE: go test -race flag is not included by default, it causes problems on several platforms: - ubuntu up to trust: link errors - ubuntu from xenial: requires extra package golang-race-detector-runtime - fedora with gccgo: complains about "import cycles" (Works well on fedora with original go) Enable manually with -DGO_TEST_FLAGS="-v -race" > Add options to enable Sanitizers to CMake build > --- > > Key: PROTON-1540 > URL: https://issues.apache.org/jira/browse/PROTON-1540 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Reporter: Jiri Daněk >Assignee: Alan Conway >Priority: Minor > Labels: patch > Fix For: proton-c-0.18.0 > > > To get the most out of sanitizers in Qpid Dispatch, it helps to compile > Proton with sanitizers as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1705) [go] binding puts build artifacts in the source tree
[ https://issues.apache.org/jira/browse/PROTON-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276942#comment-16276942 ] ASF subversion and git services commented on PROTON-1705: - Commit 3fed547e3d4f5ffad4181f82e7b21c3599eb2ed7 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3fed547 ] PROTON-1705: [go] output to build tree, fix .gitignore and config.sh - remove .gitignore entries for Go output in source tree - fix config.sh GOPATH to point to build tree > [go] binding puts build artifacts in the source tree > > > Key: PROTON-1705 > URL: https://issues.apache.org/jira/browse/PROTON-1705 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Reporter: Alan Conway >Assignee: Alan Conway > > The Go build puts object files in the source tree which is bad practice and > causes confusion if artifacts are left behind. Make it do all its work in the > build tree. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-889) linkRoute patterns beginning with #/string match substrings after the /
Ernest Allen created DISPATCH-889:
-
Summary: linkRoute patterns beginning with #/string match
substrings after the /
Key: DISPATCH-889
URL: https://issues.apache.org/jira/browse/DISPATCH-889
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 1.0.0
Reporter: Ernest Allen
Assignee: Ken Giusti
linkRoutes with a pattern of #/policy match substrings of the word policy
- 1. setup a router
router {
mode: standalone
id: A
}
listener {
host: 0.0.0.0
port: 2
role: normal
saslMechanisms: ANONYMOUS
}
connector {
name: policy-connector
role: route-container
host: 0.0.0.0
port:
saslMechanisms: ANONYMOUS
}
linkRoute {
pattern: #/policy
dir: in
connection: policy-connector
}
- 2. start an acceptor on that host:port
qpid-proton/examples/python/server_direct.py
- 3. verify linkRoute is established
qdstat -b 0.0.0.0:2 --linkroutes
Link Routes
address dir distrib status
=
#/policy in linkBalanced active
- 4. send some messages through the router
addresses that should match
qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/policy -m 1
-> message received at server_direct.py
qpid-proton/examples/python/simple_send -a 0.0.0.0:2/ken-is-great/policy -m
1
-> message received at server_direct.py
qpid-proton/examples/python/simple_send -a 0.0.0.0:2/policy -m 1
-> message received at server_direct.py
addresses that should not match
qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/a -m 1
-> message NOT sent - this is the correct behavior
qpid-proton/examples/python/simple_send -a 0.0.0.0:2/bob.com/p -m 1
-> message received at server_direct.py - this is a bug
qpid-proton/examples/python/simple_send -a 0.0.0.0:2/poli -m 1
-> message received at server_direct.py - this is a bug
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-882) router buffers messages for slow presettled receiver
[ https://issues.apache.org/jira/browse/DISPATCH-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-882. - Resolution: Fixed > router buffers messages for slow presettled receiver > > > Key: DISPATCH-882 > URL: https://issues.apache.org/jira/browse/DISPATCH-882 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Gordon Sim >Assignee: Ken Giusti > Fix For: 1.1.0 > > > For an anycast address with incoming transfers unsettled and outgoing > transfers pre-settled, if the receiver can't keep up with the sender, the > router appears to buffer a growing number of deliveries. > The link stats for the receiver, which is receiving pre-settled, are shown as > accepted and unsettled (with a small number of undelivered) with presettled > count remaining at zero and the unsettled count growing. qpid-stat -m shows > growth in buffer and message content related types. > It looks like there is no limit to the amount of messages the router will try > to buffer in this case(?) though I did not push it all the way to failure. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8014) [Broker-J][WMC] Loading of WMC fails on systems with high CPU usage
[
https://issues.apache.org/jira/browse/QPID-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8014:
-
Fix Version/s: (was: qpid-java-broker-7.0.1)
qpid-java-broker-7.1.0
> [Broker-J][WMC] Loading of WMC fails on systems with high CPU usage
> ---
>
> Key: QPID-8014
> URL: https://issues.apache.org/jira/browse/QPID-8014
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Priority: Trivial
> Fix For: qpid-java-broker-7.1.0
>
> Attachments:
> 0001-QPID-8014-Broker-J-WMC-Make-sure-that-qpid-console-s.patch
>
>
> WMC fails to load on OS having CPU usage over 70%.
> The following error is reported in web browser web console
> {noformat}
> TypeError: controller.tabContainer is undefined
> Stack trace:
> @http://localhost:8080/js/qpid/management/controller.js:108:13
> .cache["dojo/ready"]/http://localhost:8080/dojo/dojo/dojo.js:8:98046
> .cache["dojo/ready"]/http://localhost:8080/dojo/dojo/dojo.js:8:97671
> req.signal/<@http://localhost:8080/dojo/dojo/dojo.js:8:3806
> _9@http://localhost:8080/dojo/dojo/dojo.js:8:328
> req.signal@http://localhost:8080/dojo/dojo/dojo.js:8:3771
> _38@http://localhost:8080/dojo/dojo/dojo.js:8:13709
> _81@http://localhost:8080/dojo/dojo/dojo.js:8:13758
> _33/_f6@http://localhost:8080/dojo/dojo/dojo.js:8:15537
> req.injectUrl/_10b@http://localhost:8080/dojo/dojo/dojo.js:8:18464
> xhr@http://localhost:8080/dojo/dojo/dojo.js:8:93734
> .cache["dojo/_base/xhr"]/http://localhost:8080/dojo/dojo/dojo.js:8:57975
> .cache["dojo/_base/xhr"]/http://localhost:8080/dojo/dojo/dojo.js:8:58333
> @http://localhost:8080/js/qpid/common/footer.js:26:1
> .cache["dojo/_base/array"]/http://localhost:8080/dojo/dojo/dojo.js:8:43572
> .cache["dojo/query"]/http://localhost:8080/dojo/dojo/dojo.js:8:140582
> @http://localhost:8080/js/qpid/common/footer.js:23:1
> _ce@http://localhost:8080/dojo/dojo/dojo.js:8:11945
> _37@http://localhost:8080/dojo/dojo/dojo.js:8:27097
> _37@http://localhost:8080/dojo/dojo/dojo.js:8:13438
> _81/<@http://localhost:8080/dojo/dojo/dojo.js:8:13833
> _38@http://localhost:8080/dojo/dojo/dojo.js:8:13659
> _81@http://localhost:8080/dojo/dojo/dojo.js:8:13758
> _33/_f6@http://localhost:8080/dojo/dojo/dojo.js:8:15537
> req.injectUrl/_10b@http://localhost:8080/dojo/dojo/dojo.js:8:18464
> {noformat}
> The issue was reproduced with the following:
> Firefox 45.8.0
> OS Windows 7.
> CPU usage 70%-90%
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7632) [AMQP 0-10] NPE from QueueQuery when queue argument omitted
[
https://issues.apache.org/jira/browse/QPID-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276770#comment-16276770
]
Keith Wall commented on QPID-7632:
--
I wonder if we should apply a similar annotation based idea like we did for
AMQP 1.0 in QPID7932?
> [AMQP 0-10] NPE from QueueQuery when queue argument omitted
> ---
>
> Key: QPID-7632
> URL: https://issues.apache.org/jira/browse/QPID-7632
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.1
>
>
> A client generated an illegal {{QueueQuery}} (null queue argument). This
> caused a NPE server side, and an {{INTERNAL_ERROR}} to be returned to the
> peer.
> An {{ILLEGAL_ARGUMENT}} or {{INVALID_ARGUMENT}} would have probably been more
> appropriate.
> This problem did not cause a server crash.
> {noformat}
> 017-01-19 17:01:40,459 DEBUG [IO-/127.0.0.1:56497] o.a.q.t.Connection
> RECV: [conn:3cd09483] ch=1 QueueQuery()
> 2017-01-19 17:01:40,460 DEBUG [IO-/127.0.0.1:56497] o.a.q.t.Session
> identify: ch=1, commandId=0
> 2017-01-19 17:01:40,471 ERROR [IO-/127.0.0.1:56497]
> o.a.q.s.p.v.ServerSessionDelegate Exception processing command
> java.lang.NullPointerException: null
> at
> java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
> ~[na:1.8.0_111]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getChildByName(AbstractConfiguredObject.java:2306)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getAttainedChildByName(AbstractConfiguredObject.java:2324)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.awaitChildClassToAttainState(AbstractConfiguredObject.java:3081)
> ~[classes/:na]
> at
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.getAttainedMessageSource(AbstractVirtualHost.java:1246)
> ~[classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.getMessageSource(ServerSessionDelegate.java:1458)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.queueQuery(ServerSessionDelegate.java:1667)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.queueQuery(ServerSessionDelegate.java:87)
> [classes/:na]
> at org.apache.qpid.transport.QueueQuery.dispatch(QueueQuery.java:87)
> [classes/:na]
> at
> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:57)
> ~[classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.command(ServerSessionDelegate.java:104)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.command(ServerSessionDelegate.java:87)
> [classes/:na]
> at org.apache.qpid.transport.Method.delegate(Method.java:153)
> [classes/:na]
> at org.apache.qpid.transport.Session.received(Session.java:582)
> [classes/:na]
> at org.apache.qpid.transport.Connection.dispatch(Connection.java:448)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:65)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:41)
> [classes/:na]
> at
> org.apache.qpid.transport.MethodDelegate.queueQuery(MethodDelegate.java:215)
> [classes/:na]
> at org.apache.qpid.transport.QueueQuery.dispatch(QueueQuery.java:87)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:55)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:41)
> [classes/:na]
> at org.apache.qpid.transport.Method.delegate(Method.java:153)
> [classes/:na]
> at org.apache.qpid.transport.Connection.received(Connection.java:401)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.access$001(ServerConnection.java:67)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection$2.run(ServerConnection.java:263)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection$2.run(ServerConnection.java:259)
> [classes/:na]
> at java.security.AccessController.doPrivileged(Native Method)
> [na:1.8.0_111]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.received(ServerConnection.java:258)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.emit(ServerAssembler.java:115)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.assemble(ServerAssembler.java:204)
> [classes/:na]
>
[jira] [Updated] (QPID-8044) [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0 vote
[
https://issues.apache.org/jira/browse/QPID-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8044:
-
Status: Open (was: Reviewable)
The binary bundle is not renamed. It is still named as
"apache-qpid-jms-0-x-${project.version}\-bin" but should be
"apache-qpid-jms-amqp-0-x-${project.version}\-bin"
> [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0 vote
> --
>
> Key: QPID-8044
> URL: https://issues.apache.org/jira/browse/QPID-8044
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
>Affects Versions: qpid-java-client-0-x-6.3.0
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Minor
> Fix For: qpid-java-client-0-x-6.3.1
>
>
> Robbie raised the following during the 6.3.0 vote:
> > Comments:
> > -The NOTICE file in the source release archive says Apache Qpid Java
> > and should be updated going forward.
> > -The slf4j-api details in the binary archive NOTICE can be removed
> > going forward as its covered by the details in the LICENCE file
> > already.
> > -The directories in all the archives dont match their file names (sans
> > extension), which seems like it was the intended name, e.g
> > apache-qpid-jms-0-x-6.3.0-src isn't aligned with
> > apache-qpid-jms-amqp-0-x-6.3.0-src.tar.gz
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7632) [AMQP 0-10] NPE from QueueQuery when queue argument omitted
[
https://issues.apache.org/jira/browse/QPID-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7632:
-
Fix Version/s: (was: Future)
qpid-java-broker-7.0.1
> [AMQP 0-10] NPE from QueueQuery when queue argument omitted
> ---
>
> Key: QPID-7632
> URL: https://issues.apache.org/jira/browse/QPID-7632
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
>
> A client generated an illegal {{QueueQuery}} (null queue argument). This
> caused a NPE server side, and an {{INTERNAL_ERROR}} to be returned to the
> peer.
> An {{ILLEGAL_ARGUMENT}} or {{INVALID_ARGUMENT}} would have probably been more
> appropriate.
> This problem did not cause a server crash.
> {noformat}
> 017-01-19 17:01:40,459 DEBUG [IO-/127.0.0.1:56497] o.a.q.t.Connection
> RECV: [conn:3cd09483] ch=1 QueueQuery()
> 2017-01-19 17:01:40,460 DEBUG [IO-/127.0.0.1:56497] o.a.q.t.Session
> identify: ch=1, commandId=0
> 2017-01-19 17:01:40,471 ERROR [IO-/127.0.0.1:56497]
> o.a.q.s.p.v.ServerSessionDelegate Exception processing command
> java.lang.NullPointerException: null
> at
> java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
> ~[na:1.8.0_111]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getChildByName(AbstractConfiguredObject.java:2306)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getAttainedChildByName(AbstractConfiguredObject.java:2324)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.awaitChildClassToAttainState(AbstractConfiguredObject.java:3081)
> ~[classes/:na]
> at
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.getAttainedMessageSource(AbstractVirtualHost.java:1246)
> ~[classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.getMessageSource(ServerSessionDelegate.java:1458)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.queueQuery(ServerSessionDelegate.java:1667)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.queueQuery(ServerSessionDelegate.java:87)
> [classes/:na]
> at org.apache.qpid.transport.QueueQuery.dispatch(QueueQuery.java:87)
> [classes/:na]
> at
> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:57)
> ~[classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.command(ServerSessionDelegate.java:104)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.command(ServerSessionDelegate.java:87)
> [classes/:na]
> at org.apache.qpid.transport.Method.delegate(Method.java:153)
> [classes/:na]
> at org.apache.qpid.transport.Session.received(Session.java:582)
> [classes/:na]
> at org.apache.qpid.transport.Connection.dispatch(Connection.java:448)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:65)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:41)
> [classes/:na]
> at
> org.apache.qpid.transport.MethodDelegate.queueQuery(MethodDelegate.java:215)
> [classes/:na]
> at org.apache.qpid.transport.QueueQuery.dispatch(QueueQuery.java:87)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:55)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:41)
> [classes/:na]
> at org.apache.qpid.transport.Method.delegate(Method.java:153)
> [classes/:na]
> at org.apache.qpid.transport.Connection.received(Connection.java:401)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.access$001(ServerConnection.java:67)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection$2.run(ServerConnection.java:263)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection$2.run(ServerConnection.java:259)
> [classes/:na]
> at java.security.AccessController.doPrivileged(Native Method)
> [na:1.8.0_111]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.received(ServerConnection.java:258)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.emit(ServerAssembler.java:115)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.assemble(ServerAssembler.java:204)
> [classes/:na]
> at
>
[jira] [Updated] (QPID-7632) [AMQP 0-10] NPE from QueueQuery when queue argument omitted
[
https://issues.apache.org/jira/browse/QPID-7632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7632:
-
Priority: Minor (was: Major)
> [AMQP 0-10] NPE from QueueQuery when queue argument omitted
> ---
>
> Key: QPID-7632
> URL: https://issues.apache.org/jira/browse/QPID-7632
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.1
>
>
> A client generated an illegal {{QueueQuery}} (null queue argument). This
> caused a NPE server side, and an {{INTERNAL_ERROR}} to be returned to the
> peer.
> An {{ILLEGAL_ARGUMENT}} or {{INVALID_ARGUMENT}} would have probably been more
> appropriate.
> This problem did not cause a server crash.
> {noformat}
> 017-01-19 17:01:40,459 DEBUG [IO-/127.0.0.1:56497] o.a.q.t.Connection
> RECV: [conn:3cd09483] ch=1 QueueQuery()
> 2017-01-19 17:01:40,460 DEBUG [IO-/127.0.0.1:56497] o.a.q.t.Session
> identify: ch=1, commandId=0
> 2017-01-19 17:01:40,471 ERROR [IO-/127.0.0.1:56497]
> o.a.q.s.p.v.ServerSessionDelegate Exception processing command
> java.lang.NullPointerException: null
> at
> java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
> ~[na:1.8.0_111]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getChildByName(AbstractConfiguredObject.java:2306)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getAttainedChildByName(AbstractConfiguredObject.java:2324)
> ~[classes/:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.awaitChildClassToAttainState(AbstractConfiguredObject.java:3081)
> ~[classes/:na]
> at
> org.apache.qpid.server.virtualhost.AbstractVirtualHost.getAttainedMessageSource(AbstractVirtualHost.java:1246)
> ~[classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.getMessageSource(ServerSessionDelegate.java:1458)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.queueQuery(ServerSessionDelegate.java:1667)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.queueQuery(ServerSessionDelegate.java:87)
> [classes/:na]
> at org.apache.qpid.transport.QueueQuery.dispatch(QueueQuery.java:87)
> [classes/:na]
> at
> org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:57)
> ~[classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.command(ServerSessionDelegate.java:104)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerSessionDelegate.command(ServerSessionDelegate.java:87)
> [classes/:na]
> at org.apache.qpid.transport.Method.delegate(Method.java:153)
> [classes/:na]
> at org.apache.qpid.transport.Session.received(Session.java:582)
> [classes/:na]
> at org.apache.qpid.transport.Connection.dispatch(Connection.java:448)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:65)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:41)
> [classes/:na]
> at
> org.apache.qpid.transport.MethodDelegate.queueQuery(MethodDelegate.java:215)
> [classes/:na]
> at org.apache.qpid.transport.QueueQuery.dispatch(QueueQuery.java:87)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:55)
> [classes/:na]
> at
> org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:41)
> [classes/:na]
> at org.apache.qpid.transport.Method.delegate(Method.java:153)
> [classes/:na]
> at org.apache.qpid.transport.Connection.received(Connection.java:401)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.access$001(ServerConnection.java:67)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection$2.run(ServerConnection.java:263)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection$2.run(ServerConnection.java:259)
> [classes/:na]
> at java.security.AccessController.doPrivileged(Native Method)
> [na:1.8.0_111]
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.received(ServerConnection.java:258)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.emit(ServerAssembler.java:115)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.assemble(ServerAssembler.java:204)
> [classes/:na]
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.frame(ServerAssembler.java:144)
>
[jira] [Updated] (QPID-8044) [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0 vote
[ https://issues.apache.org/jira/browse/QPID-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8044: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-x] Address minor packaging issues raised during 6.3.0 vote > -- > > Key: QPID-8044 > URL: https://issues.apache.org/jira/browse/QPID-8044 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 0-x >Affects Versions: qpid-java-client-0-x-6.3.0 >Reporter: Keith Wall >Assignee: Keith Wall >Priority: Minor > Fix For: qpid-java-client-0-x-6.3.1 > > > Robbie raised the following during the 6.3.0 vote: > > Comments: > > -The NOTICE file in the source release archive says Apache Qpid Java > > and should be updated going forward. > > -The slf4j-api details in the binary archive NOTICE can be removed > > going forward as its covered by the details in the LICENCE file > > already. > > -The directories in all the archives dont match their file names (sans > > extension), which seems like it was the intended name, e.g > > apache-qpid-jms-0-x-6.3.0-src isn't aligned with > > apache-qpid-jms-amqp-0-x-6.3.0-src.tar.gz -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7942) [Java Broker] AppenderUtilsTest does not work on Windows
[ https://issues.apache.org/jira/browse/QPID-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7942. -- Resolution: Fixed > [Java Broker] AppenderUtilsTest does not work on Windows > > > Key: QPID-7942 > URL: https://issues.apache.org/jira/browse/QPID-7942 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-broker-7.0.0 > > > AppenderUtilsTest fails if it is unable to change the permissions on a newly > created temporary director so that it is not writable. It seems that it is > not possible to do so in Windows (10). The inability to do so does not > reflect any error in the Qpid code (perhaps the test could try a different > mechanism for creating a directory that cannot be written to?) and so the > test should not fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7942) [Java Broker] AppenderUtilsTest does not work on Windows
[ https://issues.apache.org/jira/browse/QPID-7942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7942: - Fix Version/s: qpid-java-broker-7.0.0 > [Java Broker] AppenderUtilsTest does not work on Windows > > > Key: QPID-7942 > URL: https://issues.apache.org/jira/browse/QPID-7942 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-broker-7.0.0 > > > AppenderUtilsTest fails if it is unable to change the permissions on a newly > created temporary director so that it is not writable. It seems that it is > not possible to do so in Windows (10). The inability to do so does not > reflect any error in the Qpid code (perhaps the test could try a different > mechanism for creating a directory that cannot be written to?) and so the > test should not fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs
[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8025: - Fix Version/s: qpid-java-broker-7.0.1 > [Java Broker] Improve detach error message on unsubscribing from JMS shared > subs > > > Key: QPID-8025 > URL: https://issues.apache.org/jira/browse/QPID-8025 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Rob Godfrey > Fix For: qpid-java-broker-7.0.1 > > > On attempting to unsubscribe from a shared subscription, JMS requires an > error to occur if there exist active subscribers. The error message returned > by the broker in this case currently refers to the queue the broker generates > for the durable subscription, the name of which is in effect an > implementation artefact. > Since the particular implementation of shared subscriptions is essentially > JMS specific, it makes sense for the returned error message to be in terms of > the shared sub name, not the queue -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8026) [Java Broker] [AMQP 1.0] Add support for max-message-size on consumer attach
[ https://issues.apache.org/jira/browse/QPID-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8026: - Fix Version/s: qpid-java-broker-7.1.0 > [Java Broker] [AMQP 1.0] Add support for max-message-size on consumer attach > > > Key: QPID-8026 > URL: https://issues.apache.org/jira/browse/QPID-8026 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Rob Godfrey > Fix For: qpid-java-broker-7.1.0 > > > QPID-7957 added support for sending the max-message-size on producer attaches > *sent* to the broker, but there is currently no support in the broker for the > case where a consumer attaches a link which asserts that the consumer is > unable to receive messages above a certain size on that link. > In this case the consumer should, I think, behave as if a filter had been > applied which simply excludes from the possibility of delivery any message > which (when converted into an AMQP 1.0 payload) would be above the given size. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8014) [Broker-J][WMC] Loading of WMC fails on systems with high CPU usage
[
https://issues.apache.org/jira/browse/QPID-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8014:
-
Fix Version/s: qpid-java-broker-7.0.1
> [Broker-J][WMC] Loading of WMC fails on systems with high CPU usage
> ---
>
> Key: QPID-8014
> URL: https://issues.apache.org/jira/browse/QPID-8014
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
>Priority: Trivial
> Fix For: qpid-java-broker-7.0.1
>
> Attachments:
> 0001-QPID-8014-Broker-J-WMC-Make-sure-that-qpid-console-s.patch
>
>
> WMC fails to load on OS having CPU usage over 70%.
> The following error is reported in web browser web console
> {noformat}
> TypeError: controller.tabContainer is undefined
> Stack trace:
> @http://localhost:8080/js/qpid/management/controller.js:108:13
> .cache["dojo/ready"]/http://localhost:8080/dojo/dojo/dojo.js:8:98046
> .cache["dojo/ready"]/http://localhost:8080/dojo/dojo/dojo.js:8:97671
> req.signal/<@http://localhost:8080/dojo/dojo/dojo.js:8:3806
> _9@http://localhost:8080/dojo/dojo/dojo.js:8:328
> req.signal@http://localhost:8080/dojo/dojo/dojo.js:8:3771
> _38@http://localhost:8080/dojo/dojo/dojo.js:8:13709
> _81@http://localhost:8080/dojo/dojo/dojo.js:8:13758
> _33/_f6@http://localhost:8080/dojo/dojo/dojo.js:8:15537
> req.injectUrl/_10b@http://localhost:8080/dojo/dojo/dojo.js:8:18464
> xhr@http://localhost:8080/dojo/dojo/dojo.js:8:93734
> .cache["dojo/_base/xhr"]/http://localhost:8080/dojo/dojo/dojo.js:8:57975
> .cache["dojo/_base/xhr"]/http://localhost:8080/dojo/dojo/dojo.js:8:58333
> @http://localhost:8080/js/qpid/common/footer.js:26:1
> .cache["dojo/_base/array"]/http://localhost:8080/dojo/dojo/dojo.js:8:43572
> .cache["dojo/query"]/http://localhost:8080/dojo/dojo/dojo.js:8:140582
> @http://localhost:8080/js/qpid/common/footer.js:23:1
> _ce@http://localhost:8080/dojo/dojo/dojo.js:8:11945
> _37@http://localhost:8080/dojo/dojo/dojo.js:8:27097
> _37@http://localhost:8080/dojo/dojo/dojo.js:8:13438
> _81/<@http://localhost:8080/dojo/dojo/dojo.js:8:13833
> _38@http://localhost:8080/dojo/dojo/dojo.js:8:13659
> _81@http://localhost:8080/dojo/dojo/dojo.js:8:13758
> _33/_f6@http://localhost:8080/dojo/dojo/dojo.js:8:15537
> req.injectUrl/_10b@http://localhost:8080/dojo/dojo/dojo.js:8:18464
> {noformat}
> The issue was reproduced with the following:
> Firefox 45.8.0
> OS Windows 7.
> CPU usage 70%-90%
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8031) [Broker-J, System Tests] Bump version of AMQP 0-x client to 6.3.0
[ https://issues.apache.org/jira/browse/QPID-8031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8031: - Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J, System Tests] Bump version of AMQP 0-x client to 6.3.0 > - > > Key: QPID-8031 > URL: https://issues.apache.org/jira/browse/QPID-8031 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Lorenz Quack >Priority: Minor > Fix For: qpid-java-broker-7.1.0 > > Attachments: > 0001-QPID-8031-Broker-J-System-Tests-Bump-version-of-AMQP.patch > > > When the 6.3.0 client is released we should bump the version in the broker. > Eventually the broker system tests should become independent of the specific > client version. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8040) [Broker-J] Uncaught java.nio.channels.CancelledKeyException seen during Broker shutdown
[
https://issues.apache.org/jira/browse/QPID-8040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8040:
-
Fix Version/s: qpid-java-broker-7.0.1
> [Broker-J] Uncaught java.nio.channels.CancelledKeyException seen during
> Broker shutdown
> ---
>
> Key: QPID-8040
> URL: https://issues.apache.org/jira/browse/QPID-8040
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.0
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.1
>
> Attachments:
> TEST-org.apache.qpid.systest.management.amqp.AmqpManagementTest.testInvokeOperationReturningMap
>
>
> The following exception was trapped by the UncaughtExceptionHandler during a
> shutdown of the Broker. The would have caused a abnormal termination. I
> expect it could also happen during a HA virtualhost mastership change too.
> This code hasn't changed, so I think the problem is probably longstanding.
> {noformat}
> 2017-11-10 20:30:04,540 DEBUG [QpidJMS Connection Executor:
> ID:51dec5e7-faf9-4b92-89ec-16396a27a101:1] o.a.q.j.u.ThreadPoolUtils Shutdown
> of ExecutorService:
> java.util.concurrent.ScheduledThreadPoolExecutor@6fbbe33[Terminated, pool
> size = 0, active threads = 0, queued tasks = 0, completed tasks = 24] is
> shutdown: true and terminated: true took: 0.000 seconds.
> 2017-11-10 20:30:04,540 DEBUG [VirtualHostNode-test-Config]
> o.a.q.s.c.u.TaskExecutorImpl Stopping task executor
> virtualhost-test-preferences
> 2017-11-10 20:30:04,544 DEBUG [VirtualHostNode-test-Config]
> o.a.q.s.c.u.TaskExecutorImpl Task executor is stopped
> 2017-11-10 20:30:04,543 ERROR [Selector-Port-amqp]
> o.a.q.t.u.InternalBrokerHolder Uncaught exception from thread
> Selector-Port-amqp
> java.nio.channels.CancelledKeyException: null
> at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73)
> at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:82)
> at
> java.nio.channels.spi.AbstractSelectableChannel.register(AbstractSelectableChannel.java:204)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.processSelectionKeys(SelectorThread.java:240)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:326)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
> at
> org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:528)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8017) [Broker-J] [BDB] JE log events written at JUL level FINE and below not included in the log produced by a BrokerLogger
[
https://issues.apache.org/jira/browse/QPID-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8017:
-
Fix Version/s: (was: Future)
qpid-java-broker-7.0.1
> [Broker-J] [BDB] JE log events written at JUL level FINE and below not
> included in the log produced by a BrokerLogger
> --
>
> Key: QPID-8017
> URL: https://issues.apache.org/jira/browse/QPID-8017
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.1, qpid-java-broker-7.0.0
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.1
>
>
> Reproduction:
> * Add {{NameAndLevel}} logger inclusion rule BrokerLogger {{file}} for source
> {{com.sleepycat.je.*}} with Level.ALL
> * Add a BDB HA VHN/VHN
> * Expected behaviour: verbose logging from JE. Actual behaviour: moderate
> logging only
> For instance, JE writes the following message at {{FINE}} which should be
> logged by the handler as {{TRACE}} but it is absent.
> {noformat}
> 2017-11-07 10:42:15,467 TRACE [Cleaner-1] (c.s.j.c.UtilizationCalculator) -
> [default] Clean file none: predicted min util is below minUtilization,
> current util min: 20 max: 20, predicted util min: 20 max: 20
> {noformat}
> There is a workaround for the functional problem, albeit a restart is
> required and the ability to change the process's system properties. Use the
> normal JUL system property {{java.util.logging.config.file}}. Set this to
> the location of a logging.properties file with the {{com.sleepycat.je}}
> logger set to the desired level. Once the JVM is restarted, the Broker's log
> files will include the logging.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7996) [Broker-J] Make operations regarding link registry thread safe
[ https://issues.apache.org/jira/browse/QPID-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7996: - Fix Version/s: (was: qpid-java-broker-7.0.1) qpid-java-broker-7.1.0 > [Broker-J] Make operations regarding link registry thread safe > -- > > Key: QPID-7996 > URL: https://issues.apache.org/jira/browse/QPID-7996 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0 >Reporter: Alex Rudyy > Fix For: qpid-java-broker-7.1.0 > > > Operations like removal of shared subscription links and 'null source lookup' > for global shared subscriptions are not thread safe. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8029) [Broker-J] [AMQP 0-8..0-91] tx.rollback on non-transacted channel should not rollback the channel
[
https://issues.apache.org/jira/browse/QPID-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8029:
-
Fix Version/s: qpid-java-broker-7.0.1
> [Broker-J] [AMQP 0-8..0-91] tx.rollback on non-transacted channel should not
> rollback the channel
> --
>
> Key: QPID-8029
> URL: https://issues.apache.org/jira/browse/QPID-8029
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-broker-7.0.1
>
>
> Currently, calling {{tx.rollback}} on a non-transacted session closes the
> channel (as required by the specification), but then erroneously goes on to
> rollback anyway.
> AMQP 0-9 spec says:
> bq. The client must use this method [tx.select] at least once on a channel
> before using the Commit or Rollback methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8036) [Broker-J] [BDB HA] If ReplicationEnvironment fails when creating a node for the first time, clean up any directory left behind by BDB
[
https://issues.apache.org/jira/browse/QPID-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8036:
-
Description:
If the {{ReplicatedEnvironment}} constructor fails for a new node, any
directory left behind by BDB JE HA should be cleaned up. We have seen problem
reports where group creation had failed (owning to network issues within a
segmented network), but the environment directory was being left behind on disk.
The existence of the directory then goes on to cause further failures if later
another group tries to create a new node in the same location. Currently this
requires manual (shell) intervention to clean-up.
was:
If the {{ReplicatedEnvironment}} constructor fails for a new node, any
directory left behind by BDB JE HA should be cleaned up. We have seen problem
reports where group creation had failed (owning to network issues within a
segmented network), but the environment directory was being left behind on disk.
The existence of the directory then goes on to cause further failures if later
another group tries to create a new node on the same location.
> [Broker-J] [BDB HA] If ReplicationEnvironment fails when creating a node for
> the first time, clean up any directory left behind by BDB
> --
>
> Key: QPID-8036
> URL: https://issues.apache.org/jira/browse/QPID-8036
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
>Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
>
> If the {{ReplicatedEnvironment}} constructor fails for a new node, any
> directory left behind by BDB JE HA should be cleaned up. We have seen
> problem reports where group creation had failed (owning to network issues
> within a segmented network), but the environment directory was being left
> behind on disk.
> The existence of the directory then goes on to cause further failures if
> later another group tries to create a new node in the same location.
> Currently this requires manual (shell) intervention to clean-up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8036) [Broker-J] [BDB HA] If ReplicationEnvironment fails when creating a node for the first time, clean up any directory left behind by BDB
[
https://issues.apache.org/jira/browse/QPID-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8036:
-
Fix Version/s: qpid-java-broker-7.0.1
> [Broker-J] [BDB HA] If ReplicationEnvironment fails when creating a node for
> the first time, clean up any directory left behind by BDB
> --
>
> Key: QPID-8036
> URL: https://issues.apache.org/jira/browse/QPID-8036
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
>Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.1
>
>
> If the {{ReplicatedEnvironment}} constructor fails for a new node, any
> directory left behind by BDB JE HA should be cleaned up. We have seen
> problem reports where group creation had failed (owning to network issues
> within a segmented network), but the environment directory was being left
> behind on disk.
> The existence of the directory then goes on to cause further failures if
> later another group tries to create a new node in the same location.
> Currently this requires manual (shell) intervention to clean-up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8042) [Broker-J][AMQP 1.0] Add support for pipelined connection open containing sasl frames
[
https://issues.apache.org/jira/browse/QPID-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8042:
-
Fix Version/s: qpid-java-broker-7.0.1
> [Broker-J][AMQP 1.0] Add support for pipelined connection open containing
> sasl frames
> -
>
> Key: QPID-8042
> URL: https://issues.apache.org/jira/browse/QPID-8042
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.0.1
>
>
> Opening of connection with pipelined SASL header, sasl mechanism frame (for
> plain), sasl init (with valid SASL initial response), protocol header and
> connection open frame fails with the following exception
> {noformat}
> org.apache.qpid.server.util.ConnectionScopedRuntimeException: Connection is
> closed before being fully established: specified frame size 1095586128 larger
> than maximum frame header size 4096
> at
> org.apache.qpid.server.protocol.v1_0.AMQPConnection_1_0Impl.closeConnection(AMQPConnection_1_0Impl.java:1176)
> at
> org.apache.qpid.server.protocol.v1_0.AMQPConnection_1_0Impl.handleError(AMQPConnection_1_0Impl.java:783)
> at
> org.apache.qpid.server.protocol.v1_0.framing.FrameHandler.parse(FrameHandler.java:215)
> at
> org.apache.qpid.server.protocol.v1_0.AMQPConnection_1_0Impl.lambda$received$11(AMQPConnection_1_0Impl.java:1316)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.qpid.server.protocol.v1_0.AMQPConnection_1_0Impl.received(AMQPConnection_1_0Impl.java:1291)
> at
> org.apache.qpid.server.transport.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:134)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.processAmqpData(NonBlockingConnection.java:610)
> at
> org.apache.qpid.server.transport.NonBlockingConnectionPlainDelegate.processData(NonBlockingConnectionPlainDelegate.java:58)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doRead(NonBlockingConnection.java:496)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doWork(NonBlockingConnection.java:270)
> at
> org.apache.qpid.server.transport.NetworkConnectionScheduler.processConnection(NetworkConnectionScheduler.java:134)
> at
> org.apache.qpid.server.transport.SelectorThread$ConnectionProcessor.processConnection(SelectorThread.java:570)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:361)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
> at
> org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:528)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> As per spec section {{2.4.2 Pipelined Open}}
> {quote}
> For applications that use many short-lived connections, it MAY be desirable
> to pipeline the connection negotiation process. A peer MAY do this by
> starting to send subsequent frames before receiving the partner’s connection
> header or open frame. This is permitted so long as the pipelined frames are
> known a priori to conform to the
> capabilities and limitations of its partner.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session
[
https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276613#comment-16276613
]
Keith Wall edited comment on QPID-8047 at 12/4/17 10:56 AM:
Obviously, a well behaved client should not do this, but the NPE is still
unacceptable. Does the Broker fail?
was (Author: k-wall):
Does this Broker fail?
> [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session
> -
>
> Key: QPID-8047
> URL: https://issues.apache.org/jira/browse/QPID-8047
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.0.1
>
>
> The following NPE is reported on receiving of detach for unknown session
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.stopAllSubscriptions(ServerConnectionDelegate.java:377)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.sessionDetach(ServerConnectionDelegate.java:366)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.sessionDetach(ServerConnectionDelegate.java:52)
> at
> org.apache.qpid.server.protocol.v0_10.transport.SessionDetach.dispatch(SessionDetach.java:90)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.control(ServerConnectionDelegate.java:97)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.control(ServerConnectionDelegate.java:52)
> at
> org.apache.qpid.server.protocol.v0_10.transport.Method.delegate(Method.java:157)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.received(ServerConnection.java:279)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.emit(ServerAssembler.java:178)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.assemble(ServerAssembler.java:256)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.frame(ServerAssembler.java:205)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.received(ServerAssembler.java:135)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.received(ServerAssembler.java:109)
> at
> org.apache.qpid.server.protocol.v0_10.ServerInputHandler.received(ServerInputHandler.java:184)
> at
> org.apache.qpid.server.protocol.v0_10.AMQPConnection_0_10Impl.lambda$received$1(AMQPConnection_0_10Impl.java:146)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.qpid.server.protocol.v0_10.AMQPConnection_0_10Impl.received(AMQPConnection_0_10Impl.java:141)
> at
> org.apache.qpid.server.transport.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:134)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.processAmqpData(NonBlockingConnection.java:610)
> at
> org.apache.qpid.server.transport.NonBlockingConnectionPlainDelegate.processData(NonBlockingConnectionPlainDelegate.java:58)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doRead(NonBlockingConnection.java:496)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doWork(NonBlockingConnection.java:270)
> at
> org.apache.qpid.server.transport.NetworkConnectionScheduler.processConnection(NetworkConnectionScheduler.java:134)
> at
> org.apache.qpid.server.transport.SelectorThread$ConnectionProcessor.processConnection(SelectorThread.java:570)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:361)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
> at
> org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:528)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session
[
https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276613#comment-16276613
]
Keith Wall commented on QPID-8047:
--
Does this Broker fail?
> [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session
> -
>
> Key: QPID-8047
> URL: https://issues.apache.org/jira/browse/QPID-8047
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.0.1
>
>
> The following NPE is reported on receiving of detach for unknown session
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.stopAllSubscriptions(ServerConnectionDelegate.java:377)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.sessionDetach(ServerConnectionDelegate.java:366)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.sessionDetach(ServerConnectionDelegate.java:52)
> at
> org.apache.qpid.server.protocol.v0_10.transport.SessionDetach.dispatch(SessionDetach.java:90)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.control(ServerConnectionDelegate.java:97)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.control(ServerConnectionDelegate.java:52)
> at
> org.apache.qpid.server.protocol.v0_10.transport.Method.delegate(Method.java:157)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.received(ServerConnection.java:279)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.emit(ServerAssembler.java:178)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.assemble(ServerAssembler.java:256)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.frame(ServerAssembler.java:205)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.received(ServerAssembler.java:135)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.received(ServerAssembler.java:109)
> at
> org.apache.qpid.server.protocol.v0_10.ServerInputHandler.received(ServerInputHandler.java:184)
> at
> org.apache.qpid.server.protocol.v0_10.AMQPConnection_0_10Impl.lambda$received$1(AMQPConnection_0_10Impl.java:146)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.qpid.server.protocol.v0_10.AMQPConnection_0_10Impl.received(AMQPConnection_0_10Impl.java:141)
> at
> org.apache.qpid.server.transport.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:134)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.processAmqpData(NonBlockingConnection.java:610)
> at
> org.apache.qpid.server.transport.NonBlockingConnectionPlainDelegate.processData(NonBlockingConnectionPlainDelegate.java:58)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doRead(NonBlockingConnection.java:496)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doWork(NonBlockingConnection.java:270)
> at
> org.apache.qpid.server.transport.NetworkConnectionScheduler.processConnection(NetworkConnectionScheduler.java:134)
> at
> org.apache.qpid.server.transport.SelectorThread$ConnectionProcessor.processConnection(SelectorThread.java:570)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:361)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
> at
> org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:528)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8047) [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session
[
https://issues.apache.org/jira/browse/QPID-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8047:
-
Fix Version/s: qpid-java-broker-7.0.1
> [Broker-J][AMQP 0-10] NPE on receiving session.detach for unknown session
> -
>
> Key: QPID-8047
> URL: https://issues.apache.org/jira/browse/QPID-8047
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0
>Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.0.1
>
>
> The following NPE is reported on receiving of detach for unknown session
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.stopAllSubscriptions(ServerConnectionDelegate.java:377)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.sessionDetach(ServerConnectionDelegate.java:366)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.sessionDetach(ServerConnectionDelegate.java:52)
> at
> org.apache.qpid.server.protocol.v0_10.transport.SessionDetach.dispatch(SessionDetach.java:90)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.control(ServerConnectionDelegate.java:97)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnectionDelegate.control(ServerConnectionDelegate.java:52)
> at
> org.apache.qpid.server.protocol.v0_10.transport.Method.delegate(Method.java:157)
> at
> org.apache.qpid.server.protocol.v0_10.ServerConnection.received(ServerConnection.java:279)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.emit(ServerAssembler.java:178)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.assemble(ServerAssembler.java:256)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.frame(ServerAssembler.java:205)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.received(ServerAssembler.java:135)
> at
> org.apache.qpid.server.protocol.v0_10.ServerAssembler.received(ServerAssembler.java:109)
> at
> org.apache.qpid.server.protocol.v0_10.ServerInputHandler.received(ServerInputHandler.java:184)
> at
> org.apache.qpid.server.protocol.v0_10.AMQPConnection_0_10Impl.lambda$received$1(AMQPConnection_0_10Impl.java:146)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.qpid.server.protocol.v0_10.AMQPConnection_0_10Impl.received(AMQPConnection_0_10Impl.java:141)
> at
> org.apache.qpid.server.transport.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:134)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.processAmqpData(NonBlockingConnection.java:610)
> at
> org.apache.qpid.server.transport.NonBlockingConnectionPlainDelegate.processData(NonBlockingConnectionPlainDelegate.java:58)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doRead(NonBlockingConnection.java:496)
> at
> org.apache.qpid.server.transport.NonBlockingConnection.doWork(NonBlockingConnection.java:270)
> at
> org.apache.qpid.server.transport.NetworkConnectionScheduler.processConnection(NetworkConnectionScheduler.java:134)
> at
> org.apache.qpid.server.transport.SelectorThread$ConnectionProcessor.processConnection(SelectorThread.java:570)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.performSelect(SelectorThread.java:361)
> at
> org.apache.qpid.server.transport.SelectorThread$SelectionTask.run(SelectorThread.java:97)
> at
> org.apache.qpid.server.transport.SelectorThread.run(SelectorThread.java:528)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
