[jira] [Created] (AMQ-4583) Links on http://activemq.apache.org/redelivery-policy.html are outdated
Martin Lichtin created AMQ-4583: --- Summary: Links on http://activemq.apache.org/redelivery-policy.html are outdated Key: AMQ-4583 URL: https://issues.apache.org/jira/browse/AMQ-4583 Project: ActiveMQ Issue Type: Bug Components: Documentation Reporter: Martin Lichtin Priority: Minor The links to the code are no longer working. For example: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQCPP-493) cannot compile on hpux
Massimo Cora' created AMQCPP-493: Summary: cannot compile on hpux Key: AMQCPP-493 URL: https://issues.apache.org/jira/browse/AMQCPP-493 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.7.0 Environment: HP-UX hp3 B.11.31 U ia64 2723170535 Reporter: Massimo Cora' Assignee: Timothy Bish I have ./configure and then make. This is the error returned by the compiling process: Making all in src/main /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../..-ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c -o decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo `test -f 'decaf/internal/util/concurrent/unix/PlatformThread.cpp' || echo './'`decaf/internal/util/concurrent/unix/PlatformThread.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c decaf/internal/util/concurrent/unix/PlatformThread.cpp -fPIC -DPIC -o decaf/internal/util/concurrent/unix/.libs/libactivemq_cpp_la-PlatformThread.o decaf/internal/util/concurrent/unix/PlatformThread.cpp: In static member function 'static void decaf::internal::util::concurrent::PlatformThread::yeild()': decaf/internal/util/concurrent/unix/PlatformThread.cpp:450: error: 'pthread_yield' was not declared in this scope *** Error exit code 1 Stop. *** Error exit code 1 Stop. *** Error exit code 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4583) Links on http://activemq.apache.org/redelivery-policy.html are outdated
[ https://issues.apache.org/jira/browse/AMQ-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Lichtin updated AMQ-4583: Description: The links to the code are no longer working. For example: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup Similar problem with code links on page http://activemq.apache.org/message-redelivery-and-dlq-handling.html Perhaps further pages are affected? was: The links to the code are no longer working. For example: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup Links on http://activemq.apache.org/redelivery-policy.html are outdated --- Key: AMQ-4583 URL: https://issues.apache.org/jira/browse/AMQ-4583 Project: ActiveMQ Issue Type: Bug Components: Documentation Reporter: Martin Lichtin Priority: Minor The links to the code are no longer working. For example: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup Similar problem with code links on page http://activemq.apache.org/message-redelivery-and-dlq-handling.html Perhaps further pages are affected? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4583) Links on http://activemq.apache.org/redelivery-policy.html are outdated
[ https://issues.apache.org/jira/browse/AMQ-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-4583. --- Resolution: Fixed Fixed on ones I could find, open more as you encounter other broken links. Links on http://activemq.apache.org/redelivery-policy.html are outdated --- Key: AMQ-4583 URL: https://issues.apache.org/jira/browse/AMQ-4583 Project: ActiveMQ Issue Type: Bug Components: Documentation Reporter: Martin Lichtin Priority: Minor The links to the code are no longer working. For example: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/RedeliveryPolicy.java?view=markup Similar problem with code links on page http://activemq.apache.org/message-redelivery-and-dlq-handling.html Perhaps further pages are affected? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQCPP-493) cannot compile on hpux
[ https://issues.apache.org/jira/browse/AMQCPP-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQCPP-493: Priority: Minor (was: Major) Not a directly supported platform, waiting on patches. cannot compile on hpux -- Key: AMQCPP-493 URL: https://issues.apache.org/jira/browse/AMQCPP-493 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.7.0 Environment: HP-UX hp3 B.11.31 U ia64 2723170535 Reporter: Massimo Cora' Assignee: Timothy Bish Priority: Minor I have ./configure and then make. This is the error returned by the compiling process: Making all in src/main /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../..-ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c -o decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo `test -f 'decaf/internal/util/concurrent/unix/PlatformThread.cpp' || echo './'`decaf/internal/util/concurrent/unix/PlatformThread.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c decaf/internal/util/concurrent/unix/PlatformThread.cpp -fPIC -DPIC -o decaf/internal/util/concurrent/unix/.libs/libactivemq_cpp_la-PlatformThread.o decaf/internal/util/concurrent/unix/PlatformThread.cpp: In static member function 'static void decaf::internal::util::concurrent::PlatformThread::yeild()': decaf/internal/util/concurrent/unix/PlatformThread.cpp:450: error: 'pthread_yield' was not declared in this scope *** Error exit code 1 Stop. *** Error exit code 1 Stop. *** Error exit code 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-493) cannot compile on hpux
[ https://issues.apache.org/jira/browse/AMQCPP-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685608#comment-13685608 ] Timothy Bish commented on AMQCPP-493: - Patches welcomed, I have no access to HPUX so can't test there myself. cannot compile on hpux -- Key: AMQCPP-493 URL: https://issues.apache.org/jira/browse/AMQCPP-493 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.7.0 Environment: HP-UX hp3 B.11.31 U ia64 2723170535 Reporter: Massimo Cora' Assignee: Timothy Bish I have ./configure and then make. This is the error returned by the compiling process: Making all in src/main /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../..-ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c -o decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo `test -f 'decaf/internal/util/concurrent/unix/PlatformThread.cpp' || echo './'`decaf/internal/util/concurrent/unix/PlatformThread.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c decaf/internal/util/concurrent/unix/PlatformThread.cpp -fPIC -DPIC -o decaf/internal/util/concurrent/unix/.libs/libactivemq_cpp_la-PlatformThread.o decaf/internal/util/concurrent/unix/PlatformThread.cpp: In static member function 'static void decaf::internal::util::concurrent::PlatformThread::yeild()': decaf/internal/util/concurrent/unix/PlatformThread.cpp:450: error: 'pthread_yield' was not declared in this scope *** Error exit code 1 Stop. *** Error exit code 1 Stop. *** Error exit code 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-493) cannot compile on hpux
[ https://issues.apache.org/jira/browse/AMQCPP-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685613#comment-13685613 ] Massimo Cora' commented on AMQCPP-493: -- I can do them, but I need to know what to fix. Some more info on the system: $ g++ --version g++ (GCC) 4.2.3 Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. cannot compile on hpux -- Key: AMQCPP-493 URL: https://issues.apache.org/jira/browse/AMQCPP-493 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.7.0 Environment: HP-UX hp3 B.11.31 U ia64 2723170535 Reporter: Massimo Cora' Assignee: Timothy Bish Priority: Minor I have ./configure and then make. This is the error returned by the compiling process: Making all in src/main /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../..-ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c -o decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo `test -f 'decaf/internal/util/concurrent/unix/PlatformThread.cpp' || echo './'`decaf/internal/util/concurrent/unix/PlatformThread.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c decaf/internal/util/concurrent/unix/PlatformThread.cpp -fPIC -DPIC -o decaf/internal/util/concurrent/unix/.libs/libactivemq_cpp_la-PlatformThread.o decaf/internal/util/concurrent/unix/PlatformThread.cpp: In static member function 'static void decaf::internal::util::concurrent::PlatformThread::yeild()': decaf/internal/util/concurrent/unix/PlatformThread.cpp:450: error: 'pthread_yield' was not declared in this scope *** Error exit code 1 Stop. *** Error exit code 1 Stop. *** Error exit code 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-493) cannot compile on hpux
[ https://issues.apache.org/jira/browse/AMQCPP-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685624#comment-13685624 ] Timothy Bish commented on AMQCPP-493: - Well, from the error its not finding 'pthread_yield' so you need to either figure out if that's supported any why its not finding it or figure out a workaround. cannot compile on hpux -- Key: AMQCPP-493 URL: https://issues.apache.org/jira/browse/AMQCPP-493 Project: ActiveMQ C++ Client Issue Type: Bug Components: Decaf Affects Versions: 3.7.0 Environment: HP-UX hp3 B.11.31 U ia64 2723170535 Reporter: Massimo Cora' Assignee: Timothy Bish Priority: Minor I have ./configure and then make. This is the error returned by the compiling process: Making all in src/main /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../..-ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c -o decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo `test -f 'decaf/internal/util/concurrent/unix/PlatformThread.cpp' || echo './'`decaf/internal/util/concurrent/unix/PlatformThread.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../.. -ansi -pedantic -DHPUX11 -D_REENTRANT -D_HPUX_SOURCE -D_LARGEFILE64_SOURCE -I/diap6/home/jaeco/dev-root/usr/include/apr-1 -I/usr/local/include -W -Wall -Wextra -Wconversion -fPIC -fstrict-aliasing -Wstrict-aliasing=2 -Wno-long-long -g -O2 -pthread -MT decaf/internal/util/concurrent/unix/libactivemq_cpp_la-PlatformThread.lo -MD -MP -MF decaf/internal/util/concurrent/unix/.deps/libactivemq_cpp_la-PlatformThread.Tpo -c decaf/internal/util/concurrent/unix/PlatformThread.cpp -fPIC -DPIC -o decaf/internal/util/concurrent/unix/.libs/libactivemq_cpp_la-PlatformThread.o decaf/internal/util/concurrent/unix/PlatformThread.cpp: In static member function 'static void decaf::internal::util::concurrent::PlatformThread::yeild()': decaf/internal/util/concurrent/unix/PlatformThread.cpp:450: error: 'pthread_yield' was not declared in this scope *** Error exit code 1 Stop. *** Error exit code 1 Stop. *** Error exit code 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4584) Allow configuration of a discarding dead letter strategy
Gary Tully created AMQ-4584:
---
Summary: Allow configuration of a discarding dead letter strategy
Key: AMQ-4584
URL: https://issues.apache.org/jira/browse/AMQ-4584
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.8.0
Reporter: Gary Tully
Priority: Minor
Fix For: 5.9.0
If you don't wish to retain non delivered or expired persistent messages then
it should be possible to easily disable the use of the dlq.
the discarding plugin will purge it, but that is not ideal.
Preferable is something like:
{code}destinationPolicy
policyMap
policyEntries
policyEntry queue= deadLetterStrategy=discarding /
...{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4533) Messages stuck in queue with redelivered=true
[ https://issues.apache.org/jira/browse/AMQ-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685658#comment-13685658 ] Wieslaw Dudek commented on AMQ-4533: It might not be acceptable by customers when the app performance decreases. However if that is the case I wonder if there is any other possibility to timeout some poisoned consumer and redirect all the prefetched messages to the rest of the consumers or, at least, to deliver next messages to the fast and operational consumers to avoid the msgs stuck into invalid one. Also could you create a modified version of this test case to prove that the prefetchSize=0 will solve the issue at the cost of performance degradation in processing of messages? Messages stuck in queue with redelivered=true - Key: AMQ-4533 URL: https://issues.apache.org/jira/browse/AMQ-4533 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.7.0 Environment: Fuse Message Broker 5.7.0 Reporter: Jason Shepherd Attachments: AMQ4533TestPatch.txt, AMQ4533TestPatch.txt, AMQ4533TestPatch.txt, kahaPendingMessages.zip We're getting message stuck in queues with the redelivery flag set to true. We used the following test model: put every 1 second 50 messages sequentially, and after that, the rest of 1000 msgs quickly to INPUT_QUEUE and while starting 25 listeners cosuming from INPUT_QUEUE, which takes about 30 seconds to move the message to RECEIPT_QUEUE, 10 other listeners on RECEIPT_QUEUE consume and counts them. We tried making one of the consumer slow by setting the processing time to 10 seconds (sleep) and putting a heavy load in 500 threads every 1 ms to some other queues the same time. Our test case is attached, you might need to install some dependencies to the local maven repository manually: mvn install:install-file -DgroupId=org.apache.activemq -DartifactId=activemq-core -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar -Dfile=activemq-core-5.7.0.fuse-71-047.jar mvn install:install-file -DgroupId=org.apache.kahadb -DartifactId=kahadb -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar -Dfile=kahadb-5.7.0.fuse-71-047.jar mvn install:install-file -DgroupId=org.apache.geronimo.management.specs -DartifactId=geronimo-j2ee-management_1.1_spec -Dversion=1.0.1 -Dpackaging=jar -Dfile=geronimo-j2ee-management_1.1_spec-1.0.1.jar mvn install:install-file -DgroupId=org.apache.activemq.pool -DartifactId=activemq-pool -Dversion=5.7.0-fuse-71-047 -Dpackaging=jar -Dfile=activemq-pool-5.7.0.fuse-71-047.jar To run the test, simply use the Maven test target: mvn clean test If the problem occurs the you'll get a message like this in the test results, (target/surefire-reports): java.lang.AssertionError: Still messages in InputQueue expected:0 but was:365 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4317) activemq-camel feature doesn't work
[
https://issues.apache.org/jira/browse/AMQ-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685735#comment-13685735
]
Ben O'Day commented on AMQ-4317:
any plans to include this fix in a 5.8.X release? otherwise, when will 5.9 be
available?
activemq-camel feature doesn't work
---
Key: AMQ-4317
URL: https://issues.apache.org/jira/browse/AMQ-4317
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.9.0
activemq-camel feature fails with
{code}karaf@root features:install activemq-camel
Error executing command: Jar is not a bundle, no Bundle-SymbolicName
mvn:org.apache.activemq/activemq-camel/5.8.0
karaf@root{code}
error
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4576) MQTT BlockingConnection.receive fails when subscribing multiple topics
[
https://issues.apache.org/jira/browse/AMQ-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685764#comment-13685764
]
Pedro Marques commented on AMQ-4576:
Tested the new version and it appears corrected.
MQTT BlockingConnection.receive fails when subscribing multiple topics
--
Key: AMQ-4576
URL: https://issues.apache.org/jira/browse/AMQ-4576
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Pedro Marques
Assignee: Timothy Bish
Fix For: 5.9.0
When more than one topic is supplied to BlockingConnection.subscribe the
BlockingConnection.receive fails and the following exception is thrown:
{code}
java.io.IOException: Could not connect: CONNECTION_REFUSED_SERVER_UNAVAILABLE
at
org.fusesource.mqtt.client.CallbackConnection$LoginHandler$1.onTransportCommand(CallbackConnection.java:331)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
On the server shows the following messages:
{code}
2013-06-06 15:06:00,125 WARN
[org.apache.activemq.transport.mqtt.MQTTProtocolConverter] (ActiveMQ
BrokerService[localhost] Task-1) Exception occurred processing:
null: javax.jms.JMSException: Durable consumer is in use for client:
6056@3232261834SOC and subscriptionName: 6056@3232261834SOC
2013-06-06 15:06:00,130 WARN
[org.apache.activemq.broker.TransportConnection] (ActiveMQ Transport:
tcp:///127.0.0.1:53389@1883) Failed to add Connection
ID:LTD-SFW004-53303-1370527418664-2:14, reason:
javax.jms.InvalidClientIDException: Broker: localhost - Client:
6056@3232261834SOC already connected from tcp://127.0.0.1:53388
2013-06-06 15:06:00,130 WARN
[org.apache.activemq.broker.TransportConnection.Transport] (ActiveMQ
Transport: tcp:///127.0.0.1:53389@1883) Transport Connection to:
tcp://127.0.0.1:53389 failed: java.io.IOException: Broker: localhost -
Client: 6056@3232261834SOC already connected from tcp://127.0.0.1:53388
2013-06-06 15:06:00,130 ERROR
[pt.intellicare.onecare.mqtt.OneCareFuseMqttClient]
(DefaultQuartzScheduler_Worker-8) Problem receiving mqtt messages:
java.io.IOException: Could not connect: CONNECTION_REFUSED_SERVER_UNAVAILABLE
at
org.fusesource.mqtt.client.CallbackConnection$LoginHandler$1.onTransportCommand(CallbackConnection.java:331)
[:1.5-SNAPSHOT]
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
[:1.17]
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
[:1.17]
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
[:1.17]
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
[:1.17]
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
[:1.17]
{code}
Code example:
{code}
MQTT = new MQTT();
mqtt.setHost(url);
mqtt.setClientId(clientId);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setCleanSession(false);
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
Topic[] topics = {new Topic(TopicA, QoS.EXACTLY_ONCE), new Topic(TopicB,
QoS.EXACTLY_ONCE)};
byte[] qoses = connection.subscribe(topics);
while (true) {
Message message = connection.receive();
byte[] payload = message.getPayload();
String messageContent = new String(payload);
System.out.println(Received message from topic: + message.getTopic() +
Message content: + messageContent);
message.ack();
}
{code}
The test failed when using the current fusesource client (1.5) on ActiveMQ
5.9, on Mosquitto mqtt the code works correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Marques updated AMQ-4585:
---
Description:
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session. The
test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
The problem doesn't occur always but most of the times the first reconnection
attempt is made. With setCleanSession(true) the system works fine.
Code sample (publisher, permanently running):
{code}
MQTT mqtt = new MQTT();
mqtt.setHost(url);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setClientId(test_id);
int i = 0;
while (true) {
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
String message = TestMessage: + i;
connection.publish(TopicA, message.getBytes(), QoS.AT_LEAST_ONCE,
false);
System.out.println(Vendor: Sent message.);
Thread.sleep(2500);
connection.disconnect();
Thread.sleep(2500);
i++;
}
{code}
Code sample (subscriber, fails multiple times when restarting after the
connection is closed):
{code}
try {
MQTT = new MQTT();
mqtt.setHost(url);
mqtt.setClientId(clientId);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setCleanSession(false);
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
Topic[] topics = {new Topic(TopicA, QoS.EXACTLY_ONCE)};
byte[] qoses =
[jira] [Created] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
Pedro Marques created AMQ-4585:
--
Summary: MQTT BlockingConnection.receive fails when receiving
pending messages after reconnect without cleaning session
Key: AMQ-4585
URL: https://issues.apache.org/jira/browse/AMQ-4585
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Pedro Marques
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session. The
test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
The problem doesn't occur always but most of the times the first reconnection
attempt is made. With setCleanSession(true) the system works fine.
Code sample (publisher, permanently running):
{code}
MQTT mqtt = new MQTT();
mqtt.setHost(url);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setClientId(test_id);
int i = 0;
while (true) {
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
String message = TestMessage: + i;
connection.publish(TopicA, message.getBytes(), QoS.AT_LEAST_ONCE,
false);
System.out.println(Vendor: Sent message.);
Thread.sleep(2500);
connection.disconnect();
Thread.sleep(2500);
i++;
}
{code}
Code sample (subscriber, fails multiple times when restarting after the
connection is closed):
{code}
try {
MQTT = new MQTT();
mqtt.setHost(url);
mqtt.setClientId(clientId);
mqtt.setUserName(user);
mqtt.setPassword(password);
[jira] [Updated] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Marques updated AMQ-4585:
---
Description:
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session. The
test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
The problem doesn't occur always but most of the times the first reconnection
attempt is made. With setCleanSession(true) the system works fine.
Code sample (publisher, permanently running):
{code}
MQTT mqtt = new MQTT();
mqtt.setHost(url);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setClientId(test_id);
int i = 0;
while (true) {
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
String message = TestMessage: + i;
connection.publish(TopicA, message.getBytes(), QoS.AT_LEAST_ONCE,
false);
System.out.println(Vendor: Sent message.);
Thread.sleep(2500);
connection.disconnect();
Thread.sleep(2500);
i++;
}
{code}
Code sample (subscriber, fails multiple times when restarting after the
connection is closed):
{code}
BlockingConnection connection = null;
try {
MQTT = new MQTT();
mqtt.setHost(url);
mqtt.setClientId(clientId);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setCleanSession(false);
connection = mqtt.blockingConnection();
connection.connect();
Topic[] topics = {new Topic(TopicA, QoS.EXACTLY_ONCE)};
byte[]
[jira] [Updated] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Marques updated AMQ-4585:
---
Description:
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session. The
test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
The problem doesn't occur always but most of the times the first reconnection
attempt is made. With setCleanSession(true) the system works fine.
Code sample (publisher, permanently running):
{code}
MQTT mqtt = new MQTT();
mqtt.setHost(url);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setClientId(test_id);
int i = 0;
while (true) {
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
String message = TestMessage: + i;
connection.publish(TopicA, message.getBytes(), QoS.AT_LEAST_ONCE,
false);
System.out.println(Vendor: Sent message.);
Thread.sleep(2500);
connection.disconnect();
Thread.sleep(2500);
i++;
}
{code}
Code sample (subscriber, fails multiple times when restarting after the
connection is closed):
{code}
BlockingConnection connection = null;
try {
MQTT = new MQTT();
mqtt.setHost(url);
mqtt.setClientId(clientId);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setCleanSession(false);
connection = mqtt.blockingConnection();
connection.connect();
Topic[] topics = {new Topic(TopicA, QoS.EXACTLY_ONCE)};
byte[]
[jira] [Updated] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Marques updated AMQ-4585:
---
Description:
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session. The
test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
No message is shown in the server. The problem doesn't occur always but most of
the times the first reconnection attempt is made. With setCleanSession(true)
the system works fine.
Code sample (publisher, permanently running):
{code}
MQTT mqtt = new MQTT();
mqtt.setHost(url);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setClientId(test_id);
int i = 0;
while (true) {
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
String message = TestMessage: + i;
connection.publish(TopicA, message.getBytes(), QoS.AT_LEAST_ONCE,
false);
System.out.println(Vendor: Sent message.);
Thread.sleep(2500);
connection.disconnect();
Thread.sleep(2500);
i++;
}
{code}
Code sample (subscriber, fails multiple times when restarting after the
connection is closed):
{code}
BlockingConnection connection = null;
try {
MQTT = new MQTT();
mqtt.setHost(url);
mqtt.setClientId(clientId);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setCleanSession(false);
connection = mqtt.blockingConnection();
connection.connect();
Topic[] topics = {new
[jira] [Commented] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685808#comment-13685808
]
Timothy Bish commented on AMQ-4585:
---
Not fully following the code to reproduce, best bet is to create a unit test
similar to those in the activemq-mqtt module so we can run it and see the issue
and ensure that the fix is preserved into the future.
MQTT BlockingConnection.receive fails when receiving pending messages after
reconnect without cleaning session
--
Key: AMQ-4585
URL: https://issues.apache.org/jira/browse/AMQ-4585
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Pedro Marques
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session.
The test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
No message is shown in the server. The problem doesn't occur always but most
of the times the first reconnection attempt is made. With
setCleanSession(true) the system works fine.
Code sample (publisher, permanently running):
{code}
MQTT mqtt = new MQTT();
mqtt.setHost(url);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setClientId(test_id);
int i = 0;
while (true) {
BlockingConnection connection = mqtt.blockingConnection();
[jira] [Commented] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685840#comment-13685840
]
Pedro Marques commented on AMQ-4585:
Yes, well the code is not simple because I used two classes running
simultaneously... The publisher always sending messages, the subscriber
receiving 10 messages on each run. The problem occurs when restarting the
subscriber after the first run (leaving some time between runs in order to
allow the publisher to publish some messages). Theoretically it would be simple
to use only one class publish some messages, receive them on the subscriber,
close the subscriber, publish more messages, and attempt to reconnect and
receive those messages but I haven't tested this method. I should stress that
the problem, although it fails frequently, doesn't occur every time, I had
multiple runs of the subscriber that processed the pending messages correctly.
MQTT BlockingConnection.receive fails when receiving pending messages after
reconnect without cleaning session
--
Key: AMQ-4585
URL: https://issues.apache.org/jira/browse/AMQ-4585
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Pedro Marques
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session.
The test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
[jira] [Commented] (AMQ-4585) MQTT BlockingConnection.receive fails when receiving pending messages after reconnect without cleaning session
[
https://issues.apache.org/jira/browse/AMQ-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685855#comment-13685855
]
Timothy Bish commented on AMQ-4585:
---
The test code is easy to work from so I'd try and create a unit test, I won't
have time to do that before I leave for vacation but if you can create a test
case the fix could be simple and I might get it in quickly.
MQTT BlockingConnection.receive fails when receiving pending messages after
reconnect without cleaning session
--
Key: AMQ-4585
URL: https://issues.apache.org/jira/browse/AMQ-4585
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Pedro Marques
The system throws at least three different types of exceptions when a
subscriber receives the first pending message without cleaning the session.
The test case corresponds to receiving several messages from a publisher then
closing the subscriber connection and finally reconnecting with
setCleanSession(false) and attempt to read the messages published while the
subscriber was disconnected.
The exceptions thrown:
{code}
java.net.ProtocolException: Command from server contained an invalid message
id: 1
at
org.fusesource.mqtt.client.CallbackConnection.completeRequest(CallbackConnection.java:723)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:762)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at
org.fusesource.mqtt.codec.MessageSupport$AckBase.decode(MessageSupport.java:81)
at org.fusesource.mqtt.codec.PUBREC.decode(PUBREC.java:40)
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:749)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
{code}
java.net.ProtocolException: Unexpected MQTT command type: 0
at
org.fusesource.mqtt.client.CallbackConnection.processFrame(CallbackConnection.java:775)
at
org.fusesource.mqtt.client.CallbackConnection.access$1500(CallbackConnection.java:51)
at
org.fusesource.mqtt.client.CallbackConnection$6.onTransportCommand(CallbackConnection.java:392)
at
org.fusesource.hawtdispatch.transport.TcpTransport.drainInbound(TcpTransport.java:659)
at
org.fusesource.hawtdispatch.transport.SslTransport.drainInbound(SslTransport.java:264)
at
org.fusesource.hawtdispatch.transport.TcpTransport$6.run(TcpTransport.java:538)
at
org.fusesource.hawtdispatch.internal.NioDispatchSource$3.run(NioDispatchSource.java:209)
at
org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
at
org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)
{code}
No message is shown in the server. The problem doesn't occur always but most
of the times the first reconnection attempt is made. With
setCleanSession(true) the system works fine.
Code sample (publisher, permanently running):
{code}
MQTT mqtt = new MQTT();
mqtt.setHost(url);
mqtt.setUserName(user);
mqtt.setPassword(password);
mqtt.setClientId(test_id);
int i = 0;
while (true) {
BlockingConnection connection = mqtt.blockingConnection();
[jira] [Commented] (AMQ-4317) activemq-camel feature doesn't work
[
https://issues.apache.org/jira/browse/AMQ-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685870#comment-13685870
]
Chris Geer commented on AMQ-4317:
-
I'd like to see this in 5.8.x as well
activemq-camel feature doesn't work
---
Key: AMQ-4317
URL: https://issues.apache.org/jira/browse/AMQ-4317
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.9.0
activemq-camel feature fails with
{code}karaf@root features:install activemq-camel
Error executing command: Jar is not a bundle, no Bundle-SymbolicName
mvn:org.apache.activemq/activemq-camel/5.8.0
karaf@root{code}
error
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4586) ActiveMQConnection leaks executor threads onException
Christian Posta created AMQ-4586: Summary: ActiveMQConnection leaks executor threads onException Key: AMQ-4586 URL: https://issues.apache.org/jira/browse/AMQ-4586 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: Christian Posta When a broker goes down, and client is not using failover transport, the client can experience leaked threads because the executor is not properly cleaned up. The symptoms of this are seeing ActiveMQ Connection Executor threads staying around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4586) ActiveMQConnection leaks executor threads onException
[ https://issues.apache.org/jira/browse/AMQ-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Posta updated AMQ-4586: - Attachment: ClientConnectionThreadLeakTest.java Attaching test case ActiveMQConnection leaks executor threads onException - Key: AMQ-4586 URL: https://issues.apache.org/jira/browse/AMQ-4586 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: Christian Posta Attachments: ClientConnectionThreadLeakTest.java When a broker goes down, and client is not using failover transport, the client can experience leaked threads because the executor is not properly cleaned up. The symptoms of this are seeing ActiveMQ Connection Executor threads staying around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4586) ActiveMQConnection leaks executor threads onException
[ https://issues.apache.org/jira/browse/AMQ-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685893#comment-13685893 ] Timothy Bish commented on AMQ-4586: --- Not entirely sure but I think that there's a single thread maintained in order to have at least one non-daemon thread at all times, so if you go with option two it could break the tests where we check for that. ActiveMQConnection leaks executor threads onException - Key: AMQ-4586 URL: https://issues.apache.org/jira/browse/AMQ-4586 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: Christian Posta Attachments: AMQ-4586-fix1.patch, AMQ-4586-fix2.patch, ClientConnectionThreadLeakTest.java When a broker goes down, and client is not using failover transport, the client can experience leaked threads because the executor is not properly cleaned up. The symptoms of this are seeing ActiveMQ Connection Executor threads staying around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4584) Allow configuration of a discarding dead letter strategy
[
https://issues.apache.org/jira/browse/AMQ-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-4584:
--
Attachment: AMQ4584Patch.txt
Took a quick stab at it while waiting for other things to run.
Allow configuration of a discarding dead letter strategy
Key: AMQ-4584
URL: https://issues.apache.org/jira/browse/AMQ-4584
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.8.0
Reporter: Gary Tully
Priority: Minor
Fix For: 5.9.0
Attachments: AMQ4584Patch.txt
If you don't wish to retain non delivered or expired persistent messages then
it should be possible to easily disable the use of the dlq.
the discarding plugin will purge it, but that is not ideal.
Preferable is something like:
{code}destinationPolicy
policyMap
policyEntries
policyEntry queue= deadLetterStrategy=discarding /
...{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (AMQ-3405) DLQ messages moved/copied into original queue disappear after failing processing for a second time
[ https://issues.apache.org/jira/browse/AMQ-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-3405: --- Assignee: Timothy Bish While we can work around this with disable of the Audit, it would be better to fix this so that the Audit of the Message is rolled back as messages are moved out of the DLQ. DLQ messages moved/copied into original queue disappear after failing processing for a second time -- Key: AMQ-3405 URL: https://issues.apache.org/jira/browse/AMQ-3405 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.2 Environment: Windows 7, Java 64bit 1.6 update 20, Client and server 5.4.2 Reporter: Carey Flichel Assignee: Timothy Bish 1. Message in queue A fails enough times to be moved to the DLQ. 2. We move/copy the message back to queue A to attempt reprocessing. Invoking the retry operation from JMX can also be used. 3. The consumer once again fails to consume the message greater than the max number of times. 4. The message is not put back into the DLQ. If it was moved rather than copied, it means we have a message that was never successfully consumed, but has nevertheless disappeared. This is all with the default ActiveMQ settings, though I tried adjusted the DLQ configuration to support both expired and non-persistent messages. I found this posting which seems to indicate the same issue I am seeing: http://www.mail-archive.com/users@activemq.apache.org/msg09683.html. One difference that I am seeing is that restarting ActiveMQ does not cause the message to show up in the DLQ again. Once it is lost, it is lost forever. To replicate this, I believe you can use a consumer that just fails on every invocation. One interesting thing is that if I put a message into the DLQ directly, then move it to a queue with a consumer, it will end up in the DLQ again as you would expect. If I then move the DLQ message back to the original queue, it will then show the bevahiour outlined above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4584) Allow configuration of a discarding dead letter strategy
[
https://issues.apache.org/jira/browse/AMQ-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686018#comment-13686018
]
Gary Tully commented on AMQ-4584:
-
@tim Looks perfect
Allow configuration of a discarding dead letter strategy
Key: AMQ-4584
URL: https://issues.apache.org/jira/browse/AMQ-4584
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.8.0
Reporter: Gary Tully
Priority: Minor
Fix For: 5.9.0
Attachments: AMQ4584Patch.txt
If you don't wish to retain non delivered or expired persistent messages then
it should be possible to easily disable the use of the dlq.
the discarding plugin will purge it, but that is not ideal.
Preferable is something like:
{code}destinationPolicy
policyMap
policyEntries
policyEntry queue= deadLetterStrategy=discarding /
...{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4586) ActiveMQConnection leaks executor threads onException
[ https://issues.apache.org/jira/browse/AMQ-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686031#comment-13686031 ] Timothy Bish commented on AMQ-4586: --- Part of the trouble here is that the getConnection method doesn't do anything if the conn.start() fails so the connection is never closed. I'm not sure if there's any async exceptions that are recoverable or not, if so then closing the down the executor would be bad. ActiveMQConnection leaks executor threads onException - Key: AMQ-4586 URL: https://issues.apache.org/jira/browse/AMQ-4586 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: Christian Posta Attachments: AMQ-4586-fix1.patch, AMQ-4586-fix2.patch, ClientConnectionThreadLeakTest.java When a broker goes down, and client is not using failover transport, the client can experience leaked threads because the executor is not properly cleaned up. The symptoms of this are seeing ActiveMQ Connection Executor threads staying around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4584) Allow configuration of a discarding dead letter strategy
[
https://issues.apache.org/jira/browse/AMQ-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-4584.
---
Resolution: Fixed
Assignee: Timothy Bish
fixed on trunk
Allow configuration of a discarding dead letter strategy
Key: AMQ-4584
URL: https://issues.apache.org/jira/browse/AMQ-4584
Project: ActiveMQ
Issue Type: Improvement
Components: Broker
Affects Versions: 5.8.0
Reporter: Gary Tully
Assignee: Timothy Bish
Priority: Minor
Fix For: 5.9.0
Attachments: AMQ4584Patch.txt
If you don't wish to retain non delivered or expired persistent messages then
it should be possible to easily disable the use of the dlq.
the discarding plugin will purge it, but that is not ideal.
Preferable is something like:
{code}destinationPolicy
policyMap
policyEntries
policyEntry queue= deadLetterStrategy=discarding /
...{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-4586) ActiveMQConnection leaks executor threads onException
[ https://issues.apache.org/jira/browse/AMQ-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Posta updated AMQ-4586: - Attachment: ClientConnectionThreadLeakTest.java Yep, you're right. Updated test case passes every time without the patches. Thanks for your eyes on this.. ActiveMQConnection leaks executor threads onException - Key: AMQ-4586 URL: https://issues.apache.org/jira/browse/AMQ-4586 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: Christian Posta Attachments: AMQ-4586-fix1.patch, AMQ-4586-fix2.patch, ClientConnectionThreadLeakTest.java, ClientConnectionThreadLeakTest.java When a broker goes down, and client is not using failover transport, the client can experience leaked threads because the executor is not properly cleaned up. The symptoms of this are seeing ActiveMQ Connection Executor threads staying around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4586) ActiveMQConnection leaks executor threads onException
[ https://issues.apache.org/jira/browse/AMQ-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Posta resolved AMQ-4586. -- Resolution: Not A Problem Solution: either use failover, or make sure to catch all exceptions and clean up properly. ActiveMQConnection leaks executor threads onException - Key: AMQ-4586 URL: https://issues.apache.org/jira/browse/AMQ-4586 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Reporter: Christian Posta Attachments: AMQ-4586-fix1.patch, AMQ-4586-fix2.patch, ClientConnectionThreadLeakTest.java, ClientConnectionThreadLeakTest.java When a broker goes down, and client is not using failover transport, the client can experience leaked threads because the executor is not properly cleaned up. The symptoms of this are seeing ActiveMQ Connection Executor threads staying around. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3405) DLQ messages moved/copied into original queue disappear after failing processing for a second time
[ https://issues.apache.org/jira/browse/AMQ-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3405. --- Resolution: Fixed Fix Version/s: 5.9.0 Fixed now on trunk, when a message is moved out of a DLQ its rolled back from the DLQ's Audit so subsequent failures will result in it reappearing in the DLQ. DLQ messages moved/copied into original queue disappear after failing processing for a second time -- Key: AMQ-3405 URL: https://issues.apache.org/jira/browse/AMQ-3405 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.2 Environment: Windows 7, Java 64bit 1.6 update 20, Client and server 5.4.2 Reporter: Carey Flichel Assignee: Timothy Bish Fix For: 5.9.0 1. Message in queue A fails enough times to be moved to the DLQ. 2. We move/copy the message back to queue A to attempt reprocessing. Invoking the retry operation from JMX can also be used. 3. The consumer once again fails to consume the message greater than the max number of times. 4. The message is not put back into the DLQ. If it was moved rather than copied, it means we have a message that was never successfully consumed, but has nevertheless disappeared. This is all with the default ActiveMQ settings, though I tried adjusted the DLQ configuration to support both expired and non-persistent messages. I found this posting which seems to indicate the same issue I am seeing: http://www.mail-archive.com/users@activemq.apache.org/msg09683.html. One difference that I am seeing is that restarting ActiveMQ does not cause the message to show up in the DLQ again. Once it is lost, it is lost forever. To replicate this, I believe you can use a consumer that just fails on every invocation. One interesting thing is that if I put a message into the DLQ directly, then move it to a queue with a consumer, it will end up in the DLQ again as you would expect. If I then move the DLQ message back to the original queue, it will then show the bevahiour outlined above. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Openwire Generator #802
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/802/ -- [INFO] [INFO] [INFO] Building ActiveMQ :: Openwire Generator 5.9-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-openwire-generator --- Jun 18, 2013 3:03:55 AM hudson.maven.ExecutedMojo init WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (default-cli) @ activemq-openwire-generator --- [INFO] Building jar: https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/target/activemq-openwire-generator-5.9-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-openwire-generator --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ activemq-openwire-generator --- [INFO] Compiling 18 source files to https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/target/classes [INFO] [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/src/test/resources [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-openwire-generator --- [INFO] [INFO] No sources to compile [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-openwire-generator --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ activemq-openwire-generator --- [INFO] Building jar: https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/target/activemq-openwire-generator-5.9-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-openwire-generator --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-openwire-generator --- Jun 18, 2013 3:04:00 AM hudson.maven.ExecutedMojo init WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ activemq-openwire-generator --- [WARNING] Artifact org.apache.activemq:activemq-openwire-generator:java-source:sources:5.9-SNAPSHOT already attached to project, ignoring duplicate [INFO] [INFO] --- maven-javadoc-plugin:2.8.1:jar (attach-javadocs) @ activemq-openwire-generator --- [INFO] Loading source files for package org.apache.activemq.openwire.tool... Constructing Javadoc information... Standard Doclet version 1.6.0_45 Building tree for all the packages and classes... Generating https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/target/apidocs/org/apache/activemq/openwire/tool//CGeneratorTask.html... Generating https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/target/apidocs/org/apache/activemq/openwire/tool//CHeadersGenerator.html... Generating https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/target/apidocs/org/apache/activemq/openwire/tool//CppClassesGenerator.html... Generating https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-openwire-generator/ws/target/apidocs/org/apache/activemq/openwire/tool//CppGeneratorTask.html... Generating
Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Blueprint #802
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-blueprint/802/ -- [INFO] [INFO] [INFO] Skipping ActiveMQ :: Memory Usage Test Plugin [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Performance Test Plugin [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: StartUp Plugin [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: Web [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Skipping ActiveMQ :: OSGi bundle [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] [INFO] Building ActiveMQ :: Blueprint 5.9-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-blueprint --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-blueprint --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-blueprint --- Jun 18, 2013 3:04:26 AM hudson.maven.ExecutedMojo init WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] Building jar: https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-blueprint/ws/target/activemq-blueprint-5.9-SNAPSHOT-sources.jar [INFO] --- maven-source-plugin:2.2.1:jar (default-cli) @ activemq-blueprint --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-blueprint --- [INFO] [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-blueprint --- [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-blueprint --- [INFO] [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-blueprint --- [INFO] [INFO] No sources to compile [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ activemq-blueprint --- [INFO] [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-blueprint/ws/src/test/resources [INFO] Copying 3 resources [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-blueprint --- [INFO] [INFO] No sources to compile [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ activemq-blueprint --- [INFO] [INFO] Surefire report directory: https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-blueprint/ws/target/surefire-reports [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-blueprint --- --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results [INFO] [INFO] --- maven-bundle-plugin:2.3.7:bundle (default-bundle) @ activemq-blueprint --- [WARNING] Bundle org.apache.activemq:activemq-blueprint:bundle:5.9-SNAPSHOT : Instructions in Export-Package that are never used: org\.apache\.activemq.*.* Classpath: Jar:.,Jar:org.apache.aries.blueprint,Jar:xbean-blueprint,Jar:commons-jexl,Jar:pax-logging-api [WARNING] Bundle org.apache.activemq:activemq-blueprint:bundle:5.9-SNAPSHOT :
Build failed in Jenkins: ActiveMQ-Trunk-Deploy #802
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/802/changes Changes: [tabish] Fix and updated test for: https://issues.apache.org/jira/browse/AMQ-3405 [tabish] update svn:ignore [tabish] fix and test for: https://issues.apache.org/jira/browse/AMQ-4584 -- [...truncated 5847 lines...] [INFO] ActiveMQ :: STOMP Protocol SKIPPED [INFO] ActiveMQ :: MQTT Protocol . SKIPPED [INFO] ActiveMQ :: JDBC Store SKIPPED [INFO] ActiveMQ :: LevelDB Store . SKIPPED [INFO] ActiveMQ :: RA SKIPPED [INFO] ActiveMQ :: Pool .. SKIPPED [INFO] ActiveMQ :: Spring SKIPPED [INFO] ActiveMQ :: AMQP .. SKIPPED [INFO] ActiveMQ :: Console ... SKIPPED [INFO] ActiveMQ :: Unit Tests SKIPPED [INFO] ActiveMQ :: Camel . SKIPPED [INFO] ActiveMQ :: HTTP Protocol Support . SKIPPED [INFO] ActiveMQ :: All JAR bundle SKIPPED [INFO] ActiveMQ :: File Server ... SKIPPED [INFO] ActiveMQ :: Log4j Appender SKIPPED [INFO] ActiveMQ :: Apache Karaf .. SKIPPED [INFO] ActiveMQ :: RAR ... SKIPPED [INFO] ActiveMQ :: Run Jar ... SKIPPED [INFO] ActiveMQ :: Tooling ... SUCCESS [4.546s] [INFO] ActiveMQ :: Memory Usage Test Plugin .. SKIPPED [INFO] ActiveMQ :: Performance Test Plugin ... SKIPPED [INFO] ActiveMQ :: StartUp Plugin SKIPPED [INFO] ActiveMQ :: Web ... SKIPPED [INFO] ActiveMQ :: OSGi bundle ... SKIPPED [INFO] ActiveMQ :: Blueprint . FAILURE [3.867s] [INFO] ActiveMQ :: Web Demo .. SKIPPED [INFO] ActiveMQ :: Web Console ... SKIPPED [INFO] ActiveMQ :: Karaf Integration Tests ... SKIPPED [INFO] ActiveMQ :: Integration Test :: Spring 3.1 SKIPPED [INFO] ActiveMQ :: Assembly .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:02.646s [INFO] Finished at: Tue Jun 18 03:04:28 UTC 2013 [INFO] Final Memory: 41M/981M [INFO] [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/deploy/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-parent/builds/2013-06-18_03-03-07/archive/org.apache.activemq/activemq-parent/5.9-SNAPSHOT/activemq-parent-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/deploy/activemq-client/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-client/builds/2013-06-18_03-03-07/archive/org.apache.activemq/activemq-client/5.9-SNAPSHOT/activemq-client-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/deploy/assembly/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$apache-activemq/builds/2013-06-18_03-03-13/archive/org.apache.activemq/apache-activemq/5.9-SNAPSHOT/apache-activemq-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/deploy/activemq-camel/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-camel/builds/2013-06-18_03-03-09/archive/org.apache.activemq/activemq-camel/5.9-SNAPSHOT/activemq-camel-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/deploy/activemq-tooling/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq.tooling$activemq-tooling/builds/2013-06-18_03-03-11/archive/org.apache.activemq.tooling/activemq-tooling/5.9-SNAPSHOT/activemq-tooling-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/deploy/activemq-pool/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-pool/builds/2013-06-18_03-03-10/archive/org.apache.activemq/activemq-pool/5.9-SNAPSHOT/activemq-pool-5.9-SNAPSHOT.pom [JENKINS] Archiving https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/ws/deploy/activemq-karaf-itest/pom.xml to /home/hudson/hudson/jobs/ActiveMQ-Trunk-Deploy/modules/org.apache.activemq$activemq-karaf-itest/builds/2013-06-18_03-03-12/archive/org.apache.activemq/activemq-karaf-itest/5.9-SNAPSHOT/activemq-karaf-itest-5.9-SNAPSHOT.pom [JENKINS] Archiving
