[jira] [Closed] (DISPATCH-764) Cannot receive from a multicast address
[
https://issues.apache.org/jira/browse/DISPATCH-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek closed DISPATCH-764.
---
Resolution: Not A Bug
My mistake, the simple_send.py does not print the error it is getting, which is
Condition: qd:forbidden
Description: Deliveries to a multicast address must be pre-settled
So it is only the result of change of behavior implemented in DISPATCH-744.
> Cannot receive from a multicast address
> ---
>
> Key: DISPATCH-764
> URL: https://issues.apache.org/jira/browse/DISPATCH-764
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Jiri Danek
>Priority: Critical
>
> 1) Start qdrouterd with the default config (listens on localhost, defines
> `multicast` address prefix)
> 2) {{qpid-proton/examples/python/simple_recv.py -a 127.0.0.1:5672/multicast
> -m 1}}
> 3) {{qpid-proton/examples/python/simple_send.py -a 127.0.0.1:5672/multicast
> -m 1}}
> The message sent in step 3) is not received and printed by receiver started
> in step 2).
> This used to work in version 0.7.0 and in version 0.8.0, it does not work for
> me in git tip build (what is to be 1.0.0).
> Since this seems such a basic scenario, I have doubts if it is really a bug.
> Maybe the behavior of the feature just changed, or I am doing something wrong.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-764) Cannot receive from a multicast address
Jiri Danek created DISPATCH-764:
---
Summary: Cannot receive from a multicast address
Key: DISPATCH-764
URL: https://issues.apache.org/jira/browse/DISPATCH-764
Project: Qpid Dispatch
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Jiri Danek
Priority: Critical
1) Start qdrouterd with the default config (listens on localhost, defines
`multicast` address prefix)
2) {{qpid-proton/examples/python/simple_recv.py -a 127.0.0.1:5672/multicast -m
1}}
3) {{qpid-proton/examples/python/simple_send.py -a 127.0.0.1:5672/multicast -m
1}}
The message sent in step 3) is not received and printed by receiver started in
step 2).
This used to work in version 0.7.0 and in version 0.8.0, it does not work for
me in git tip build (what is to be 1.0.0).
Since this seems such a basic scenario, I have doubts if it is really a bug.
Maybe the behavior of the feature just changed, or I am doing something wrong.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7768) Problem building on Fedora rawhide
[
https://issues.apache.org/jira/browse/QPID-7768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997194#comment-15997194
]
Irina Boverman commented on QPID-7768:
--
[ 78%] Building CXX object
src/CMakeFiles/qpidbroker.dir/qpid/broker/SessionAdapter.cpp.o
cd /builddir/build/BUILD/qpid-cpp-1.36.0/src && /usr/bin/c++
-DXQ_EFFECTIVE_BOOLEAN_VALUE_HPP -Dqpidbroker_EXPORTS
-I/builddir/build/BUILD/qpid-cpp-1.36.0/src
-I/builddir/build/BUILD/qpid-cpp-1.36.0/src/../include -I/usr/include/nss3
-I/usr/include/nspr4 -std=c++11 -Wno-implicit-fallthrough
-Wno-deprecated-declarations -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4 -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic
-fvisibility-inlines-hidden -Werror -pedantic -Wall -Wextra -Wno-shadow
-Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var
-Winvalid-pch -Wno-system-headers -Woverloaded-virtual
-Wno-error=deprecated-declarations -O2 -g -DNDEBUG -fPIC -pthread -o
CMakeFiles/qpidbroker.dir/qpid/broker/SessionAdapter.cpp.o -c
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SessionAdapter.cpp
In file included from
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.cpp:22:0:
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.h: In
member function 'const qpid::broker::Token&
qpid::broker::Tokeniser::nextToken()':
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.h:67:8:
error: '.qpid::broker::Token::type' may be used uninitialized in
this function [-Werror=maybe-uninitialized]
struct Token {
^
cc1plus: all warnings being treated as errors
make[2]: *** [src/CMakeFiles/qpidbroker.dir/build.make:3282:
src/CMakeFiles/qpidbroker.dir/qpid/broker/SelectorToken.cpp.o] Error 1
> Problem building on Fedora rawhide
> --
>
> Key: QPID-7768
> URL: https://issues.apache.org/jira/browse/QPID-7768
> Project: Qpid
> Issue Type: Bug
> Components: C++ Build
>Affects Versions: qpid-cpp-1.36.0
> Environment: [ 78%] Building CXX object
> src/CMakeFiles/qpidbroker.dir/qpid/broker/SessionAdapter.cpp.o
> cd /builddir/build/BUILD/qpid-cpp-1.36.0/src && /usr/bin/c++
> -DXQ_EFFECTIVE_BOOLEAN_VALUE_HPP -Dqpidbroker_EXPORTS
> -I/builddir/build/BUILD/qpid-cpp-1.36.0/src
> -I/builddir/build/BUILD/qpid-cpp-1.36.0/src/../include -I/usr/include/nss3
> -I/usr/include/nspr4 -std=c++11 -Wno-implicit-fallthrough
> -Wno-deprecated-declarations -O2 -g -pipe -Wall -Werror=format-security
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
> --param=ssp-buffer-size=4 -grecord-gcc-switches
> -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic
> -fvisibility-inlines-hidden -Werror -pedantic -Wall -Wextra -Wno-shadow
> -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
> -Wvolatile-register-var -Winvalid-pch -Wno-system-headers
> -Woverloaded-virtual -Wno-error=deprecated-declarations -O2 -g -DNDEBUG -fPIC
> -pthread -o CMakeFiles/qpidbroker.dir/qpid/broker/SessionAdapter.cpp.o -c
> /builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SessionAdapter.cpp
> In file included from
> /builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.cpp:22:0:
> /builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.h: In
> member function 'const qpid::broker::Token&
> qpid::broker::Tokeniser::nextToken()':
> /builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.h:67:8:
> error: '.qpid::broker::Token::type' may be used uninitialized in
> this function [-Werror=maybe-uninitialized]
> struct Token {
> ^
> cc1plus: all warnings being treated as errors
> make[2]: *** [src/CMakeFiles/qpidbroker.dir/build.make:3282:
> src/CMakeFiles/qpidbroker.dir/qpid/broker/SelectorToken.cpp.o] Error 1
>Reporter: Irina Boverman
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7768) Problem building on Fedora rawhide
Irina Boverman created QPID-7768:
Summary: Problem building on Fedora rawhide
Key: QPID-7768
URL: https://issues.apache.org/jira/browse/QPID-7768
Project: Qpid
Issue Type: Bug
Components: C++ Build
Affects Versions: qpid-cpp-1.36.0
Environment: [ 78%] Building CXX object
src/CMakeFiles/qpidbroker.dir/qpid/broker/SessionAdapter.cpp.o
cd /builddir/build/BUILD/qpid-cpp-1.36.0/src && /usr/bin/c++
-DXQ_EFFECTIVE_BOOLEAN_VALUE_HPP -Dqpidbroker_EXPORTS
-I/builddir/build/BUILD/qpid-cpp-1.36.0/src
-I/builddir/build/BUILD/qpid-cpp-1.36.0/src/../include -I/usr/include/nss3
-I/usr/include/nspr4 -std=c++11 -Wno-implicit-fallthrough
-Wno-deprecated-declarations -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4 -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic
-fvisibility-inlines-hidden -Werror -pedantic -Wall -Wextra -Wno-shadow
-Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wvolatile-register-var
-Winvalid-pch -Wno-system-headers -Woverloaded-virtual
-Wno-error=deprecated-declarations -O2 -g -DNDEBUG -fPIC -pthread -o
CMakeFiles/qpidbroker.dir/qpid/broker/SessionAdapter.cpp.o -c
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SessionAdapter.cpp
In file included from
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.cpp:22:0:
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.h: In
member function 'const qpid::broker::Token&
qpid::broker::Tokeniser::nextToken()':
/builddir/build/BUILD/qpid-cpp-1.36.0/src/qpid/broker/SelectorToken.h:67:8:
error: '.qpid::broker::Token::type' may be used uninitialized in
this function [-Werror=maybe-uninitialized]
struct Token {
^
cc1plus: all warnings being treated as errors
make[2]: *** [src/CMakeFiles/qpidbroker.dir/build.make:3282:
src/CMakeFiles/qpidbroker.dir/qpid/broker/SelectorToken.cpp.o] Error 1
Reporter: Irina Boverman
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1472) travis test for libuv proactor
[ https://issues.apache.org/jira/browse/PROTON-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1472. - Resolution: Fixed > travis test for libuv proactor > -- > > Key: PROTON-1472 > URL: https://issues.apache.org/jira/browse/PROTON-1472 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Affects Versions: 0.17.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.18.0 > > > The .travis.yml script does not install libuv and so does not test the libuv > proactor. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7753) Sparsely occupied message buffers may lead to java.lang.OutOfMemoryError: Direct buffer memory
[
https://issues.apache.org/jira/browse/QPID-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996859#comment-15996859
]
ASF subversion and git services commented on QPID-7753:
---
Commit 7f9cc7573892f88ba8adc690f06a3229d5235b0a in qpid-broker-j's branch
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=7f9cc75 ]
QPID-7753: [AMQP1.0] Fix QpidByteBuffer leak of data sections
> Sparsely occupied message buffers may lead to java.lang.OutOfMemoryError:
> Direct buffer memory
> --
>
> Key: QPID-7753
> URL: https://issues.apache.org/jira/browse/QPID-7753
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1
>Reporter: Keith Wall
>Assignee: Keith Wall
> Attachments: flow-to-disk-based-on-used-direct-memory-6-0-x.diff
>
>
> Some Broker usage patterns can lead to the Broker failing with a
> "java.lang.OutOfMemoryError: Direct buffer memory" error.
> For the condition to manifest a producing application needs to use a single
> connection for the production of messages. Some messages need to be consumed
> quickly whilst others remain on the Broker. This pattern might result from:
> # the consuming application using message selectors to selectively consume
> some messages whilst leaving others on the Broker.
> # the use of 'out of order' queue types (priority/sorted etc) where lower
> priority items are left of the Broker.
> # the producing application routing messages to multiple queues and the
> consuming application draining some queues but not others.
> The problem arises owing to the buffering strategy under the IO layer.
> {{NonBlockingConnection}} allocates a {{netInputBuffer}} from pooled direct
> memory of size 256K. This buffer is used for all network reads until the
> space remaining in the buffer is less than the amount required to complete
> the AMQP frame that is currently being read, in which case a new
> netInputBuffer is allocated. The protocol layers identify the message
> payload/message headers as part of AMQP frame parsing and create a
> byte-buffer *views* onto the original input byte buffer. This byte buffer is
> retained by the store until the message is consumed. In the usage pattern
> described above, a single long lived message amongst a stream of shorted
> lived messages causes an entire 256K buffer chunk to be retained. Qpid
> cannot dispose or reuse the buffer until it is entirely unoccupied.
> The flow to disk feature is designed to prevent excessive direct memory use
> by flushing messages to disk if thresholds are breached. Flow to disk does
> not help the scenario described above because it considers the total payloads
> of live messages. Its algorithm does not consider direct memory occupancy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-763) Router crashes when config file defines listener { addr: } instead of { host: }
[
https://issues.apache.org/jira/browse/DISPATCH-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-763:
Summary: Router crashes when config file defines listener { addr: } instead
of { host: } (was: Router crashes with the following config file)
> Router crashes when config file defines listener { addr: } instead of { host:
> }
> ---
>
> Key: DISPATCH-763
> URL: https://issues.apache.org/jira/browse/DISPATCH-763
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.0.0
> Environment: Debian Stretch, qpid-proton from git, qpid-dispatch from
> git
>Reporter: Jiri Danek
>Priority: Critical
> Attachments: DISPATCH-763.core.zip
>
>
> If I run {{qdrouterd -c console.conf}}, where console.conf is the config
> pasted below, the router crashes. The router works ok with the default
> config. This error appeared only recently (during last week, no sooner). The
> config used to work fine before.
> The attached stack trace and core file come from debug build. With production
> build, it obviously does not print the assertion error and it crashes
> somewhat later.
> {noformat}
> # qdrouterd -c /mnt/run/router/console.conf
> 2017-05-04 13:57:19.313172 + SERVER (warning) HTTP support is not
> available
> 2017-05-04 13:57:19.313239 + SERVER (info) Container Name: Router.A
> 2017-05-04 13:57:19.31 + ROUTER (info) Router started in Standalone
> mode
> 2017-05-04 13:57:19.313456 + ROUTER_CORE (info) Allow Unsettled
> Multicast: no
> 2017-05-04 13:57:19.313734 + ROUTER_CORE (info) Router Core thread
> running. 0/Router.A
> 2017-05-04 13:57:19.313759 + ROUTER_CORE (info) In-process subscription
> M/$management
> 2017-05-04 13:57:19.321037 + AGENT (info) Activating management agent on
> $_management_internal
> 2017-05-04 13:57:19.321127 + ROUTER_CORE (info) In-process subscription
> L/$management
> 2017-05-04 13:57:19.321164 + ROUTER_CORE (info) In-process subscription
> L/$_management_internal
> 2017-05-04 13:57:19.322578 + CONN_MGR (info) Configured Listener:
> 0.0.0.0:amqp proto=any, role=normal
> qdrouterd: /main/qpid-dispatch/src/connection_manager.c:187: set_config_host:
> Assertion `config->host' failed.
> Aborted (core dumped)
> {noformat}
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> address {
> prefix: closest
> distribution: closest
> }
> address {
> prefix: multicast
> distribution: multicast
> }
> address {
> prefix: unicast
> distribution: closest
> }
> address {
> prefix: exclusive
> distribution: closest
> }
> address {
> prefix: broadcast
> distribution: multicast
> }
> listener {
> name: ProxyListener
> role: normal
> addr: 0.0.0.0
> port: 20009
> sasl-mechanisms: ANONYMOUS
> }
> {noformat}
> {noformat}
> # gdb -c core `which qdrouterd`
> GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
>
[jira] [Updated] (DISPATCH-763) Router crashes with the following config file
[
https://issues.apache.org/jira/browse/DISPATCH-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-763:
Affects Version/s: 1.0.0
> Router crashes with the following config file
> -
>
> Key: DISPATCH-763
> URL: https://issues.apache.org/jira/browse/DISPATCH-763
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.0.0
> Environment: Debian Stretch, qpid-proton from git, qpid-dispatch from
> git
>Reporter: Jiri Danek
>Priority: Critical
> Attachments: DISPATCH-763.core.zip
>
>
> If I run {{qdrouterd -c console.conf}}, where console.conf is the config
> pasted below, the router crashes. The router works ok with the default
> config. This error appeared only recently (during last week, no sooner). The
> config used to work fine before.
> The attached stack trace and core file come from debug build. With production
> build, it obviously does not print the assertion error and it crashes
> somewhat later.
> {noformat}
> # qdrouterd -c /mnt/run/router/console.conf
> 2017-05-04 13:57:19.313172 + SERVER (warning) HTTP support is not
> available
> 2017-05-04 13:57:19.313239 + SERVER (info) Container Name: Router.A
> 2017-05-04 13:57:19.31 + ROUTER (info) Router started in Standalone
> mode
> 2017-05-04 13:57:19.313456 + ROUTER_CORE (info) Allow Unsettled
> Multicast: no
> 2017-05-04 13:57:19.313734 + ROUTER_CORE (info) Router Core thread
> running. 0/Router.A
> 2017-05-04 13:57:19.313759 + ROUTER_CORE (info) In-process subscription
> M/$management
> 2017-05-04 13:57:19.321037 + AGENT (info) Activating management agent on
> $_management_internal
> 2017-05-04 13:57:19.321127 + ROUTER_CORE (info) In-process subscription
> L/$management
> 2017-05-04 13:57:19.321164 + ROUTER_CORE (info) In-process subscription
> L/$_management_internal
> 2017-05-04 13:57:19.322578 + CONN_MGR (info) Configured Listener:
> 0.0.0.0:amqp proto=any, role=normal
> qdrouterd: /main/qpid-dispatch/src/connection_manager.c:187: set_config_host:
> Assertion `config->host' failed.
> Aborted (core dumped)
> {noformat}
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> address {
> prefix: closest
> distribution: closest
> }
> address {
> prefix: multicast
> distribution: multicast
> }
> address {
> prefix: unicast
> distribution: closest
> }
> address {
> prefix: exclusive
> distribution: closest
> }
> address {
> prefix: broadcast
> distribution: multicast
> }
> listener {
> name: ProxyListener
> role: normal
> addr: 0.0.0.0
> port: 20009
> sasl-mechanisms: ANONYMOUS
> }
> {noformat}
> {noformat}
> # gdb -c core `which qdrouterd`
> GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
>
[jira] [Updated] (DISPATCH-763) Router crashes with the following config file
[
https://issues.apache.org/jira/browse/DISPATCH-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-763:
Attachment: DISPATCH-763.core.zip
> Router crashes with the following config file
> -
>
> Key: DISPATCH-763
> URL: https://issues.apache.org/jira/browse/DISPATCH-763
> Project: Qpid Dispatch
> Issue Type: Bug
> Environment: Debian Stretch, qpid-proton from git, qpid-dispatch from
> git
>Reporter: Jiri Danek
>Priority: Critical
> Attachments: DISPATCH-763.core.zip
>
>
> If I run {{qdrouterd -c console.conf}}, where console.conf is the config
> pasted below, the router crashes. The router works ok with the default
> config. This error appeared only recently (during last week, no sooner). The
> config used to work fine before.
> The attached stack trace and core file come from debug build. With production
> build, it obviously does not print the assertion error and it crashes
> somewhat later.
> {noformat}
> # qdrouterd -c /mnt/run/router/console.conf
> 2017-05-04 13:57:19.313172 + SERVER (warning) HTTP support is not
> available
> 2017-05-04 13:57:19.313239 + SERVER (info) Container Name: Router.A
> 2017-05-04 13:57:19.31 + ROUTER (info) Router started in Standalone
> mode
> 2017-05-04 13:57:19.313456 + ROUTER_CORE (info) Allow Unsettled
> Multicast: no
> 2017-05-04 13:57:19.313734 + ROUTER_CORE (info) Router Core thread
> running. 0/Router.A
> 2017-05-04 13:57:19.313759 + ROUTER_CORE (info) In-process subscription
> M/$management
> 2017-05-04 13:57:19.321037 + AGENT (info) Activating management agent on
> $_management_internal
> 2017-05-04 13:57:19.321127 + ROUTER_CORE (info) In-process subscription
> L/$management
> 2017-05-04 13:57:19.321164 + ROUTER_CORE (info) In-process subscription
> L/$_management_internal
> 2017-05-04 13:57:19.322578 + CONN_MGR (info) Configured Listener:
> 0.0.0.0:amqp proto=any, role=normal
> qdrouterd: /main/qpid-dispatch/src/connection_manager.c:187: set_config_host:
> Assertion `config->host' failed.
> Aborted (core dumped)
> {noformat}
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> port: amqp
> authenticatePeer: no
> }
> address {
> prefix: closest
> distribution: closest
> }
> address {
> prefix: multicast
> distribution: multicast
> }
> address {
> prefix: unicast
> distribution: closest
> }
> address {
> prefix: exclusive
> distribution: closest
> }
> address {
> prefix: broadcast
> distribution: multicast
> }
> listener {
> name: ProxyListener
> role: normal
> addr: 0.0.0.0
> port: 20009
> sasl-mechanisms: ANONYMOUS
> }
> {noformat}
> {noformat}
> # gdb -c core `which qdrouterd`
> GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
>
[jira] [Updated] (DISPATCH-763) Router crashes with the following config file
[
https://issues.apache.org/jira/browse/DISPATCH-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek updated DISPATCH-763:
Description:
If I run {{qdrouterd -c console.conf}}, where console.conf is the config pasted
below, the router crashes. The router works ok with the default config. This
error appeared only recently (during last week, no sooner). The config used to
work fine before.
The attached stack trace and core file come from debug build. With production
build, it obviously does not print the assertion error and it crashes somewhat
later.
{noformat}
# qdrouterd -c /mnt/run/router/console.conf
2017-05-04 13:57:19.313172 + SERVER (warning) HTTP support is not available
2017-05-04 13:57:19.313239 + SERVER (info) Container Name: Router.A
2017-05-04 13:57:19.31 + ROUTER (info) Router started in Standalone mode
2017-05-04 13:57:19.313456 + ROUTER_CORE (info) Allow Unsettled Multicast:
no
2017-05-04 13:57:19.313734 + ROUTER_CORE (info) Router Core thread running.
0/Router.A
2017-05-04 13:57:19.313759 + ROUTER_CORE (info) In-process subscription
M/$management
2017-05-04 13:57:19.321037 + AGENT (info) Activating management agent on
$_management_internal
2017-05-04 13:57:19.321127 + ROUTER_CORE (info) In-process subscription
L/$management
2017-05-04 13:57:19.321164 + ROUTER_CORE (info) In-process subscription
L/$_management_internal
2017-05-04 13:57:19.322578 + CONN_MGR (info) Configured Listener:
0.0.0.0:amqp proto=any, role=normal
qdrouterd: /main/qpid-dispatch/src/connection_manager.c:187: set_config_host:
Assertion `config->host' failed.
Aborted (core dumped)
{noformat}
{noformat}
router {
mode: standalone
id: Router.A
}
listener {
host: 0.0.0.0
port: amqp
authenticatePeer: no
}
address {
prefix: closest
distribution: closest
}
address {
prefix: multicast
distribution: multicast
}
address {
prefix: unicast
distribution: closest
}
address {
prefix: exclusive
distribution: closest
}
address {
prefix: broadcast
distribution: multicast
}
listener {
name: ProxyListener
role: normal
addr: 0.0.0.0
port: 20009
sasl-mechanisms: ANONYMOUS
}
{noformat}
{noformat}
# gdb -c core `which qdrouterd`
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[jira] [Created] (DISPATCH-763) Router crashes with the following config file
Jiri Danek created DISPATCH-763:
---
Summary: Router crashes with the following config file
Key: DISPATCH-763
URL: https://issues.apache.org/jira/browse/DISPATCH-763
Project: Qpid Dispatch
Issue Type: Bug
Environment: Debian Stretch, qpid-proton from git, qpid-dispatch from
git
Reporter: Jiri Danek
Priority: Critical
If I run {{qdrouterd -c console.conf}}, where console.conf is the config pasted
below, the router crashes. The router works ok with the default config. This
error appeared only recently (during last week, no sooner).
The attached stack trace and core file come from debug build. With production
build, it obviously does not print the assertion error and it crashes somewhat
later.
{noformat}
# qdrouterd -c /mnt/run/router/console.conf
2017-05-04 13:57:19.313172 + SERVER (warning) HTTP support is not available
2017-05-04 13:57:19.313239 + SERVER (info) Container Name: Router.A
2017-05-04 13:57:19.31 + ROUTER (info) Router started in Standalone mode
2017-05-04 13:57:19.313456 + ROUTER_CORE (info) Allow Unsettled Multicast:
no
2017-05-04 13:57:19.313734 + ROUTER_CORE (info) Router Core thread running.
0/Router.A
2017-05-04 13:57:19.313759 + ROUTER_CORE (info) In-process subscription
M/$management
2017-05-04 13:57:19.321037 + AGENT (info) Activating management agent on
$_management_internal
2017-05-04 13:57:19.321127 + ROUTER_CORE (info) In-process subscription
L/$management
2017-05-04 13:57:19.321164 + ROUTER_CORE (info) In-process subscription
L/$_management_internal
2017-05-04 13:57:19.322578 + CONN_MGR (info) Configured Listener:
0.0.0.0:amqp proto=any, role=normal
qdrouterd: /main/qpid-dispatch/src/connection_manager.c:187: set_config_host:
Assertion `config->host' failed.
Aborted (core dumped)
{noformat}
{noformat}
router {
mode: standalone
id: Router.A
}
listener {
host: 0.0.0.0
port: amqp
authenticatePeer: no
}
address {
prefix: closest
distribution: closest
}
address {
prefix: multicast
distribution: multicast
}
address {
prefix: unicast
distribution: closest
}
address {
prefix: exclusive
distribution: closest
}
address {
prefix: broadcast
distribution: multicast
}
listener {
name: ProxyListener
role: normal
addr: 0.0.0.0
port: 20009
sasl-mechanisms: ANONYMOUS
}
{noformat}
{noformat}
# gdb -c core `which qdrouterd`
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[jira] [Assigned] (DISPATCH-757) Qpid Dispatch does not compile under Ubuntu
[
https://issues.apache.org/jira/browse/DISPATCH-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway reassigned DISPATCH-757:
Assignee: Ganesh Murthy (was: Alan Conway)
> Qpid Dispatch does not compile under Ubuntu
> ---
>
> Key: DISPATCH-757
> URL: https://issues.apache.org/jira/browse/DISPATCH-757
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 1.0.0
>
>
> Got the following error message when compiling qpid-dispatch master on
> ubuntu:latest.
> The following is the compile error -
> {noformat}
> [ 66%] Building C object src/CMakeFiles/qpid-dispatch.dir/trace_mask.c.o
> [ 67%] Building C object
> src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o
> /main/qpid-dispatch/src/http-libwebsockets.c: In function 'logger':
> /main/qpid-dispatch/src/http-libwebsockets.c:54:23: error: implicit
> declaration of function 'isspace' [-Werror=implicit-function-declaration]
> while (len > 1 && isspace(line[len-1])) { /* Strip trailing newline */
>^
> cc1: all warnings being treated as errors
> src/CMakeFiles/qpid-dispatch.dir/build.make:1184: recipe for target
> 'src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o' failed
> make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o] Error 1
> CMakeFiles/Makefile2:981: recipe for target
> 'src/CMakeFiles/qpid-dispatch.dir/all' failed
> make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
> make: *** [all] Error 2
> Makefile:138: recipe for target 'all' failed
> The command '/bin/sh -c cmake .. -DCMAKE_INSTALL_PREFIX=/usr && make install'
> returned a non-zero code: 2
> [gmurthy@localhost dockerfiles]$
> {noformat}
> The following is the docker file used
> {noformat}
> #
> # Licensed to the Apache Software Foundation (ASF) under one
> # or more contributor license agreements. See the NOTICE file
> # distributed with this work for additional information
> # regarding copyright ownership. The ASF licenses this file
> # to you under the Apache License, Version 2.0 (the
> # "License"); you may not use this file except in compliance
> # with the License. You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing,
> # software distributed under the License is distributed on an
> # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> # KIND, either express or implied. See the License for the
> # specific language governing permissions and limitations
> # under the License.
> #
> # Gets the latest Ubuntu from dockerhub
> FROM ubuntu:latest
> MAINTAINER "dev@qpid.apache.org"
> # Install all the required packages. Some in this list were picked off from
> proton's INSTALL.md
> (https://github.com/apache/qpid-proton/blob/master/INSTALL.md) and the rest
> are from dispatch (https://github.com/apache/qpid-dispatch/blob/master/README)
> RUN apt-get update && apt-get -y install gcc cmake cmake-curses-gui uuid-dev
> libssl-dev libsasl2-2 libsasl2-dev sasl2-bin swig python-dev ruby-dev
> libperl-dev git make doxygen valgrind emacs libuv1 libuv1-dev
> # Create a main directory and clone the qpid-proton repo from github
> RUN mkdir /main && cd /main && git clone
> https://git-wip-us.apache.org/repos/asf/qpid-proton.git && cd
> /main/qpid-proton && mkdir /main/qpid-proton/build
> WORKDIR /main/qpid-proton/build
> # make and install proton
> RUN cmake .. -DSYSINSTALL_BINDINGS=ON -DCMAKE_INSTALL_PREFIX=/usr
> -DSYSINSTALL_PYTHON=ON && make install
> # download libwebsockets code from
> https://github.com/warmcat/libwebsockets/commits/v2.1-stable
> RUN cd /main && git clone --branch v2.1-stable
> https://github.com/warmcat/libwebsockets.git && mkdir
> /main/libwebsockets/build
> WORKDIR /main/libwebsockets/build
> RUN cmake .. && make install
> # Clone the qpid-dispatch git repo
> RUN cd /main && git clone
> https://git-wip-us.apache.org/repos/asf/qpid-dispatch.git && mkdir
> /main/qpid-dispatch/build
> WORKDIR /main/qpid-dispatch/build
> RUN cmake .. -DCMAKE_INSTALL_PREFIX=/usr && make install
> # Add site-packages to the PYTHONPATH environment variable. This is because
> Ubuntu does not list the site-packages folder in the sys.path
> ENV PYTHONPATH=/usr/lib/python2.7/site-packages
> # Uncomment the following line if you would like to run all the dispatch unit
> tests and system tests.
> # RUN ctest -VV
> # Start the dispatch router
> CMD ["qdrouterd"]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-757) Qpid Dispatch does not compile under Ubuntu
[
https://issues.apache.org/jira/browse/DISPATCH-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996751#comment-15996751
]
Alan Conway commented on DISPATCH-757:
--
[~jdanek] I see the same thing. I will keep this JIRA open until we can
reliably run the test on CI systems like docker.
One problem is using valgrind with the embedded python VM - valgrind
instruments the entire executable so our valgrind runs are insanely slow due to
the work of tracking the python runtimes. However I turned it off in
.travis.yml and still see many failures so it is not the only problem.
In general our tests rely far to much on timeouts, which are inclined to go
wrong if the performance characteristics change. I think we need to try to
eliminate them as much as possible. If a test hangs permanently then cmake or
the surrounding CI harness will eventually time it out so we don't need most of
those timeouts in our test code.
> Qpid Dispatch does not compile under Ubuntu
> ---
>
> Key: DISPATCH-757
> URL: https://issues.apache.org/jira/browse/DISPATCH-757
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Alan Conway
> Fix For: 1.0.0
>
>
> Got the following error message when compiling qpid-dispatch master on
> ubuntu:latest.
> The following is the compile error -
> {noformat}
> [ 66%] Building C object src/CMakeFiles/qpid-dispatch.dir/trace_mask.c.o
> [ 67%] Building C object
> src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o
> /main/qpid-dispatch/src/http-libwebsockets.c: In function 'logger':
> /main/qpid-dispatch/src/http-libwebsockets.c:54:23: error: implicit
> declaration of function 'isspace' [-Werror=implicit-function-declaration]
> while (len > 1 && isspace(line[len-1])) { /* Strip trailing newline */
>^
> cc1: all warnings being treated as errors
> src/CMakeFiles/qpid-dispatch.dir/build.make:1184: recipe for target
> 'src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o' failed
> make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o] Error 1
> CMakeFiles/Makefile2:981: recipe for target
> 'src/CMakeFiles/qpid-dispatch.dir/all' failed
> make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
> make: *** [all] Error 2
> Makefile:138: recipe for target 'all' failed
> The command '/bin/sh -c cmake .. -DCMAKE_INSTALL_PREFIX=/usr && make install'
> returned a non-zero code: 2
> [gmurthy@localhost dockerfiles]$
> {noformat}
> The following is the docker file used
> {noformat}
> #
> # Licensed to the Apache Software Foundation (ASF) under one
> # or more contributor license agreements. See the NOTICE file
> # distributed with this work for additional information
> # regarding copyright ownership. The ASF licenses this file
> # to you under the Apache License, Version 2.0 (the
> # "License"); you may not use this file except in compliance
> # with the License. You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing,
> # software distributed under the License is distributed on an
> # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> # KIND, either express or implied. See the License for the
> # specific language governing permissions and limitations
> # under the License.
> #
> # Gets the latest Ubuntu from dockerhub
> FROM ubuntu:latest
> MAINTAINER "dev@qpid.apache.org"
> # Install all the required packages. Some in this list were picked off from
> proton's INSTALL.md
> (https://github.com/apache/qpid-proton/blob/master/INSTALL.md) and the rest
> are from dispatch (https://github.com/apache/qpid-dispatch/blob/master/README)
> RUN apt-get update && apt-get -y install gcc cmake cmake-curses-gui uuid-dev
> libssl-dev libsasl2-2 libsasl2-dev sasl2-bin swig python-dev ruby-dev
> libperl-dev git make doxygen valgrind emacs libuv1 libuv1-dev
> # Create a main directory and clone the qpid-proton repo from github
> RUN mkdir /main && cd /main && git clone
> https://git-wip-us.apache.org/repos/asf/qpid-proton.git && cd
> /main/qpid-proton && mkdir /main/qpid-proton/build
> WORKDIR /main/qpid-proton/build
> # make and install proton
> RUN cmake .. -DSYSINSTALL_BINDINGS=ON -DCMAKE_INSTALL_PREFIX=/usr
> -DSYSINSTALL_PYTHON=ON && make install
> # download libwebsockets code from
> https://github.com/warmcat/libwebsockets/commits/v2.1-stable
> RUN cd /main && git clone --branch v2.1-stable
> https://github.com/warmcat/libwebsockets.git && mkdir
> /main/libwebsockets/build
> WORKDIR /main/libwebsockets/build
> RUN cmake .. && make install
> # Clone the qpid-dispatch git repo
> RUN cd /main && git clone
> https://git-wip-us.apache.org/repos/asf/qpid-dispatch.git && mkdir
>
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996734#comment-15996734
]
Robbie Gemmell commented on QPID-7767:
--
Yes, the information there is for the older client and will give the
information Rob asked for.
The new clients equivalent is detailed in its docs, at
http://qpid.apache.org/releases/qpid-jms-0.22.0/docs/index.html#logging
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7753) Sparsely occupied message buffers may lead to java.lang.OutOfMemoryError: Direct buffer memory
[
https://issues.apache.org/jira/browse/QPID-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996705#comment-15996705
]
ASF subversion and git services commented on QPID-7753:
---
Commit 2c0e54fd1c4138845be340c2790222758bfeffbe 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=2c0e54f ]
QPID-7753: Address thread safety comments from Rob Godfrey
Refactor AMQP 1.0 message section implementations to avoid duplication
> Sparsely occupied message buffers may lead to java.lang.OutOfMemoryError:
> Direct buffer memory
> --
>
> Key: QPID-7753
> URL: https://issues.apache.org/jira/browse/QPID-7753
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1
>Reporter: Keith Wall
>Assignee: Keith Wall
> Attachments: flow-to-disk-based-on-used-direct-memory-6-0-x.diff
>
>
> Some Broker usage patterns can lead to the Broker failing with a
> "java.lang.OutOfMemoryError: Direct buffer memory" error.
> For the condition to manifest a producing application needs to use a single
> connection for the production of messages. Some messages need to be consumed
> quickly whilst others remain on the Broker. This pattern might result from:
> # the consuming application using message selectors to selectively consume
> some messages whilst leaving others on the Broker.
> # the use of 'out of order' queue types (priority/sorted etc) where lower
> priority items are left of the Broker.
> # the producing application routing messages to multiple queues and the
> consuming application draining some queues but not others.
> The problem arises owing to the buffering strategy under the IO layer.
> {{NonBlockingConnection}} allocates a {{netInputBuffer}} from pooled direct
> memory of size 256K. This buffer is used for all network reads until the
> space remaining in the buffer is less than the amount required to complete
> the AMQP frame that is currently being read, in which case a new
> netInputBuffer is allocated. The protocol layers identify the message
> payload/message headers as part of AMQP frame parsing and create a
> byte-buffer *views* onto the original input byte buffer. This byte buffer is
> retained by the store until the message is consumed. In the usage pattern
> described above, a single long lived message amongst a stream of shorted
> lived messages causes an entire 256K buffer chunk to be retained. Qpid
> cannot dispose or reuse the buffer until it is entirely unoccupied.
> The flow to disk feature is designed to prevent excessive direct memory use
> by flushing messages to disk if thresholds are breached. Flow to disk does
> not help the scenario described above because it considers the total payloads
> of live messages. Its algorithm does not consider direct memory occupancy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996665#comment-15996665
]
Kapila Arora commented on QPID-7767:
I was referring your link for generating protocol log
http://mail-archives.apache.org/mod_mbox/qpid-users/201402.mbox/%3CCACsaS94QyZbYrScWNtChgk=gn3ojdzgsl5sk5rrnvoj9izj...@mail.gmail.com%3E
is that the right link to generate the protocol log ?
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-762) Hawtio console does not show details about a connection whereas stand-alone console does
[ https://issues.apache.org/jira/browse/DISPATCH-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-762: Affects Version/s: 1.0.0 > Hawtio console does not show details about a connection whereas stand-alone > console does > > > Key: DISPATCH-762 > URL: https://issues.apache.org/jira/browse/DISPATCH-762 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.0.0 >Reporter: Jiri Danek >Priority: Minor > Attachments: vlcsnap-2017-05-04-14h05m40s322.png > > > 1) Open hawtio console and go to Overview tab. > 2) Expand the Connections node in the tree on the left > 3) Click one of the individual connections. > 4) Note that connection details in the right pane are empty! > If you find the same connection on the Entities tab of the console, the > details will be displayed there. > See the screenshot below, or a screen recording at > https://www.youtube.com/watch?v=9Hv7iNuDZQs > !vlcsnap-2017-05-04-14h05m40s322.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-762) Hawtio console does not show details about a connection whereas stand-alone console does
[ https://issues.apache.org/jira/browse/DISPATCH-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-762: Description: 1) Open hawtio console and go to Overview tab. 2) Expand the Connections node in the tree on the left 3) Click one of the individual connections. 4) Note that connection details in the right pane are empty! If you find the same connection on the Entities tab of the console, the details will be displayed there. See the screenshot below, or a screen recording at https://www.youtube.com/watch?v=9Hv7iNuDZQs !vlcsnap-2017-05-04-14h05m40s322.png! was: 1) Open hawtio console and go to Overview tab. 2) Expand the Connections node in the tree on the left 3) Click one of the individual connections. 4) Note that connection details in the right pane are empty! If you find the same connection on the Entities tab of the console, the details will be displayed there. !vlcsnap-2017-05-04-14h05m40s322.png! https://www.youtube.com/watch?v=9Hv7iNuDZQs > Hawtio console does not show details about a connection whereas stand-alone > console does > > > Key: DISPATCH-762 > URL: https://issues.apache.org/jira/browse/DISPATCH-762 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Jiri Danek >Priority: Minor > Attachments: vlcsnap-2017-05-04-14h05m40s322.png > > > 1) Open hawtio console and go to Overview tab. > 2) Expand the Connections node in the tree on the left > 3) Click one of the individual connections. > 4) Note that connection details in the right pane are empty! > If you find the same connection on the Entities tab of the console, the > details will be displayed there. > See the screenshot below, or a screen recording at > https://www.youtube.com/watch?v=9Hv7iNuDZQs > !vlcsnap-2017-05-04-14h05m40s322.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-762) Hawtio console does not show details about a connection whereas stand-alone console does
[ https://issues.apache.org/jira/browse/DISPATCH-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-762: Attachment: vlcsnap-2017-05-04-14h05m40s322.png > Hawtio console does not show details about a connection whereas stand-alone > console does > > > Key: DISPATCH-762 > URL: https://issues.apache.org/jira/browse/DISPATCH-762 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Reporter: Jiri Danek >Priority: Minor > Attachments: vlcsnap-2017-05-04-14h05m40s322.png > > > 1) Open hawtio console and go to Overview tab. > 2) Expand the Connections node in the tree on the left > 3) Click one of the individual connections. > 4) Note that connection details in the right pane are empty! > If you find the same connection on the Entities tab of the console, the > details will be displayed there. > !vlcsnap-2017-05-04-14h05m40s322.png! > https://www.youtube.com/watch?v=9Hv7iNuDZQs -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-762) Hawtio console does not show details about a connection whereas stand-alone console does
Jiri Danek created DISPATCH-762: --- Summary: Hawtio console does not show details about a connection whereas stand-alone console does Key: DISPATCH-762 URL: https://issues.apache.org/jira/browse/DISPATCH-762 Project: Qpid Dispatch Issue Type: Bug Components: Console Reporter: Jiri Danek Priority: Minor 1) Open hawtio console and go to Overview tab. 2) Expand the Connections node in the tree on the left 3) Click one of the individual connections. 4) Note that connection details in the right pane are empty! If you find the same connection on the Entities tab of the console, the details will be displayed there. !vlcsnap-2017-05-04-14h05m40s322.png! https://www.youtube.com/watch?v=9Hv7iNuDZQs -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996533#comment-15996533
]
Rob Godfrey commented on QPID-7767:
---
Do you have more of the protocol log from the client from before the error
occurred? Are there other errors before this point? I think it's entirely
possible that this is a problem on the server side, rather than the client, but
understanding how the client gets into the state where is doesn't believe there
is an endpoint associated with handle=0 would be good to know.
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996525#comment-15996525
]
Kapila Arora edited comment on QPID-7767 at 5/4/17 10:37 AM:
-
I am trying to get hold of the Latest 0.22 version code for AMQP 1.0
Connectivity .
was (Author: kapilaarora):
Let me check on the Latest JMS client and then see if this issue persist .
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996525#comment-15996525
]
Kapila Arora commented on QPID-7767:
Let me check on the Latest JMS client and then see if this issue persist .
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996519#comment-15996519
]
Robbie Gemmell commented on QPID-7767:
--
{quote}
Rob - I saw the one issue in the past for almost around similar lines.
QPID-6482
is that similar issue , where data packets comes with more= false property
instead of more = true ?
{quote}
I don't think so, but you cant really tell for sure from the information
available. Here it is saying it doesnt know what consumer they are for, there
it was saying the message segments were incorrectly indentifying whether more
content was coming.
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996511#comment-15996511
]
Robbie Gemmell commented on QPID-7767:
--
Yes, those are older than the current client releases, the components now all
have independent version numbers and releases. Those are the latest, and last,
libs released for that old client however.
You can find current information on the Qpid website. In this case, pages that
might help specifically include http://qpid.apache.org/download.html,
http://qpid.apache.org/maven.html, and
http://qpid.apache.org/components/jms/index.html as I linked to before.
Various pages will also link to http://qpid.apache.org/releases/index.html for
details on older releases the site still carrys content for, and also links to
the distribution archive for downloading even older releases should there be
some strange need to. We typically carry around 2 years of previous release
content on the site, so the old Qpid 0.32 content is actually due for removal
now and I'll add that task to some updates I'm planning.
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996503#comment-15996503
]
Kapila Arora commented on QPID-7767:
Rob - I saw the one issue in the past for almost around similar lines.
QPID-6482
is that similar issue , where data packets comes with more= false property
instead of more = true ?
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996496#comment-15996496
]
Kapila Arora commented on QPID-7767:
Hi Rob-
Here are libs , which i used to get for QPID JMS Client with version 0.32
geronimo-jms_1.1_spec-1.1.1.jar
qpid-amqp-1-0-client-0.32.jar
qpid-amqp-1-0-client-jms-0.32.jar
qpid-amqp-1-0-common-0.32.jar
slf4j-api-1.7.21.jar
you mean to say , these are not the latest ones .
will you able to point the location , from where i can download the Latest JMS
0.22 Libs or 0.11 version Libs ?
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-261) Not possible to connect to IBM's IIB AMQP broker
[
https://issues.apache.org/jira/browse/QPIDJMS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996492#comment-15996492
]
Robbie Gemmell commented on QPIDJMS-261:
[~thiengu] Can I ask how you got on with this? Did you raise a ticket with IBM,
and if so get any response? Did you change proton to try working around the
issue from the client side?
> Not possible to connect to IBM's IIB AMQP broker
>
>
> Key: QPIDJMS-261
> URL: https://issues.apache.org/jira/browse/QPIDJMS-261
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.20.0
> Environment: Java 1.8
>Reporter: Tin Nguyen
> Attachments: qpid.0.11.1.log, qpid.0.11.1.pcapng, qpid.0.20.0.log,
> qpid.0.20.0.pcapng
>
>
> With the latest 0.20 version I'm not able to connect to IBM's Integration Bus
> running AMQP implementation (afaik it's just a rip off from qpid).
> Seems like something changed with the way qpid-jms handles SASL
> authentication? It's working in 0.11.1 so I tried to look into the changes
> but there were quite a few.
> I don't have access to the IBM server but the admin told me that my client
> didn't get authenticated.
> log output from the qpid client:
> 2348 [AmqpProvider:(1):[amqp://SERVER:5672/TOPIC]] INFO
> o.a.q.j.s.SaslMechanismFinder - Best match for SASL auth was: SASL-PLAIN
> 8120 [AmqpProvider:(1):[amqp://SERVER:5672/TOPIC]] WARN
> o.a.q.j.p.a.b.AmqpResourceBuilder - Open of resource:(JmsConnectionInfo {
> ID:9088d3b3-0cba-4fb4-bb87-207872077309:1, configuredURI =
> amqp://SERVER:5672/TOPIC, connectedURI = null }) failed: AMQXR0041E: A
> connection was not authorized for channel SYSTEM.DEF.AMQP received from
> 10.2.190.60. MQRC 2035 MQRC_NOT_AUTHORIZED [condition =
> amqp:unauthorized-access]
> 8121 [AmqpProvider:(1):[amqp://SERVER:5672/TOPIC]] INFO
> o.a.q.j.p.a.AmqpProvider - Transport failed: An existing connection was
> forcibly closed by the remote host
> Caught exception, exiting.
> javax.jms.JMSSecurityException: AMQXR0041E: A connection was not authorized
> for channel SYSTEM.DEF.AMQP received from 10.2.10.60. MQRC 2035
> MQRC_NOT_AUTHORIZED [condition = amqp:unauthorized-access]
> LOGS on IBM server
> 01/17/2017 01:40:21 PM - Process(51975.7) User(mqm) Program(java)
> Host(SERVER) Installation(Installation1)
> VRMF(9.0.0.0) QMgr(UUFNLB1E)
>
> AMQ5534: User ID 'hadoop' authentication failed
> EXPLANATION:
> The user ID and password supplied by the 'AMQP' program could not be
> authenticated.
> Additional information: 'N/A'.
> ACTION:
> Ensure that the correct user ID and password are provided by the application.
> Ensure that the authentication repository is correctly configured. Look at
> previous error messages for any additional information.
> - amqzfuca.c : 4486
> ---
> 01/17/2017 01:40:21 PM - Process(51975.7) User(mqm) Program(java)
> Host(SERVER) Installation(Installation1)
> VRMF(9.0.0.0) QMgr(UUFNLB1E)
>
> AMQ5542: The failed authentication check was caused by the queue manager
> CONNAUTH CHCKCLNT(REQDADM) configuration.
> EXPLANATION:
> The user ID 'hadoop' and its password were checked because the queue manager
> connection authority (CONNAUTH) configuration refers to an authentication
> information (AUTHINFO) object named 'SYSTEM.DEFAULT.AUTHINFO.IDPWOS' with
> CHCKCLNT(REQDADM).
> This message accompanies a previous error to clarify the reason for the user
> ID
> and password check.
> ACTION:
> Refer to the previous error for more information.
> Ensure that a password is specified by the client application and that the
> password is correct for the user ID. The authentication configuration of the
> queue manager connection determines the user ID repository. For example, the
> local operating system user database or an LDAP server.
> If the CHCKCLNT setting is OPTIONAL, the authentication check can be avoided
> by
> not passing a user ID across the channel. For example, by omitting the MQCSP
> structure from the client MQCONNX API call.
> To avoid the authentication check, you can amend the authentication
> configuration of the queue manager connection, but you should generally not
> allow unauthenticated remote access.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996467#comment-15996467
]
Robbie Gemmell commented on QPID-7767:
--
You appear to be using the old 'amqp-1-0-client-jms' module from the Qpid 0.32
release. That client is no longer maintained by the project, and was succeeded
a couple of years ago by a newer client.
That said, from doing a quick grep of its code, it seems likely its hitting
this line:
http://svn.apache.org/viewvc/qpid/tags/0.32/qpid/java/amqp-1-0-common/src/main/java/org/apache/qpid/amqp_1_0/transport/SessionEndpoint.java?annotate=1667701#l388,
which is essentially saying the session recieved a message for a consumer it
is unaware of (the 'handle' referred to didnt yield a link) at the time.
Details of the newer AMQP 1.0 JMS client are at
http://qpid.apache.org/components/jms/index.html. Its current release is
0.22.0, though I note your mention of IBM in the JIRA details. If you are also
trying to connect to an IBM server and in addition to the Azure Service Bus,
you could hit a server bug noted in QPIDJMS-261 and QPIDJMS-287. If so, youd
possibly need to try the older 0.11.1 release, where subtle differences in
client behaviour (which newer client releases can't easily mimmick) effectively
worked around the server issue.
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapila Arora updated QPID-7767:
---
Priority: Critical (was: Major)
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
>Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapila Arora updated QPID-7767:
---
Attachment: Qpid_error_log.txt
You can start looking on this log file . We are getting this issue from Line #
389 .
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7753) Sparsely occupied message buffers may lead to java.lang.OutOfMemoryError: Direct buffer memory
[
https://issues.apache.org/jira/browse/QPID-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7753:
-
Attachment: flow-to-disk-based-on-used-direct-memory-6-0-x.diff
Attached a patch for 6.0.x branch with a work around triggering "flow to disk"
based on direct memory consumption. This prevents the issue from building up.
The changes are already committed into 6.0.x branch under revision
[c1284ac30f1c83261089dd4627f48f29509fddb8|https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=c1284ac].
> Sparsely occupied message buffers may lead to java.lang.OutOfMemoryError:
> Direct buffer memory
> --
>
> Key: QPID-7753
> URL: https://issues.apache.org/jira/browse/QPID-7753
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1
>Reporter: Keith Wall
>Assignee: Keith Wall
> Attachments: flow-to-disk-based-on-used-direct-memory-6-0-x.diff
>
>
> Some Broker usage patterns can lead to the Broker failing with a
> "java.lang.OutOfMemoryError: Direct buffer memory" error.
> For the condition to manifest a producing application needs to use a single
> connection for the production of messages. Some messages need to be consumed
> quickly whilst others remain on the Broker. This pattern might result from:
> # the consuming application using message selectors to selectively consume
> some messages whilst leaving others on the Broker.
> # the use of 'out of order' queue types (priority/sorted etc) where lower
> priority items are left of the Broker.
> # the producing application routing messages to multiple queues and the
> consuming application draining some queues but not others.
> The problem arises owing to the buffering strategy under the IO layer.
> {{NonBlockingConnection}} allocates a {{netInputBuffer}} from pooled direct
> memory of size 256K. This buffer is used for all network reads until the
> space remaining in the buffer is less than the amount required to complete
> the AMQP frame that is currently being read, in which case a new
> netInputBuffer is allocated. The protocol layers identify the message
> payload/message headers as part of AMQP frame parsing and create a
> byte-buffer *views* onto the original input byte buffer. This byte buffer is
> retained by the store until the message is consumed. In the usage pattern
> described above, a single long lived message amongst a stream of shorted
> lived messages causes an entire 256K buffer chunk to be retained. Qpid
> cannot dispose or reuse the buffer until it is entirely unoccupied.
> The flow to disk feature is designed to prevent excessive direct memory use
> by flushing messages to disk if thresholds are breached. Flow to disk does
> not help the scenario described above because it considers the total payloads
> of live messages. Its algorithm does not consider direct memory occupancy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7763) [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold
[ https://issues.apache.org/jira/browse/QPID-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996418#comment-15996418 ] ASF subversion and git services commented on QPID-7763: --- Commit 0169136fc01628dbbf064ffe7a3aafaac200d319 in qpid-broker-j's branch refs/heads/6.0.x from [~lorenz.quack] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=0169136 ] QPID-7763: [Java Broker] Fix mock in unit tests (cherry picked from commit bc9bf4b6c476cdbde04027b447e74b68aa8d0919) > [Java Broker] Flow to disk if allocated direct memory exceeds broker wide > broker.flowToDiskThreshold > > > Key: QPID-7763 > URL: https://issues.apache.org/jira/browse/QPID-7763 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Lorenz Quack > > Currently the broker.flowToDiskThreshold is compared against the size used by > messages on queues. > However, the intent was to have a mechanism for preventing the broker going > out of direct memory. For this it is much more interesting to observe how > much direct memory the QpidByteBuffers use. The two numbers can easily differ > since the QBB can be sparsely populated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7763) [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold
[ https://issues.apache.org/jira/browse/QPID-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996417#comment-15996417 ] ASF subversion and git services commented on QPID-7763: --- Commit 2b91b4419841fb84bb97028d6995f7f125570412 in qpid-broker-j's branch refs/heads/6.0.x from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=2b91b44 ] QPID-7763: [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold (cherry picked from commit 07ea26e7b8fdc24621fcde04949df633186fa5a0) > [Java Broker] Flow to disk if allocated direct memory exceeds broker wide > broker.flowToDiskThreshold > > > Key: QPID-7763 > URL: https://issues.apache.org/jira/browse/QPID-7763 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Lorenz Quack > > Currently the broker.flowToDiskThreshold is compared against the size used by > messages on queues. > However, the intent was to have a mechanism for preventing the broker going > out of direct memory. For this it is much more interesting to observe how > much direct memory the QpidByteBuffers use. The two numbers can easily differ > since the QBB can be sparsely populated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapila Arora updated QPID-7767:
---
Environment:
Source - Linux machine on softLayer Cloud . IBM Integration Bus Version 9.0.0.2
, use the Apache qpid JMS 0.32 version as AMQP Client to receive the data
packets on AMQP Channel .
Target - Azure Service bus on Public cloud exposed with AMQP Server .
was:
Source - Linux machine on softLayer Cloud . IBM Integration Bus Version 9.0.0.2
, use the apache qpid JMS 0.32 version as AMQP Client to receive the data
Target - Azure Service bus on Public cloud exposed with AMQP Server .
Fix Version/s: 0.32
Component/s: (was: Java Common)
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
> Fix For: 0.32
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996403#comment-15996403
]
Kapila Arora commented on QPID-7767:
This is really important and critical issue , we are struggling with AMQP
Client . Please suggest
> Unknown endpoint Transfer issue on AMQP Connection
> --
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.32
> Environment: Source - Linux machine on softLayer Cloud . IBM
> Integration Bus Version 9.0.0.2 , use the Apache qpid JMS 0.32 version as
> AMQP Client to receive the data packets on AMQP Channel .
> Target - Azure Service bus on Public cloud exposed with AMQP Server .
>Reporter: Kapila Arora
> Fix For: 0.32
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7767) Unknown endpoint Transfer issue on AMQP Connection
Kapila Arora created QPID-7767:
--
Summary: Unknown endpoint Transfer issue on AMQP Connection
Key: QPID-7767
URL: https://issues.apache.org/jira/browse/QPID-7767
Project: Qpid
Issue Type: Bug
Components: Java Client, Java Common
Affects Versions: 0.32
Environment: Source - Linux machine on softLayer Cloud . IBM
Integration Bus Version 9.0.0.2 , use the apache qpid JMS 0.32 version as AMQP
Client to receive the data
Target - Azure Service bus on Public cloud exposed with AMQP Server .
Reporter: Kapila Arora
Getting Errors in the AMQP Client
2017-05-03 06:45:15.048212 Unknown endpoint
Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
Data Packets
Unknown endpoint
Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
2017-05-03 06:45:15.396212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7763) [Java Broker] Flow to disk if allocated direct memory exceeds broker wide broker.flowToDiskThreshold
[ https://issues.apache.org/jira/browse/QPID-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996396#comment-15996396 ] ASF subversion and git services commented on QPID-7763: --- Commit 6efc91066968e4226a905bc903f2b2d228843acb in qpid-broker-j's branch refs/heads/6.1.x from [~alex.rufous] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=6efc910 ] QPID-7763: Fix failing test and dispose end of frame buffer in amqp 0-9 > [Java Broker] Flow to disk if allocated direct memory exceeds broker wide > broker.flowToDiskThreshold > > > Key: QPID-7763 > URL: https://issues.apache.org/jira/browse/QPID-7763 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Lorenz Quack > > Currently the broker.flowToDiskThreshold is compared against the size used by > messages on queues. > However, the intent was to have a mechanism for preventing the broker going > out of direct memory. For this it is much more interesting to observe how > much direct memory the QpidByteBuffers use. The two numbers can easily differ > since the QBB can be sparsely populated. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-757) Qpid Dispatch does not compile under Ubuntu
[
https://issues.apache.org/jira/browse/DISPATCH-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996347#comment-15996347
]
Jiri Danek commented on DISPATCH-757:
-
In my travis build (in Docker) it seems the test failures are essentially
random. If I run the docker build locally at my laptop, it succeeds in about 50
% without any test failure. On travis, the success rate is lower. Maybe because
of travis performance.
I experienced similar issues before, see DISPATCH-480, I believed this to be
caused by timeouts.
> Qpid Dispatch does not compile under Ubuntu
> ---
>
> Key: DISPATCH-757
> URL: https://issues.apache.org/jira/browse/DISPATCH-757
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Alan Conway
> Fix For: 1.0.0
>
>
> Got the following error message when compiling qpid-dispatch master on
> ubuntu:latest.
> The following is the compile error -
> {noformat}
> [ 66%] Building C object src/CMakeFiles/qpid-dispatch.dir/trace_mask.c.o
> [ 67%] Building C object
> src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o
> /main/qpid-dispatch/src/http-libwebsockets.c: In function 'logger':
> /main/qpid-dispatch/src/http-libwebsockets.c:54:23: error: implicit
> declaration of function 'isspace' [-Werror=implicit-function-declaration]
> while (len > 1 && isspace(line[len-1])) { /* Strip trailing newline */
>^
> cc1: all warnings being treated as errors
> src/CMakeFiles/qpid-dispatch.dir/build.make:1184: recipe for target
> 'src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o' failed
> make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o] Error 1
> CMakeFiles/Makefile2:981: recipe for target
> 'src/CMakeFiles/qpid-dispatch.dir/all' failed
> make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
> make: *** [all] Error 2
> Makefile:138: recipe for target 'all' failed
> The command '/bin/sh -c cmake .. -DCMAKE_INSTALL_PREFIX=/usr && make install'
> returned a non-zero code: 2
> [gmurthy@localhost dockerfiles]$
> {noformat}
> The following is the docker file used
> {noformat}
> #
> # Licensed to the Apache Software Foundation (ASF) under one
> # or more contributor license agreements. See the NOTICE file
> # distributed with this work for additional information
> # regarding copyright ownership. The ASF licenses this file
> # to you under the Apache License, Version 2.0 (the
> # "License"); you may not use this file except in compliance
> # with the License. You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing,
> # software distributed under the License is distributed on an
> # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> # KIND, either express or implied. See the License for the
> # specific language governing permissions and limitations
> # under the License.
> #
> # Gets the latest Ubuntu from dockerhub
> FROM ubuntu:latest
> MAINTAINER "dev@qpid.apache.org"
> # Install all the required packages. Some in this list were picked off from
> proton's INSTALL.md
> (https://github.com/apache/qpid-proton/blob/master/INSTALL.md) and the rest
> are from dispatch (https://github.com/apache/qpid-dispatch/blob/master/README)
> RUN apt-get update && apt-get -y install gcc cmake cmake-curses-gui uuid-dev
> libssl-dev libsasl2-2 libsasl2-dev sasl2-bin swig python-dev ruby-dev
> libperl-dev git make doxygen valgrind emacs libuv1 libuv1-dev
> # Create a main directory and clone the qpid-proton repo from github
> RUN mkdir /main && cd /main && git clone
> https://git-wip-us.apache.org/repos/asf/qpid-proton.git && cd
> /main/qpid-proton && mkdir /main/qpid-proton/build
> WORKDIR /main/qpid-proton/build
> # make and install proton
> RUN cmake .. -DSYSINSTALL_BINDINGS=ON -DCMAKE_INSTALL_PREFIX=/usr
> -DSYSINSTALL_PYTHON=ON && make install
> # download libwebsockets code from
> https://github.com/warmcat/libwebsockets/commits/v2.1-stable
> RUN cd /main && git clone --branch v2.1-stable
> https://github.com/warmcat/libwebsockets.git && mkdir
> /main/libwebsockets/build
> WORKDIR /main/libwebsockets/build
> RUN cmake .. && make install
> # Clone the qpid-dispatch git repo
> RUN cd /main && git clone
> https://git-wip-us.apache.org/repos/asf/qpid-dispatch.git && mkdir
> /main/qpid-dispatch/build
> WORKDIR /main/qpid-dispatch/build
> RUN cmake .. -DCMAKE_INSTALL_PREFIX=/usr && make install
> # Add site-packages to the PYTHONPATH environment variable. This is because
> Ubuntu does not list the site-packages folder in the sys.path
> ENV PYTHONPATH=/usr/lib/python2.7/site-packages
> # Uncomment the following line if you would like to run all the dispatch unit
> tests and system
[jira] [Commented] (QPID-7639) Implement large transaction guard restricting direct memory consumption by messages from uncommitted transactions on the connection
[ https://issues.apache.org/jira/browse/QPID-7639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996298#comment-15996298 ] ASF subversion and git services commented on QPID-7639: --- Commit 54b58c603acc88cf3bbbdb20fd71cefc159c2546 in qpid-broker-j's branch refs/heads/master from [~k-wall] [ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=54b58c6 ] QPID-7639: Correct participle flown => flowed in code and documentation > Implement large transaction guard restricting direct memory consumption by > messages from uncommitted transactions on the connection > > > Key: QPID-7639 > URL: https://issues.apache.org/jira/browse/QPID-7639 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: qpid-java-broker-7.0.0 > > > The current implementation of AMQP 0-x layers restrict the memory consumption > by messages from uncommitted transactions on the session level. > We need to change the existing implementations to apply the limit per > connection and add implementation for AMQP 1.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
