Need help on messages getting stuck due to message selector
Hi, I am facing an issue regarding some messages get stuck in the queue. The background of the issue is. 1. We have 2 consumers configured to listen to the same queue. 2. One consumer has a message selector criteria set while the other doesn't. 3. When the messages are pushed into the queue, they basically get shared between the consumers. 4. The consumer which doesn't have the criteria processes the messages assigned to it without any issue. 5. But the consumer that has the selection criteria doesn't process the messages assigned to it due to the message selector condition. Now my question is why the messages ignored by the second consumer (with message selector) don't get reassigned to the first consumer(without selector). Could anyone help me in identifying the reason for it? -- View this message in context: http://activemq.2283324.n4.nabble.com/Need-help-on-messages-getting-stuck-due-to-message-selector-tp3013173p3013173.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Commented: (AMQ-2988) Allow to retrieve the JMSProperties when using JMS Stream (ActiveMQInputStream)
[ https://issues.apache.org/activemq/browse/AMQ-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62827#action_62827 ] Norman Maurer commented on AMQ-2988: Thx a bunch! Allow to retrieve the JMSProperties when using JMS Stream (ActiveMQInputStream) --- Key: AMQ-2988 URL: https://issues.apache.org/activemq/browse/AMQ-2988 Project: ActiveMQ Issue Type: Improvement Components: Broker Reporter: Norman Maurer Assignee: Timothy Bish Fix For: 5.5.0 Attachments: ActiveMQInputStream_JMSProps.diff, AMQ-2988_junit.diff When using JMS Streams (aka ActiveMQInputStream and ActiveMQOutputStream) its impossible to retrieve the used JMS Properties which where used while writing the OutputStream. The only method which allows this is the ActiveMQInputStream.receive() method. But this will corrupt the InputStream because it will remove the Message from it. So I think it makes sense to add a method for retrieving the Properties. I also think the receive() method should be private or protected to guard against wrong usage ( I used it before to retrieve the properties and wondered why it corrupted the stream). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
[ https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62828#action_62828 ] Abhishek C commented on AMQ-2736: - @Swen Does using non transacted sessions with auto acknowledge clear the log files? We have been facing a similar problem, however we are using Kaha Persistence Adapter on upgrading from 5.3.2 to 5.4.1. We had to upgrade to 5.4.1 because earlier using Durable Subs Topics our data files weren't getting cleaned up. Now our index-subs file are creating an issue. Any Final fix for this problem? KahaDB doesn't clean up old files - Key: AMQ-2736 URL: https://issues.apache.org/activemq/browse/AMQ-2736 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2 Reporter: Adrian Trenaman Priority: Critical Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java Over time, we're seeing that kahadb doesn't clean up old journal files. As a result, we eventually run out of disk space, or rather, we hit our usage limits and our producers are slowed down by the producer flow control mechanism. Others have experienced this problem too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/%3c27502591.p...@talk.nabble.com%3e) For now, we're moving back to the old amqPersistenceStore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Failed to resolve artifact: xmlpull:xmlpull:jar:1.1.3.4d_b4_min
I found that a xmlpull dependency is missing from central repo. Does anyone know how to report this kind of issues ? * [INFO] * * [ERROR] BUILD ERROR* * [INFO] * * [INFO] Failed to resolve artifact.* * * * Missing:* * --* * 1) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * Try downloading the file manually from the project website.* * * * Then, install it using the command: * * mvn install:install-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file* * * * Alternatively, if you host your own repository you can deploy the file there: * * mvn deploy:deploy-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]* * * * Path to dependency: * * 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * 2) org.apache.activemq:activemq-web:jar:5.4.1* * 3) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * --* * 1 required artifact is missing.* * * * for artifact: * * org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * * * from the specified remote repositories:* * central (http://repo1.maven.org/maven2),* * codehaus.snapshots (http://snapshots.repository.codehaus.org),* * apache.snapshots (http://repository.apache.org/snapshots),* -- Shawn
Re: Failed to resolve artifact: xmlpull:xmlpull:jar:1.1.3.4d_b4_min
Hi, this is fixed on the trunk, so instead of xmlpull we now use xpp3 version 1.1.4c. If you need to build the older version, you can use a bit older version 1.1.3.4a of xmlpull, just change xmlpull-version in pom.xml Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Oct 26, 2010 at 10:40 AM, Shawn Jiang genspr...@gmail.com wrote: I found that a xmlpull dependency is missing from central repo. Does anyone know how to report this kind of issues ? * [INFO] * * [ERROR] BUILD ERROR* * [INFO] * * [INFO] Failed to resolve artifact.* * * * Missing:* * --* * 1) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * Try downloading the file manually from the project website.* * * * Then, install it using the command: * * mvn install:install-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file* * * * Alternatively, if you host your own repository you can deploy the file there: * * mvn deploy:deploy-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]* * * * Path to dependency: * * 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * 2) org.apache.activemq:activemq-web:jar:5.4.1* * 3) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * --* * 1 required artifact is missing.* * * * for artifact: * * org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * * * from the specified remote repositories:* * central (http://repo1.maven.org/maven2),* * codehaus.snapshots (http://snapshots.repository.codehaus.org),* * apache.snapshots (http://repository.apache.org/snapshots),* -- Shawn
Re: Failed to resolve artifact: xmlpull:xmlpull:jar:1.1.3.4d_b4_min
Thanks, I'll use the older version to build. On Tue, Oct 26, 2010 at 4:47 PM, Dejan Bosanac de...@nighttale.net wrote: Hi, this is fixed on the trunk, so instead of xmlpull we now use xpp3 version 1.1.4c. If you need to build the older version, you can use a bit older version 1.1.3.4a of xmlpull, just change xmlpull-version in pom.xml Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Oct 26, 2010 at 10:40 AM, Shawn Jiang genspr...@gmail.com wrote: I found that a xmlpull dependency is missing from central repo. Does anyone know how to report this kind of issues ? * [INFO] * * [ERROR] BUILD ERROR* * [INFO] * * [INFO] Failed to resolve artifact.* * * * Missing:* * --* * 1) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * Try downloading the file manually from the project website.* * * * Then, install it using the command: * * mvn install:install-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file* * * * Alternatively, if you host your own repository you can deploy the file there: * * mvn deploy:deploy-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]* * * * Path to dependency: * * 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * 2) org.apache.activemq:activemq-web:jar:5.4.1* * 3) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * --* * 1 required artifact is missing.* * * * for artifact: * * org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * * * from the specified remote repositories:* * central (http://repo1.maven.org/maven2),* * codehaus.snapshots (http://snapshots.repository.codehaus.org),* * apache.snapshots (http://repository.apache.org/snapshots),* -- Shawn -- Shawn
[jira] Created: (AMQ-2998) JVM crash when stopping a connection from a client
JVM crash when stopping a connection from a client -- Key: AMQ-2998 URL: https://issues.apache.org/activemq/browse/AMQ-2998 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.3.0 Environment: Broker running on Ubuntu 64, jvm 1.6.0_20. Client running on Scientific Linux CERN SLC release 4.8 JVM 1.5.0_17 Reporter: andrea manzi My Message Producer client code, in case of an exception sending message to the broker, tries to close the connections and recreate it. After more than one year without problems yesterday I got a crash on Producer client side. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2998) JVM crash when stopping a connection from a client
[ https://issues.apache.org/activemq/browse/AMQ-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] andrea manzi updated AMQ-2998: -- Attachment: hs_err_pid15885.log JVM crash when stopping a connection from a client -- Key: AMQ-2998 URL: https://issues.apache.org/activemq/browse/AMQ-2998 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.3.0 Environment: Broker running on Ubuntu 64, jvm 1.6.0_20. Client running on Scientific Linux CERN SLC release 4.8 JVM 1.5.0_17 Reporter: andrea manzi Attachments: hs_err_pid15885.log My Message Producer client code, in case of an exception sending message to the broker, tries to close the connections and recreate it. After more than one year without problems yesterday I got a crash on Producer client side. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2998) JVM crash when stopping a connection from a client
[ https://issues.apache.org/activemq/browse/AMQ-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] andrea manzi updated AMQ-2998: -- Attachment: hs_err_pid15885.log Correct version of the jvm dump log JVM crash when stopping a connection from a client -- Key: AMQ-2998 URL: https://issues.apache.org/activemq/browse/AMQ-2998 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.3.0 Environment: Broker running on Ubuntu 64, jvm 1.6.0_20. Client running on Scientific Linux CERN SLC release 4.8 JVM 1.5.0_17 Reporter: andrea manzi Attachments: hs_err_pid15885.log, hs_err_pid15885.log My Message Producer client code, in case of an exception sending message to the broker, tries to close the connections and recreate it. After more than one year without problems yesterday I got a crash on Producer client side. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Need help on messages getting stuck due to message selector
they should do, can you post your test case? On 26 October 2010 07:06, dayanand dayana...@gmail.com wrote: Hi, I am facing an issue regarding some messages get stuck in the queue. The background of the issue is. 1. We have 2 consumers configured to listen to the same queue. 2. One consumer has a message selector criteria set while the other doesn't. 3. When the messages are pushed into the queue, they basically get shared between the consumers. 4. The consumer which doesn't have the criteria processes the messages assigned to it without any issue. 5. But the consumer that has the selection criteria doesn't process the messages assigned to it due to the message selector condition. Now my question is why the messages ignored by the second consumer (with message selector) don't get reassigned to the first consumer(without selector). Could anyone help me in identifying the reason for it? -- View this message in context: http://activemq.2283324.n4.nabble.com/Need-help-on-messages-getting-stuck-due-to-message-selector-tp3013173p3013173.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- http://blog.garytully.com http://fusesource.com
[jira] Created: (AMQ-2999) peer transport factory mapping localhost incorrectly to loopback
peer transport factory mapping localhost incorrectly to loopback Key: AMQ-2999 URL: https://issues.apache.org/activemq/browse/AMQ-2999 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.4.1, 5.4.0, 5.3.2 Environment: Windows XP 32-bit, SUN JDK 1.6 update 21 Reporter: Petri Riipinen Issue described in the first posting of that thread: http://activemq.2283324.n4.nabble.com/Problem-with-simple-peer-configuration-my-config-or-AMQ-issue-td3013268.html#a3013268 Reply from Gary Tully explains the problem: That looks like a bug in the peer transport factory. I uses localhost:0 as the tcp transport url, but localhost maps to the loopback address since 5.3[1] so the connection is refused. The peer transport factory should use the wildcard address, 0.0.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2982) Sticky KahaDB log files due to local transaction rollback
[ https://issues.apache.org/activemq/browse/AMQ-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-2982. Resolution: Fixed Fix Version/s: 5.5.0 Assignee: Dejan Bosanac Fixed with svn revision 1027453. Thanks for the patch! Sticky KahaDB log files due to local transaction rollback - Key: AMQ-2982 URL: https://issues.apache.org/activemq/browse/AMQ-2982 Project: ActiveMQ Issue Type: Bug Components: Message Store Affects Versions: 5.4.1 Environment: Ubuntu 10.04, Java 1.6 Mac OS X 10.5, Java 1.6.0_20 Reporter: Swen Moczarski Assignee: Dejan Bosanac Fix For: 5.5.0 Attachments: AMQ2982Fix.patch, AMQ2982Test.patch On a rollback of a local transaction the transaction won't be removed from the inflight transaction list of the KahaDB MessageDatabase. This leads to KahaDB log files which won't be deleted even if there are no messages which are referred by the log file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2919) OutOfMemory exception possible when using ByteMessage-s due to JVM bug
[
https://issues.apache.org/activemq/browse/AMQ-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62833#action_62833
]
Tim George commented on AMQ-2919:
-
We are experiencing a problem in 5.4.1 (with Spring 3.0.4) which appears to be
related to this fix. No problems with 5.4.0 and the same configuration.
It looks like ActiveMQBytesMessage.storeContent closes the DeflaterStream
prematurely, leaving initializeWriting with nothing to close.
Error log:
{noformat}
Caused by: java.lang.NullPointerException: Deflater has been closed
at java.util.zip.Deflater.ensureOpen(Deflater.java:427)
at java.util.zip.Deflater.deflate(Deflater.java:305)
at
java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:159)
at
java.util.zip.DeflaterOutputStream.finish(DeflaterOutputStream.java:134)
at
java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:146)
at java.io.FilterOutputStream.close(FilterOutputStream.java:143)
at
org.apache.activemq.command.ActiveMQBytesMessage$1.close(ActiveMQBytesMessage.java:808)
at java.io.FilterOutputStream.close(FilterOutputStream.java:143)
at
org.apache.activemq.command.ActiveMQBytesMessage.storeContent(ActiveMQBytesMessage.java:124)
at
org.apache.activemq.command.ActiveMQBytesMessage.reset(ActiveMQBytesMessage.java:765)
...
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:565)
at
org.springframework.jms.core.JmsTemplate$3.doInJms(JmsTemplate.java:536)
at
org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:534)
{noformat}
OutOfMemory exception possible when using ByteMessage-s due to JVM bug
--
Key: AMQ-2919
URL: https://issues.apache.org/activemq/browse/AMQ-2919
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.4.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.4.1
Due to following http://bugs.sun.com/view_bug.do?bug_id=4797189 the custom
deflator is not closed when used with DeflaterOutputStream. A workaround is
to explicitly close it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-2999) peer transport factory mapping localhost incorrectly to loopback
[ https://issues.apache.org/activemq/browse/AMQ-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reassigned AMQ-2999: --- Assignee: Gary Tully peer transport factory mapping localhost incorrectly to loopback Key: AMQ-2999 URL: https://issues.apache.org/activemq/browse/AMQ-2999 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2, 5.4.0, 5.4.1 Environment: Windows XP 32-bit, SUN JDK 1.6 update 21 Reporter: Petri Riipinen Assignee: Gary Tully Issue described in the first posting of that thread: http://activemq.2283324.n4.nabble.com/Problem-with-simple-peer-configuration-my-config-or-AMQ-issue-td3013268.html#a3013268 Reply from Gary Tully explains the problem: That looks like a bug in the peer transport factory. I uses localhost:0 as the tcp transport url, but localhost maps to the loopback address since 5.3[1] so the connection is refused. The peer transport factory should use the wildcard address, 0.0.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2999) peer transport factory mapping localhost incorrectly to loopback
[ https://issues.apache.org/activemq/browse/AMQ-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-2999. - Resolution: Fixed Fix Version/s: 5.5.0 resolved in 1027461, wildcard address is now used for the tcp transport. If necessary we can make this configurable. peer transport factory mapping localhost incorrectly to loopback Key: AMQ-2999 URL: https://issues.apache.org/activemq/browse/AMQ-2999 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2, 5.4.0, 5.4.1 Environment: Windows XP 32-bit, SUN JDK 1.6 update 21 Reporter: Petri Riipinen Assignee: Gary Tully Fix For: 5.5.0 Issue described in the first posting of that thread: http://activemq.2283324.n4.nabble.com/Problem-with-simple-peer-configuration-my-config-or-AMQ-issue-td3013268.html#a3013268 Reply from Gary Tully explains the problem: That looks like a bug in the peer transport factory. I uses localhost:0 as the tcp transport url, but localhost maps to the loopback address since 5.3[1] so the connection is refused. The peer transport factory should use the wildcard address, 0.0.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-2983) Sticky KahaDB log files due to concurrent consumer with local transaction
[ https://issues.apache.org/activemq/browse/AMQ-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-2983: -- Assignee: Dejan Bosanac Sticky KahaDB log files due to concurrent consumer with local transaction - Key: AMQ-2983 URL: https://issues.apache.org/activemq/browse/AMQ-2983 Project: ActiveMQ Issue Type: Bug Components: Message Store Affects Versions: 5.4.1 Environment: Ubuntu 10.04, Java 1.6 Mac OS X 10.5, Java 1.6.0_20 Reporter: Swen Moczarski Assignee: Dejan Bosanac Attachments: AMQ2983Test.patch Concurrent consumer with local transactional session and session.receive() leads to KahaDB log files which won't be deleted even if there are no messages which are referred by the log file. Please, see the attached test case. If only one consumer is configured it seems to work, but with more than one concurrent consumer the test fails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
[ https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62845#action_62845 ] Jeff Genender commented on AMQ-2736: Folks.. Please try the patch supplied above: https://issues.apache.org/activemq/secure/attachment/19715/amq-2987.patch That appears to fix the problem with the AMQ-2736.zip test. KahaDB doesn't clean up old files - Key: AMQ-2736 URL: https://issues.apache.org/activemq/browse/AMQ-2736 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2 Reporter: Adrian Trenaman Priority: Critical Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java Over time, we're seeing that kahadb doesn't clean up old journal files. As a result, we eventually run out of disk space, or rather, we hit our usage limits and our producers are slowed down by the producer flow control mechanism. Others have experienced this problem too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/%3c27502591.p...@talk.nabble.com%3e) For now, we're moving back to the old amqPersistenceStore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
[ https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62846#action_62846 ] Jeff Genender commented on AMQ-2736: @Christer WIkman - Gary's attachment wasn't a patch... it was a revert to the test case to validate the test case fails. Please try my patch. KahaDB doesn't clean up old files - Key: AMQ-2736 URL: https://issues.apache.org/activemq/browse/AMQ-2736 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2 Reporter: Adrian Trenaman Priority: Critical Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java Over time, we're seeing that kahadb doesn't clean up old journal files. As a result, we eventually run out of disk space, or rather, we hit our usage limits and our producers are slowed down by the producer flow control mechanism. Others have experienced this problem too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/%3c27502591.p...@talk.nabble.com%3e) For now, we're moving back to the old amqPersistenceStore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2455) Need a facility to retry jms connections to a foreign provider by the ActiveMQ JMS bridge.
[ https://issues.apache.org/activemq/browse/AMQ-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62847#action_62847 ] Trey Hyde commented on AMQ-2455: This issue is certainly not fixed for me in 5.4.1. Is there any additional configuration I need to do? Source and config for my bridge setup to OpenMQ is here : http://github.com/centraldesktop/openmq-spring-bean Need a facility to retry jms connections to a foreign provider by the ActiveMQ JMS bridge. -- Key: AMQ-2455 URL: https://issues.apache.org/activemq/browse/AMQ-2455 Project: ActiveMQ Issue Type: New Feature Components: Broker Environment: Debian Lenny. ActiveMQ 5.2. OpenJMS-0.7.7-beta-1 Reporter: Billy Buzzard Assignee: Rob Davies Fix For: 5.4.0 Attachments: bridge-reconnect.patch, test.zip I followed an example (http://www.codeproject.com/KB/docview/jms_to_jms_bridge_activem.aspx?display=Print) showing how to set up a bridge between OpenJMS and ActiveMQ. The bridge seems to work perfectly until I stop then restart OpenJMS while leaving ActiveMQ running. Once I restart OpenJMS I try sending a message from it to ActiveMQ, but ActiveMQ doesn't receive it until I stop and restart ActiveMQ. I can recreate the exact same problem by starting ActiveMQ first and then OpenJMS. After a little more reading it looks like failover should fix this problem, but I tried it and it didn't work. I submitted a question to ActiveMQ and Gary Tully responded and told me there is currently no facility to retry jms connections to a foreign provider by the ActiveMQ JMS bridge. Assuming that remote end-points may not be using ActiveMQ then I would think this would be a very important feature to have. Here's a link to our conversation: http://www.nabble.com/How-to-configure-failover-for-jmsBridgeConnector-td25909047.html#a25918800 The conversation also contains an attachment showing me configuration file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2513) JMX bug - javax.management.InstanceNotFoundException
[ https://issues.apache.org/activemq/browse/AMQ-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62848#action_62848 ] Vadim Katz commented on AMQ-2513: - I am seeing this issue with managementContext managementContext connectorPort=1063 jmxDomainName=org.apache.activemq/ /managementContext specified on 5.3.2 broker/client I noticed that the fix has not been applied to 5.3.2 (by looking at the code) Same bug? JMX bug - javax.management.InstanceNotFoundException Key: AMQ-2513 URL: https://issues.apache.org/activemq/browse/AMQ-2513 Project: ActiveMQ Issue Type: Bug Components: JMX Affects Versions: 5.3.1 Reporter: Dariusz Szablinski Assignee: Dejan Bosanac Fix For: 5.3.1, 5.4.0 Attachments: activemq.log, activemq.xml, AMQ2513Test.java, jconsole.jpg How to reproduce: 1) start broker 2) start sending/receiving messages to/from a queue 3) the queue will show up in MBeans tree 4) kill the broker (e.g. end process on windows) 5) stat broker again 6) you can find your queue in Broker-Queues attribute, but not as a separate node on MBeans tree (see screenshot) 7) (optional) start sending/receiving messages to/from a queue 8) open web console. following exception will be thrown: 2009-11-25 21:47:45,525 | ERROR | /admin/queues.jsp;jsessionid=yjy1i2uuahpk | org.mortbay.log | btpool0-1 javax.el.ELException: java.lang.reflect.UndeclaredThrowableException at javax.el.BeanELResolver.getValue(BeanELResolver.java:266) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143) at com.sun.el.parser.AstValue.getValue(AstValue.java:138) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:206) at org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:984) at org.apache.jsp.queues_jsp._jspx_meth_c_forEach_0(org.apache.jsp.queues_jsp:141) at org.apache.jsp.queues_jsp._jspService(org.apache.jsp.queues_jsp:101) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093) at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:81) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:828) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at
Combination of JDBC persistence With and Without Journal
Hi We have a situation where we need to use the 'JDBC persistence with High performance Journal ' for some Queues and 'JDBC persistence without Journal' for some other queues. All the queues should be available at any time. How can we achieve this? Is it possible to create two persistence adapters and share for them between different queues inside a broker? Please advise. Thanks lot. -- View this message in context: http://activemq.2283324.n4.nabble.com/Combination-of-JDBC-persistence-With-and-Without-Journal-tp3014353p3014353.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Created: (AMQ-3000) Multiple Cron Scheduled Messages don't fire every minute as configured
Multiple Cron Scheduled Messages don't fire every minute as configured -- Key: AMQ-3000 URL: https://issues.apache.org/activemq/browse/AMQ-3000 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.1 Environment: Ubuntu Lucid and Windows 2k8 Reporter: Ryan Quam Fix For: 5.5.0 I ran into a scenario where I have multiple Scheduled Messages with a cron string set to fire every minute that are created at different times. However, only one is firing every minute (cycles 0 to 9). I will attach a test Case that could be incorporated into org.apache.activemq.broker.scheduler.JmsSchedulerTest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-3000) Multiple Cron Scheduled Messages don't fire every minute as configured
[ https://issues.apache.org/activemq/browse/AMQ-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Quam updated AMQ-3000: --- Attachment: JmsCronSchedulerTest.java This is a standalone JUnit test. The test method in this could be incorporated into activemq-core/src/test/java/org/apache/activemq/broker/scheduler/JmsSchedulerTest.java without modification. Multiple Cron Scheduled Messages don't fire every minute as configured -- Key: AMQ-3000 URL: https://issues.apache.org/activemq/browse/AMQ-3000 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.1 Environment: Ubuntu Lucid and Windows 2k8 Reporter: Ryan Quam Fix For: 5.5.0 Attachments: JmsCronSchedulerTest.java I ran into a scenario where I have multiple Scheduled Messages with a cron string set to fire every minute that are created at different times. However, only one is firing every minute (cycles 0 to 9). I will attach a test Case that could be incorporated into org.apache.activemq.broker.scheduler.JmsSchedulerTest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
[ https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62853#action_62853 ] Jeff Genender commented on AMQ-2736: Here is the 5.4.1 distribution with the patch in it. This is *not* an official release... could people please test it out? http://people.apache.org/~jgenender/apache-activemq-5.4.1-AMQ2736-bin.tar.gz KahaDB doesn't clean up old files - Key: AMQ-2736 URL: https://issues.apache.org/activemq/browse/AMQ-2736 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2 Reporter: Adrian Trenaman Priority: Critical Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java Over time, we're seeing that kahadb doesn't clean up old journal files. As a result, we eventually run out of disk space, or rather, we hit our usage limits and our producers are slowed down by the producer flow control mechanism. Others have experienced this problem too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/%3c27502591.p...@talk.nabble.com%3e) For now, we're moving back to the old amqPersistenceStore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1611) edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.io.IOException: Already started.
[ https://issues.apache.org/activemq/browse/AMQ-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62854#action_62854 ] Rishi Dev commented on AMQ-1611: Any update on this issue? We are facing similar problems with incubator-activemq-4.0 and will highly appreciate any help. Please refer AMQ-2977 edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.io.IOException: Already started. Key: AMQ-1611 URL: https://issues.apache.org/activemq/browse/AMQ-1611 Project: ActiveMQ Issue Type: Bug Components: Connector Reporter: Aakanksha Singh Fix For: 5.3.0 Hi..I m getting this msg in activemq.log after every 5 minutes..please provide me the solution. 2008-03-06 00:00:10,847 ERROR Failed to checkpoint a message store: edu.emory.mathcs.backport.java.util.concurrent.ExecutionE xception: java.io.IOException: Already started. | org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(Jo urnalPersistenceAdapter.java:395) [ActiveMQ Journal Checkpoint Worker] edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: java.io.IOException: Already started. at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118) at org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:386) at org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129) at org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:101) at org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25) at org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39) Caused by: java.io.IOException: Already started. at org.apache.activemq.store.jdbc.TransactionContext.begin(TransactionContext.java:145) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.beginTransaction(JDBCPersistenceAdapter.java:358) at org.apache.activemq.store.journal.JournalPersistenceAdapter.beginTransaction(JournalPersistenceAdapter.java:189) at org.apache.activemq.util.TransactionTemplate.run(TransactionTemplate.java:41) at org.apache.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:247) at org.apache.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:221) at org.apache.activemq.store.journal.JournalPersistenceAdapter$4.call(JournalPersistenceAdapter.java:356) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
[ https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62855#action_62855 ] Giampaolo Tranchida commented on AMQ-2736: -- Do not work for me, same issue. KahaDB doesn't clean up old files - Key: AMQ-2736 URL: https://issues.apache.org/activemq/browse/AMQ-2736 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2 Reporter: Adrian Trenaman Priority: Critical Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java Over time, we're seeing that kahadb doesn't clean up old journal files. As a result, we eventually run out of disk space, or rather, we hit our usage limits and our producers are slowed down by the producer flow control mechanism. Others have experienced this problem too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/%3c27502591.p...@talk.nabble.com%3e) For now, we're moving back to the old amqPersistenceStore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2736) KahaDB doesn't clean up old files
[ https://issues.apache.org/activemq/browse/AMQ-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=62856#action_62856 ] Giampaolo Tranchida commented on AMQ-2736: -- I think that the fix AMQ-2982 must fix also this issue. KahaDB doesn't clean up old files - Key: AMQ-2736 URL: https://issues.apache.org/activemq/browse/AMQ-2736 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.3.2 Reporter: Adrian Trenaman Priority: Critical Attachments: AMQ-2736.zip, amq-2987-testcase.patch, amq-2987.patch, AMQ2736Test_should_with_this_diff.txt, MyKahaDBStore.java Over time, we're seeing that kahadb doesn't clean up old journal files. As a result, we eventually run out of disk space, or rather, we hit our usage limits and our producers are slowed down by the producer flow control mechanism. Others have experienced this problem too (for example, see http://mail-archives.apache.org/mod_mbox/activemq-users/201002.mbox/%3c27502591.p...@talk.nabble.com%3e) For now, we're moving back to the old amqPersistenceStore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
