[jira] [Created] (PROTON-1545) qpid-proton doesn't build with the latest cmake
Simon Lees (SUSE) created PROTON-1545: - Summary: qpid-proton doesn't build with the latest cmake Key: PROTON-1545 URL: https://issues.apache.org/jira/browse/PROTON-1545 Project: Qpid Proton Issue Type: Bug Components: perl-binding Environment: Linux (openSUSE) Reporter: Simon Lees (SUSE) Attachments: qpid-proton-cmake-fixes.patch CMake 3.9 has a slight incompatibility affecting the name of the perl binding library, the attached patch fixes that as well as swapping to swig_add_library rather then swig_add_module as the later is depreciated. -- 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-1544) go lang binding transaction support
ivy created PROTON-1544: --- Summary: go lang binding transaction support Key: PROTON-1544 URL: https://issues.apache.org/jira/browse/PROTON-1544 Project: Qpid Proton Issue Type: Bug Reporter: ivy Does the go lang binding support AMQP transactions, If it does, is there any documentation on how to use it. If not are there plans to support it? -- 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-1477) Problem building qpid-proton 0.17.0 in Fedora rawhide
[ https://issues.apache.org/jira/browse/PROTON-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131528#comment-16131528 ] Justin Ross commented on PROTON-1477: - [~iboverma], this doesn't reproduce for me. I was able to build 0.17.0 with the perl binding enabled on F26 and current rawhide. > Problem building qpid-proton 0.17.0 in Fedora rawhide > - > > Key: PROTON-1477 > URL: https://issues.apache.org/jira/browse/PROTON-1477 > Project: Qpid Proton > Issue Type: Bug > Components: build > Environment: x86_64 >Reporter: Irina Boverman >Assignee: Justin Ross > Fix For: proton-c-0.18.0 > > > [ 39%] Swig source > cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && > /usr/bin/cmake -E make_directory > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl > make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0' > cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && > /usr/bin/swig -perl -outdir > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl -shadow > -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/src > -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/include -I/usr/include > -I/usr/lib64/perl5/CORE -o > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perlPERL_wrap.c > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perl.i > make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0' > cc1plus: error: -Wformat-security ignored without -Wformat > [-Werror=format-security] > cc1plus: all warnings being treated as errors > make[2]: *** > [proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/build.make:66: > proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/binary.cpp.o] Error 1 -- 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-1175) Document BlockingConnection resource cleanup
[ https://issues.apache.org/jira/browse/PROTON-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross resolved PROTON-1175. - Resolution: Fixed > Document BlockingConnection resource cleanup > > > Key: PROTON-1175 > URL: https://issues.apache.org/jira/browse/PROTON-1175 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Cliff Jansen >Assignee: Justin Ross > Labels: docs > Fix For: proton-c-0.18.0 > > > The documentation is silent on resource cleanup for BlockingConnections. > Currently if the BlockingConnection is not closed, the file descriptors and > other reactor machinery are leaked. > Standard Python techniques should be used to ensure resource clean up > (try..finally blocks etc.) > Only the sync_client example hints this might be desirable, let alone > necessary. -- 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-209) Update README file(s) to more specific about required versions of tools
[ https://issues.apache.org/jira/browse/PROTON-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131494#comment-16131494 ] Justin Ross commented on PROTON-209: (Asking this in the right place now.) [~aconway], what's the minimum Ruby version going to be? > Update README file(s) to more specific about required versions of tools > --- > > Key: PROTON-209 > URL: https://issues.apache.org/jira/browse/PROTON-209 > Project: Qpid Proton > Issue Type: Task > Components: proton-c >Affects Versions: 0.3 >Reporter: Philip Harvey >Assignee: Justin Ross >Priority: Minor > Labels: docs > Fix For: proton-c-0.18.0 > > > We should be more explicit about which version of the following tools are > required by Proton, either in the top level README or in READMEs in the > relevant sub-folders: > - Python (see PROTON-199). > - Swig > - cmake? (the required version is specified in the CMakeLists.txt files but > maybe it would be polite to mention in the README too). > - Maven? (or maybe we can omit this for same reasons as cmake version) > - possibly others, e.g. openssl, gcc, epydoc, Perl, Ruby etc. -- 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-1175) Document BlockingConnection resource cleanup
[ https://issues.apache.org/jira/browse/PROTON-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131492#comment-16131492 ] Justin Ross commented on PROTON-1175: - [~aconway], what's the Ruby minimum version going to be? > Document BlockingConnection resource cleanup > > > Key: PROTON-1175 > URL: https://issues.apache.org/jira/browse/PROTON-1175 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Cliff Jansen >Assignee: Justin Ross > Labels: docs > Fix For: proton-c-0.18.0 > > > The documentation is silent on resource cleanup for BlockingConnections. > Currently if the BlockingConnection is not closed, the file descriptors and > other reactor machinery are leaked. > Standard Python techniques should be used to ensure resource clean up > (try..finally blocks etc.) > Only the sync_client example hints this might be desirable, let alone > necessary. -- 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] [Issue Comment Deleted] (PROTON-1175) Document BlockingConnection resource cleanup
[ https://issues.apache.org/jira/browse/PROTON-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1175: Comment: was deleted (was: [~aconway], what's the Ruby minimum version going to be?) > Document BlockingConnection resource cleanup > > > Key: PROTON-1175 > URL: https://issues.apache.org/jira/browse/PROTON-1175 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Cliff Jansen >Assignee: Justin Ross > Labels: docs > Fix For: proton-c-0.18.0 > > > The documentation is silent on resource cleanup for BlockingConnections. > Currently if the BlockingConnection is not closed, the file descriptors and > other reactor machinery are leaked. > Standard Python techniques should be used to ensure resource clean up > (try..finally blocks etc.) > Only the sync_client example hints this might be desirable, let alone > necessary. -- 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-1175) Document BlockingConnection resource cleanup
[ https://issues.apache.org/jira/browse/PROTON-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131489#comment-16131489 ] ASF subversion and git services commented on PROTON-1175: - Commit 2449169bba068111b90955dcfbedf4f4554305a7 in qpid-proton's branch refs/heads/master from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=2449169 ] PROTON-1175: Document BlockingConnection resource cleanup > Document BlockingConnection resource cleanup > > > Key: PROTON-1175 > URL: https://issues.apache.org/jira/browse/PROTON-1175 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: 0.12.0 >Reporter: Cliff Jansen >Assignee: Justin Ross > Labels: docs > Fix For: proton-c-0.18.0 > > > The documentation is silent on resource cleanup for BlockingConnections. > Currently if the BlockingConnection is not closed, the file descriptors and > other reactor machinery are leaked. > Standard Python techniques should be used to ensure resource clean up > (try..finally blocks etc.) > Only the sync_client example hints this might be desirable, let alone > necessary. -- 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-1543) Various doc improvements
[ https://issues.apache.org/jira/browse/PROTON-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131490#comment-16131490 ] ASF subversion and git services commented on PROTON-1543: - Commit 20da10d10d6597764c8f651c451bced427dbb96c in qpid-proton's branch refs/heads/master from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=20da10d ] PROTON-1543: Copyedit the readme and install docs > Various doc improvements > > > Key: PROTON-1543 > URL: https://issues.apache.org/jira/browse/PROTON-1543 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: proton-c-0.18.0 > > -- 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-209) Update README file(s) to more specific about required versions of tools
[ https://issues.apache.org/jira/browse/PROTON-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131491#comment-16131491 ] ASF subversion and git services commented on PROTON-209: Commit 8c3ba56b8e7dfe92fb23c409cb64e960dacae26a in qpid-proton's branch refs/heads/master from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=8c3ba56 ] PROTON-209: Add a list of dependencies with tested minimum versions where they are known > Update README file(s) to more specific about required versions of tools > --- > > Key: PROTON-209 > URL: https://issues.apache.org/jira/browse/PROTON-209 > Project: Qpid Proton > Issue Type: Task > Components: proton-c >Affects Versions: 0.3 >Reporter: Philip Harvey >Assignee: Justin Ross >Priority: Minor > Labels: docs > Fix For: proton-c-0.18.0 > > > We should be more explicit about which version of the following tools are > required by Proton, either in the top level README or in READMEs in the > relevant sub-folders: > - Python (see PROTON-199). > - Swig > - cmake? (the required version is specified in the CMakeLists.txt files but > maybe it would be polite to mention in the README too). > - Maven? (or maybe we can omit this for same reasons as cmake version) > - possibly others, e.g. openssl, gcc, epydoc, Perl, Ruby etc. -- 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-1347) Container prints to stderr on connection timed out
[ https://issues.apache.org/jira/browse/PROTON-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131465#comment-16131465 ] ASF subversion and git services commented on PROTON-1347: - Commit 4657d9fbd4ac999ce3aa6c790d2a80eb9334709d in qpid-proton's branch refs/heads/master from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4657d9f ] PROTON-1347: For Python 2.6, define NullHandler if the logging module doesn't have it > Container prints to stderr on connection timed out > -- > > Key: PROTON-1347 > URL: https://issues.apache.org/jira/browse/PROTON-1347 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: 0.14.0 >Reporter: Mike Bonnet >Assignee: Justin Ross >Priority: Minor > Fix For: proton-c-0.18.0 > > > If you're using a Container to connect to a broker, and the broker is > unresponsive and the connection times out, this is printed to stderr: > ERROR:root:proton:io: recv: Connection timed out > Libraries generally shouldn't print directly to the console, especially when > the error can be handled in the code. -- 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] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1542: Fix Version/s: proton-c-0.18.0 > hostname should be set on sasl-init > --- > > Key: PROTON-1542 > URL: https://issues.apache.org/jira/browse/PROTON-1542 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c, python-binding, > ruby-binding >Reporter: Gordon Sim > Fix For: proton-c-0.18.0 > > > For a multi-tenant service/server, where each tenant has its own user base, > the hostname in the sasl-init frame provides a convenient way of determining > the correct tenant to authenticate for. > At present this is not set for any proton-c based client. It is similar to > the SNI information included in the TLS layer initiation (if such a layer is > in use). -- 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] (QPIDIT-88) Need to specify supported AMQP types per shim
Chuck Rolke created QPIDIT-88: - Summary: Need to specify supported AMQP types per shim Key: QPIDIT-88 URL: https://issues.apache.org/jira/browse/QPIDIT-88 Project: Apache QPID Interoperability Test Suite Issue Type: Bug Reporter: Chuck Rolke The AMQP.Net Lite (Lite) shim does not support any of the AMQP Decimal types. Tests may be run with _--exclude-type decimal128 --exclude-type decimal64 --exclude-type decimal32_ to avoid the failures but that applies to all sender/receiver shim pairs and not just to the Lite shim. When the test runs Lite Sender against Lite Receiver it fails in a reasonable amout of time. But with Lite Sender and ProtonCpp Receiver the test times out after 800 seconds before failing. The Lite Sender throws right away but the Cpp Receiver waits dutifully for the message stream. -- 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-7892) [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since java.io.tmpdir pointed at directory containing parentheses
[
https://issues.apache.org/jira/browse/QPID-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7892:
-
Description:
Currently on master the following tests are failing on Apache CI. The fails
started at the point {{$\{java.io.tmpdir\}}} was reassigned to the Jenkins
job's workspace directory. The workspace directory contains a pair of
parentheses. The following tests are affected:
{noformat}
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testSequentialRollover
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverRescanLimit
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverWithFile
{noformat}
I can see the issue is occurring because the regex match within
{{org.apache.qpid.server.logging.logback.RollingPolicyDecorator.ScanTask#scan}}
is treating the parentheses as regex meta characters and this is causing the
test to fail.
I do not yet understand if this issue is a simple a test one, or whether core
code is affected.
{{Pattern.escape}} can be used to escape regex metacharacters. Perhaps it
should be used??
was:
Currently on master the following tests are failing on Apache CI. The fails
started at the point ${java.io.tmpdir} was reassigned to the Jenkins job's
workspace directory. The workspace directory contains a pair of parentheses.
{noformat}
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testSequentialRollover
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverRescanLimit
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverWithFile
{noformat}
I can see the issue is occurring because the regex match
withinorg.apache.qpid.server.logging.logback.RollingPolicyDecorator.ScanTask#scan
is treating the parentheses as regex meta characters and this is causing the
test to fail.
I do not yet understand if this issue is a simple a test one, or whether core
code is affected.
Pattern.escape can be used to escape regex metacharacters. Perhaps it should be
used??
> [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since
> java.io.tmpdir pointed at directory containing parentheses
> -
>
> Key: QPID-7892
> URL: https://issues.apache.org/jira/browse/QPID-7892
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Tests
>Reporter: Keith Wall
>Priority: Minor
>
> Currently on master the following tests are failing on Apache CI. The fails
> started at the point {{$\{java.io.tmpdir\}}} was reassigned to the Jenkins
> job's workspace directory. The workspace directory contains a pair of
> parentheses. The following tests are affected:
> {noformat}
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testSequentialRollover
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverRescanLimit
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverWithFile
> {noformat}
> I can see the issue is occurring because the regex match within
> {{org.apache.qpid.server.logging.logback.RollingPolicyDecorator.ScanTask#scan}}
> is treating the parentheses as regex meta characters and this is causing the
> test to fail.
> I do not yet understand if this issue is a simple a test one, or whether core
> code is affected.
> {{Pattern.escape}} can be used to escape regex metacharacters. Perhaps it
> should be used??
--
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-7892) [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since java.io.tmpdir pointed at directory containing parentheses
[
https://issues.apache.org/jira/browse/QPID-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7892:
-
Component/s: Java Tests
> [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since
> java.io.tmpdir pointed at directory containing parentheses
> -
>
> Key: QPID-7892
> URL: https://issues.apache.org/jira/browse/QPID-7892
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Tests
>Reporter: Keith Wall
>Priority: Minor
>
> Currently on master the following tests are failing on Apache CI. The fails
> started at the point {{$\{java.io.tmpdir\}}} was reassigned to the Jenkins
> job's workspace directory. The workspace directory contains a pair of
> parentheses. The following tests are affected:
> {noformat}
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testSequentialRollover
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverRescanLimit
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverWithFile
> {noformat}
> I can see the issue is occurring because the regex match within
> {{org.apache.qpid.server.logging.logback.RollingPolicyDecorator.ScanTask#scan}}
> is treating the parentheses as regex meta characters and this is causing the
> test to fail.
> I do not yet understand if this issue is a simple a test one, or whether core
> code is affected.
> {{Pattern.escape}} can be used to escape regex metacharacters. Perhaps it
> should be used??
--
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] (QPID-7892) [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since java.io.tmpdir pointed at directory contain parentheses
Keith Wall created QPID-7892:
Summary: [Java Broker] Qpid Logback plugin RollingPolicyDecorator
tests fail since java.io.tmpdir pointed at directory contain parentheses
Key: QPID-7892
URL: https://issues.apache.org/jira/browse/QPID-7892
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Keith Wall
Currently on master the following tests are failing on Apache CI. The fails
started at the point ${java.io.tmpdir} was reassigned to the Jenkins job's
workspace directory. The workspace directory contains a pair of parentheses.
{noformat}
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testSequentialRollover
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverRescanLimit
org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverWithFile
{noformat}
I can see the issue is occurring because the regex match
withinorg.apache.qpid.server.logging.logback.RollingPolicyDecorator.ScanTask#scan
is treating the parentheses as regex meta characters and this is causing the
test to fail.
I do not yet understand if this issue is a simple a test one, or whether core
code is affected.
Pattern.escape can be used to escape regex metacharacters. Perhaps it should be
used??
--
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-7892) [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since java.io.tmpdir pointed at directory containing parentheses
[
https://issues.apache.org/jira/browse/QPID-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7892:
-
Summary: [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests
fail since java.io.tmpdir pointed at directory containing parentheses (was:
[Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since
java.io.tmpdir pointed at directory contain parentheses )
> [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since
> java.io.tmpdir pointed at directory containing parentheses
> -
>
> Key: QPID-7892
> URL: https://issues.apache.org/jira/browse/QPID-7892
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Keith Wall
>
> Currently on master the following tests are failing on Apache CI. The fails
> started at the point ${java.io.tmpdir} was reassigned to the Jenkins job's
> workspace directory. The workspace directory contains a pair of
> parentheses.
> {noformat}
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testSequentialRollover
>
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverRescanLimit
>
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverWithFile
> {noformat}
> I can see the issue is occurring because the regex match
> withinorg.apache.qpid.server.logging.logback.RollingPolicyDecorator.ScanTask#scan
> is treating the parentheses as regex meta characters and this is causing the
> test to fail.
> I do not yet understand if this issue is a simple a test one, or whether core
> code is affected.
> Pattern.escape can be used to escape regex metacharacters. Perhaps it should
> be used??
--
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-7892) [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since java.io.tmpdir pointed at directory containing parentheses
[
https://issues.apache.org/jira/browse/QPID-7892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7892:
-
Priority: Minor (was: Major)
> [Java Broker] Qpid Logback plugin RollingPolicyDecorator tests fail since
> java.io.tmpdir pointed at directory containing parentheses
> -
>
> Key: QPID-7892
> URL: https://issues.apache.org/jira/browse/QPID-7892
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Keith Wall
>Priority: Minor
>
> Currently on master the following tests are failing on Apache CI. The fails
> started at the point ${java.io.tmpdir} was reassigned to the Jenkins job's
> workspace directory. The workspace directory contains a pair of
> parentheses.
> {noformat}
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testSequentialRollover
>
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverRescanLimit
>
> org.apache.qpid.server.logging.logback.RollingPolicyDecoratorTest.testRolloverWithFile
> {noformat}
> I can see the issue is occurring because the regex match
> withinorg.apache.qpid.server.logging.logback.RollingPolicyDecorator.ScanTask#scan
> is treating the parentheses as regex meta characters and this is causing the
> test to fail.
> I do not yet understand if this issue is a simple a test one, or whether core
> code is affected.
> Pattern.escape can be used to escape regex metacharacters. Perhaps it should
> be used??
--
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-731) Support wildcard tenant vhosts in address prefix configuration
[
https://issues.apache.org/jira/browse/DISPATCH-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130395#comment-16130395
]
ASF subversion and git services commented on DISPATCH-731:
--
Commit 6def321f54b7e5baf559a51ab75cffd1c730e9db in qpid-dispatch's branch
refs/heads/master from Kenneth Giusti
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=6def321 ]
DISPATCH-731: remove noisy debug log messages
> Support wildcard tenant vhosts in address prefix configuration
> --
>
> Key: DISPATCH-731
> URL: https://issues.apache.org/jira/browse/DISPATCH-731
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Management Agent
>Affects Versions: 0.7.0
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: 1.0.0
>
>
> When specifying address prefix patterns it should be possible to use a
> wildcard match for the vhost. Example:
> address {
> prefix: a_prefix # matches current vhost (from open frame)
> }
> address {
> prefix: /my-vhost.com/other_prefix # matched only if vhost=my-vhost
> }
> address {
> prefix: /*.#.domain1.com/prefix_3 # matched if vhost ends with
> domain1.com
> }
> address {
> prefix: /my.vhost.*.com/prefix_4 #matched if vhost starts with
> 'my.vhost', has a single wildcard component, and ends with '.com'
> }
> Or something like that, I think.
--
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] (PROTON-1477) Problem building qpid-proton 0.17.0 in Fedora rawhide
[ https://issues.apache.org/jira/browse/PROTON-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1477: Fix Version/s: proton-c-0.18.0 > Problem building qpid-proton 0.17.0 in Fedora rawhide > - > > Key: PROTON-1477 > URL: https://issues.apache.org/jira/browse/PROTON-1477 > Project: Qpid Proton > Issue Type: Bug > Components: build > Environment: x86_64 >Reporter: Irina Boverman >Assignee: Justin Ross > Fix For: proton-c-0.18.0 > > > [ 39%] Swig source > cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && > /usr/bin/cmake -E make_directory > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl > make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0' > cd /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl && > /usr/bin/swig -perl -outdir > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl -shadow > -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/src > -I/builddir/build/BUILD/qpid-proton-0.17.0/proton-c/include -I/usr/include > -I/usr/lib64/perl5/CORE -o > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perlPERL_wrap.c > /builddir/build/BUILD/qpid-proton-0.17.0/proton-c/bindings/perl/perl.i > make[2]: Leaving directory '/builddir/build/BUILD/qpid-proton-0.17.0' > cc1plus: error: -Wformat-security ignored without -Wformat > [-Werror=format-security] > cc1plus: all warnings being treated as errors > make[2]: *** > [proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/build.make:66: > proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/binary.cpp.o] Error 1 -- 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-1543) Various doc improvements
Justin Ross created PROTON-1543: --- Summary: Various doc improvements Key: PROTON-1543 URL: https://issues.apache.org/jira/browse/PROTON-1543 Project: Qpid Proton Issue Type: Improvement Reporter: Justin Ross Assignee: Justin Ross Fix For: proton-c-0.18.0 -- 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-209) Three+ router test is needed in the system test suite.
[ https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130283#comment-16130283 ] ASF subversion and git services commented on DISPATCH-209: -- Commit 835f14d0f775063c45912e907f0d2a2d51c9feca in qpid-dispatch's branch refs/heads/master from [~mgoulish] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=835f14d ] DISPATCH-209 : uniq addresses used by tests > Three+ router test is needed in the system test suite. > -- > > Key: DISPATCH-209 > URL: https://issues.apache.org/jira/browse/DISPATCH-209 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Tests >Reporter: Ted Ross >Assignee: michael goulish > Fix For: 1.0.0 > > > There have arisen some issues that would have been caught had there been a > three-router test in the regression suite. This test should be added. -- 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] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned PROTON-1542: -- Assignee: (was: Gordon Sim) > hostname should be set on sasl-init > --- > > Key: PROTON-1542 > URL: https://issues.apache.org/jira/browse/PROTON-1542 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c, python-binding, > ruby-binding >Reporter: Gordon Sim > > For a multi-tenant service/server, where each tenant has its own user base, > the hostname in the sasl-init frame provides a convenient way of determining > the correct tenant to authenticate for. > At present this is not set for any proton-c based client. It is similar to > the SNI information included in the TLS layer initiation (if such a layer is > in use). -- 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] (PROTON-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned PROTON-1542: -- Assignee: Gordon Sim (was: Justin Ross) > hostname should be set on sasl-init > --- > > Key: PROTON-1542 > URL: https://issues.apache.org/jira/browse/PROTON-1542 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c, python-binding, > ruby-binding >Reporter: Gordon Sim >Assignee: Gordon Sim > > For a multi-tenant service/server, where each tenant has its own user base, > the hostname in the sasl-init frame provides a convenient way of determining > the correct tenant to authenticate for. > At present this is not set for any proton-c based client. It is similar to > the SNI information included in the TLS layer initiation (if such a layer is > in use). -- 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-1542) hostname should be set on sasl-init
[ https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130139#comment-16130139 ] Gordon Sim commented on PROTON-1542: https://issues.apache.org/jira/browse/PROTON-1535 allows the hostname to be set by plugins. This issue is covers the public api and default behaviour. > hostname should be set on sasl-init > --- > > Key: PROTON-1542 > URL: https://issues.apache.org/jira/browse/PROTON-1542 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c, python-binding, > ruby-binding >Reporter: Gordon Sim >Assignee: Justin Ross > > For a multi-tenant service/server, where each tenant has its own user base, > the hostname in the sasl-init frame provides a convenient way of determining > the correct tenant to authenticate for. > At present this is not set for any proton-c based client. It is similar to > the SNI information included in the TLS layer initiation (if such a layer is > in use). -- 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-1535) Can't set hostname on SASL-INIT through sasl plugin interface
[ https://issues.apache.org/jira/browse/PROTON-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130138#comment-16130138 ] Gordon Sim commented on PROTON-1535: See https://issues.apache.org/jira/browse/PROTON-1542 for the public API. > Can't set hostname on SASL-INIT through sasl plugin interface > - > > Key: PROTON-1535 > URL: https://issues.apache.org/jira/browse/PROTON-1535 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Gordon Sim >Assignee: Andrew Stitcher > Fix For: proton-c-0.18.0 > > > There is no way to set the hostname in the SASL-INIT frame that is sent out > by proton. This is needed if the server will use that hostname to determine > the realm/domain against which to authenticate in a multi-tenant environment. -- 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-1500) Allow plugin SASL implementations
[ https://issues.apache.org/jira/browse/PROTON-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130137#comment-16130137 ] Gordon Sim commented on PROTON-1500: See https://issues.apache.org/jira/browse/PROTON-1542 for a JIRA covering the public API. > Allow plugin SASL implementations > - > > Key: PROTON-1500 > URL: https://issues.apache.org/jira/browse/PROTON-1500 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.18.0 > > -- 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] [Issue Comment Deleted] (PROTON-1500) Allow plugin SASL implementations
[ https://issues.apache.org/jira/browse/PROTON-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated PROTON-1500: --- Comment: was deleted (was: See https://issues.apache.org/jira/browse/PROTON-1542 for a JIRA covering the public API.) > Allow plugin SASL implementations > - > > Key: PROTON-1500 > URL: https://issues.apache.org/jira/browse/PROTON-1500 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher > Fix For: proton-c-0.18.0 > > -- 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-1542) hostname should be set on sasl-init
Gordon Sim created PROTON-1542: -- Summary: hostname should be set on sasl-init Key: PROTON-1542 URL: https://issues.apache.org/jira/browse/PROTON-1542 Project: Qpid Proton Issue Type: Bug Components: cpp-binding, go-binding, proton-c, python-binding, ruby-binding Reporter: Gordon Sim Assignee: Justin Ross For a multi-tenant service/server, where each tenant has its own user base, the hostname in the sasl-init frame provides a convenient way of determining the correct tenant to authenticate for. At present this is not set for any proton-c based client. It is similar to the SNI information included in the TLS layer initiation (if such a layer is in use). -- 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-7891) AMQConnectionClosedException - Error: Unknown channel id: X [error code 504: channel error]
[
https://issues.apache.org/jira/browse/QPID-7891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130121#comment-16130121
]
Lorenz Quack commented on QPID-7891:
I'm looking into it.
> AMQConnectionClosedException - Error: Unknown channel id: X [error code 504:
> channel error]
> ---
>
> Key: QPID-7891
> URL: https://issues.apache.org/jira/browse/QPID-7891
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
>Affects Versions: qpid-java-6.1.1
>Reporter: Dharam Thacker
>Assignee: Lorenz Quack
> Labels: newbie, qpid, qpidclient
> Attachments: QpidConfig.java, qpid_debug_logs.txt
>
>
> Hi Team,
> I am facing below exception frequently on random time interval for my qpid
> client app. I have attached my spring bean definitions as well in attachment
> section.
> I don't have good way to reproduce this but it happens whenever there is
> message burst from queue for consumer application. It's also not a transient
> error but it happens quite frequently for us.
> URI as per logs : org.apache.qpid.client.AMQConnection
> Connection(1):amqp://App41e4abb8a78c4310b5ac40b973f437cc:@App41e4abb8a78c4310b5ac40b973f437cc/b82e317d53cc4f06b2f6cdc347f1a3a5?brokerlist='tcp://broker-2.qpid.services.domain.com:5672'
>
> *+Note+*: I have attached debug logs as well for details informations
> *+Exception Stacktrace:+*
> Multiple occurrences for each of below channel ids,
>
> Unknown channel id: 214
> Unknown channel id: 69
> Unknown channel id: 139
> Unknown channel id: 64
> h2.
>
> o.s.j.c.CachingConnectionFactory Encountered a JMSException - resetting the
> underlying JMS Connection javax.jms.JMSException: Exception thrown against
> AMQConnection: Host: broker-2.qpid.services.domain.com Port: 5672
> Virtual Host: 3c6273fa428142108b2fe4ffa4404612 Client ID:
> Appbb7488d910fa4c5b8e0561dec8f3f478 Active session count: 11:
> org.apache.qpid.AMQConnectionClosedException: Error: Unknown channel id: 139
> [error code 504: channel error]at
> org.apache.qpid.client.AMQConnection.convertToJMSException(AMQConnection.java:1550)
> at org.apache.qpid.client.AMQConnection.closed(AMQConnection.java:1563)
> at
> org.apache.qpid.client.AMQProtocolHandler.closed(AMQProtocolHandler.java:235)
> at
> org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.closed(AMQConnectionDelegate_8_0.java:563)
>
> at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:225)
> at java.lang.Thread.run(Thread.java:745) Caused by:
> org.apache.qpid.AMQConnectionClosedException: *{color:red}Error: Unknown
> channel id: 139{color}*
> at
> org.apache.qpid.client.handler.ConnectionCloseMethodHandler.methodReceived(ConnectionCloseMethodHandler.java:90)
>
> at
> org.apache.qpid.client.handler.ClientMethodDispatcherImpl.dispatchConnectionClose(ClientMethodDispatcherImpl.java:227)
>
> at
> org.apache.qpid.framing.ConnectionCloseBody.execute(ConnectionCloseBody.java:103)
>
> at
> org.apache.qpid.client.state.AMQStateManager.methodReceived(AMQStateManager.java:118)
>
> at
> org.apache.qpid.client.AMQProtocolHandler.methodBodyReceived(AMQProtocolHandler.java:523)
>
> at
> org.apache.qpid.client.protocol.AMQProtocolSession.methodFrameReceived(AMQProtocolSession.java:446)
>
> at
> org.apache.qpid.framing.AMQMethodBodyImpl.handle(AMQMethodBodyImpl.java:64)
> at
> org.apache.qpid.client.AMQProtocolHandler.received(AMQProtocolHandler.java:473)
>
> at
> org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.received(AMQConnectionDelegate_8_0.java:549)
>
> at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:164)
> ... 1 common frames omitted
> h2.
>
> o.s.j.c.CachingConnectionFactory Encountered a JMSException - resetting the
> underlying JMS Connection javax.jms.JMSException: Exception thrown against
> AMQConnection: Host: broker-2.qpid.services.domain.com Port: 5672
> Virtual Host: ad5203dcf2d9445dac4ce7dede1c1723 Client ID:
> App95af31d06be944faa6583a2fd7f5bca9 Active session count: 10:
> org.apache.qpid.AMQConnectionClosedException: Error: Unknown channel id: 64
> [error code 504: channel error]
> at
> org.apache.qpid.client.AMQConnection.convertToJMSException(AMQConnection.java:1550)
>
> at org.apache.qpid.client.AMQConnection.closed(AMQConnection.java:1563)
> at
> org.apache.qpid.client.AMQProtocolHandler.closed(AMQProtocolHandler.java:235)
>
> at
> org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.closed(AMQConnectionDelegate_8_0.java:563)
>
> at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:225)
>
> at java.lang.Thread.run(Thread.java:745) Caused by:
[jira] [Assigned] (QPID-7891) AMQConnectionClosedException - Error: Unknown channel id: X [error code 504: channel error]
[
https://issues.apache.org/jira/browse/QPID-7891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack reassigned QPID-7891:
--
Assignee: Lorenz Quack
> AMQConnectionClosedException - Error: Unknown channel id: X [error code 504:
> channel error]
> ---
>
> Key: QPID-7891
> URL: https://issues.apache.org/jira/browse/QPID-7891
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
>Affects Versions: qpid-java-6.1.1
>Reporter: Dharam Thacker
>Assignee: Lorenz Quack
> Labels: newbie, qpid, qpidclient
> Attachments: QpidConfig.java, qpid_debug_logs.txt
>
>
> Hi Team,
> I am facing below exception frequently on random time interval for my qpid
> client app. I have attached my spring bean definitions as well in attachment
> section.
> I don't have good way to reproduce this but it happens whenever there is
> message burst from queue for consumer application. It's also not a transient
> error but it happens quite frequently for us.
> URI as per logs : org.apache.qpid.client.AMQConnection
> Connection(1):amqp://App41e4abb8a78c4310b5ac40b973f437cc:@App41e4abb8a78c4310b5ac40b973f437cc/b82e317d53cc4f06b2f6cdc347f1a3a5?brokerlist='tcp://broker-2.qpid.services.domain.com:5672'
>
> *+Note+*: I have attached debug logs as well for details informations
> *+Exception Stacktrace:+*
> Multiple occurrences for each of below channel ids,
>
> Unknown channel id: 214
> Unknown channel id: 69
> Unknown channel id: 139
> Unknown channel id: 64
> h2.
>
> o.s.j.c.CachingConnectionFactory Encountered a JMSException - resetting the
> underlying JMS Connection javax.jms.JMSException: Exception thrown against
> AMQConnection: Host: broker-2.qpid.services.domain.com Port: 5672
> Virtual Host: 3c6273fa428142108b2fe4ffa4404612 Client ID:
> Appbb7488d910fa4c5b8e0561dec8f3f478 Active session count: 11:
> org.apache.qpid.AMQConnectionClosedException: Error: Unknown channel id: 139
> [error code 504: channel error]at
> org.apache.qpid.client.AMQConnection.convertToJMSException(AMQConnection.java:1550)
> at org.apache.qpid.client.AMQConnection.closed(AMQConnection.java:1563)
> at
> org.apache.qpid.client.AMQProtocolHandler.closed(AMQProtocolHandler.java:235)
> at
> org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.closed(AMQConnectionDelegate_8_0.java:563)
>
> at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:225)
> at java.lang.Thread.run(Thread.java:745) Caused by:
> org.apache.qpid.AMQConnectionClosedException: *{color:red}Error: Unknown
> channel id: 139{color}*
> at
> org.apache.qpid.client.handler.ConnectionCloseMethodHandler.methodReceived(ConnectionCloseMethodHandler.java:90)
>
> at
> org.apache.qpid.client.handler.ClientMethodDispatcherImpl.dispatchConnectionClose(ClientMethodDispatcherImpl.java:227)
>
> at
> org.apache.qpid.framing.ConnectionCloseBody.execute(ConnectionCloseBody.java:103)
>
> at
> org.apache.qpid.client.state.AMQStateManager.methodReceived(AMQStateManager.java:118)
>
> at
> org.apache.qpid.client.AMQProtocolHandler.methodBodyReceived(AMQProtocolHandler.java:523)
>
> at
> org.apache.qpid.client.protocol.AMQProtocolSession.methodFrameReceived(AMQProtocolSession.java:446)
>
> at
> org.apache.qpid.framing.AMQMethodBodyImpl.handle(AMQMethodBodyImpl.java:64)
> at
> org.apache.qpid.client.AMQProtocolHandler.received(AMQProtocolHandler.java:473)
>
> at
> org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.received(AMQConnectionDelegate_8_0.java:549)
>
> at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:164)
> ... 1 common frames omitted
> h2.
>
> o.s.j.c.CachingConnectionFactory Encountered a JMSException - resetting the
> underlying JMS Connection javax.jms.JMSException: Exception thrown against
> AMQConnection: Host: broker-2.qpid.services.domain.com Port: 5672
> Virtual Host: ad5203dcf2d9445dac4ce7dede1c1723 Client ID:
> App95af31d06be944faa6583a2fd7f5bca9 Active session count: 10:
> org.apache.qpid.AMQConnectionClosedException: Error: Unknown channel id: 64
> [error code 504: channel error]
> at
> org.apache.qpid.client.AMQConnection.convertToJMSException(AMQConnection.java:1550)
>
> at org.apache.qpid.client.AMQConnection.closed(AMQConnection.java:1563)
> at
> org.apache.qpid.client.AMQProtocolHandler.closed(AMQProtocolHandler.java:235)
>
> at
> org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.closed(AMQConnectionDelegate_8_0.java:563)
>
> at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:225)
>
> at java.lang.Thread.run(Thread.java:745) Caused by:
> org.apache.qpid.AMQConnectionClosedExcept
[jira] [Updated] (QPID-7891) AMQConnectionClosedException - Error: Unknown channel id: X [error code 504: channel error]
[
https://issues.apache.org/jira/browse/QPID-7891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dharam Thacker updated QPID-7891:
-
Description:
Hi Team,
I am facing below exception frequently on random time interval for my qpid
client app. I have attached my spring bean definitions as well in attachment
section.
I don't have good way to reproduce this but it happens whenever there is
message burst from queue for consumer application. It's also not a transient
error but it happens quite frequently for us.
URI as per logs : org.apache.qpid.client.AMQConnection
Connection(1):amqp://App41e4abb8a78c4310b5ac40b973f437cc:@App41e4abb8a78c4310b5ac40b973f437cc/b82e317d53cc4f06b2f6cdc347f1a3a5?brokerlist='tcp://broker-2.qpid.services.domain.com:5672'
*+Note+*: I have attached debug logs as well for details informations
*+Exception Stacktrace:+*
Multiple occurrences for each of below channel ids,
Unknown channel id: 214
Unknown channel id: 69
Unknown channel id: 139
Unknown channel id: 64
h2.
o.s.j.c.CachingConnectionFactory Encountered a JMSException - resetting the
underlying JMS Connection javax.jms.JMSException: Exception thrown against
AMQConnection: Host: broker-2.qpid.services.domain.com Port: 5672
Virtual Host: 3c6273fa428142108b2fe4ffa4404612 Client ID:
Appbb7488d910fa4c5b8e0561dec8f3f478 Active session count: 11:
org.apache.qpid.AMQConnectionClosedException: Error: Unknown channel id: 139
[error code 504: channel error]at
org.apache.qpid.client.AMQConnection.convertToJMSException(AMQConnection.java:1550)
at org.apache.qpid.client.AMQConnection.closed(AMQConnection.java:1563)
at
org.apache.qpid.client.AMQProtocolHandler.closed(AMQProtocolHandler.java:235)
at
org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.closed(AMQConnectionDelegate_8_0.java:563)
at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:225)
at java.lang.Thread.run(Thread.java:745) Caused by:
org.apache.qpid.AMQConnectionClosedException: *{color:red}Error: Unknown
channel id: 139{color}*
at
org.apache.qpid.client.handler.ConnectionCloseMethodHandler.methodReceived(ConnectionCloseMethodHandler.java:90)
at
org.apache.qpid.client.handler.ClientMethodDispatcherImpl.dispatchConnectionClose(ClientMethodDispatcherImpl.java:227)
at
org.apache.qpid.framing.ConnectionCloseBody.execute(ConnectionCloseBody.java:103)
at
org.apache.qpid.client.state.AMQStateManager.methodReceived(AMQStateManager.java:118)
at
org.apache.qpid.client.AMQProtocolHandler.methodBodyReceived(AMQProtocolHandler.java:523)
at
org.apache.qpid.client.protocol.AMQProtocolSession.methodFrameReceived(AMQProtocolSession.java:446)
at org.apache.qpid.framing.AMQMethodBodyImpl.handle(AMQMethodBodyImpl.java:64)
at
org.apache.qpid.client.AMQProtocolHandler.received(AMQProtocolHandler.java:473)
at
org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.received(AMQConnectionDelegate_8_0.java:549)
at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:164) ...
1 common frames omitted
h2.
o.s.j.c.CachingConnectionFactory Encountered a JMSException - resetting the
underlying JMS Connection javax.jms.JMSException: Exception thrown against
AMQConnection: Host: broker-2.qpid.services.domain.com Port: 5672
Virtual Host: ad5203dcf2d9445dac4ce7dede1c1723 Client ID:
App95af31d06be944faa6583a2fd7f5bca9 Active session count: 10:
org.apache.qpid.AMQConnectionClosedException: Error: Unknown channel id: 64
[error code 504: channel error]
at
org.apache.qpid.client.AMQConnection.convertToJMSException(AMQConnection.java:1550)
at org.apache.qpid.client.AMQConnection.closed(AMQConnection.java:1563)
at
org.apache.qpid.client.AMQProtocolHandler.closed(AMQProtocolHandler.java:235)
at
org.apache.qpid.client.AMQConnectionDelegate_8_0$ReceiverClosedWaiter.closed(AMQConnectionDelegate_8_0.java:563)
at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:225)
at java.lang.Thread.run(Thread.java:745) Caused by:
org.apache.qpid.AMQConnectionClosedException: *{color:red}Error: Unknown
channel id: 64{color}*
{color}*at
org.apache.qpid.client.handler.ConnectionCloseMethodHandler.methodReceived(ConnectionCloseMethodHandler.java:90)
at
org.apache.qpid.client.handler.ClientMethodDispatcherImpl.dispatchConnectionClose(ClientMethodDispatcherImpl.java:227)
at
org.apache.qpid.framing.ConnectionCloseBody.execute(ConnectionCloseBody.java:103)
at
org.apache.qpid.client.state.AMQStateManager.methodReceived(AMQStateManager.java:118)
at
org.apache.qpid.client.AMQProtocolHandler.methodBodyReceived(AMQProtocolHandler.java:523)
at
org.apache.qpid.client.protocol.AMQProtocolSession.methodFrameReceived(AMQProtocolSession.java:446)
at org.apache.qpid.framing.AMQMethodBodyImpl.handle(AMQMethodBodyImpl.java:64)
