You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Pedro de Lara (JIRA)" <ji...@apache.org> on 2012/07/24 18:43:36 UTC
[jira] [Created] (AMQ-3942) Certain messages do not expire in the
embedded broker
Pedro de Lara created AMQ-3942:
----------------------------------
Summary: Certain messages do not expire in the embedded broker
Key: AMQ-3942
URL: https://issues.apache.org/jira/browse/AMQ-3942
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.6.0, 5.4.3
Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
Reporter: Pedro de Lara
When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pedro de Lara updated AMQ-3942:
-------------------------------
Description:
When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
Test were done on activeMQ running on JDK 1.7.0_03 with the activemq executable script being pointed towards that version (Instead of "auto").
was:
When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on JDK 1.7.0_03 with the activemq executable script being pointed towards that version (Instead of "auto").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (AMQ-3942) Certain messages do not expire
in the embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422115#comment-13422115 ]
Pedro de Lara edited comment on AMQ-3942 at 7/25/12 9:30 AM:
-------------------------------------------------------------
I have now tested against 5.7-SNAPSHOT and still have the same issue. It took a little more effort on the snapshot (For some reason the JMX interface only binds itself to localhost on 5.7 so I had to tunnel) but once I got it running the issue was still there.
I am attaching my activemq.xml file in here which is the only file I have done changes on from the default installation.
Here's what I get out of the Unit Test
_Sleeping 60 seconds to allow for expiration task to expire all messages_
_Queue size is 278_
_DLQ queue size is 22_
was (Author: byteflinger):
I have now tested against 5.7-SNAPSHOT and still have the same issue. It took a little more effort on the snapshot (For some reason the JMX interface only binds itself to localhost on 5.7 so I had to tunnel) but once I got it running the issue was still there.
I am attaching my activemq.xml file in here which is the only file I have done changes on from the default installation.
Here's what I get out of the Unit Test
_emphasis_ Sleeping 60 seconds to allow for expiration task to expire all messages
_emphasis_ Queue size is 278
_emphasis_ DLQ queue size is 22
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pedro de Lara updated AMQ-3942:
-------------------------------
Affects Version/s: 5.7.0
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pedro de Lara updated AMQ-3942:
-------------------------------
Attachment: activemq.xml
ActiveMQ configuration file for embedded broker
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435950#comment-13435950 ]
Timothy Bish commented on AMQ-3942:
-----------------------------------
This has not been reproducible here.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: activemq.xml, ExpirationTest.java, ExpirationTest.java
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on both JDK 1.7.0_03 and 1.6.0_33 with the activemq executable script being pointed towards those versions (Instead of "auto").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422224#comment-13422224 ]
Timothy Bish commented on AMQ-3942:
-----------------------------------
Recommend you try this on Java 1.6 which is the supported version for AMQ 5.6.0. I have not been able to reproduce this issue there.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on JDK 1.7.0_03 with the activemq executable script being pointed towards that version (Instead of "auto").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-3942.
-----------------------------
Resolution: Cannot Reproduce
Assignee: Timothy Bish
Cannot reproduce this.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Assignee: Timothy Bish
> Labels: expiration, timetolive, ttl
> Attachments: activemq.xml, ExpirationTest.java, ExpirationTest.java
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on both JDK 1.7.0_03 and 1.6.0_33 with the activemq executable script being pointed towards those versions (Instead of "auto").
--
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-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422115#comment-13422115 ]
Pedro de Lara commented on AMQ-3942:
------------------------------------
I have now tested against 5.7-SNAPSHOT and still have the same issue. It took a little more effort on the snapshot (For some reason the JMX interface only binds itself to localhost on 5.7 so I had to tunnel) but once I got it running the issue was still there.
I am attaching my activemq.xml file in here which is the only file I have done changes on from the default installation.
Here's what I get out of the Unit Test
_emphasis_ Sleeping 60 seconds to allow for expiration task to expire all messages
_emphasis_ Queue size is 278
_emphasis_ DLQ queue size is 22
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421714#comment-13421714 ]
Timothy Bish commented on AMQ-3942:
-----------------------------------
Can you try your test against a 5.7-SNAPSHOT broker? I ran it here a few times and it passed every time.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422124#comment-13422124 ]
Pedro de Lara commented on AMQ-3942:
------------------------------------
Added more information about java environment activemq is running on.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on JDK 1.7.0_03 with the activemq executable script being pointed towards that version (Instead of "auto").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pedro de Lara updated AMQ-3942:
-------------------------------
Description:
When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
was:
When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422363#comment-13422363 ]
Pedro de Lara commented on AMQ-3942:
------------------------------------
Just tried it on both activeMQ 5.6.0 and 5.7-SNAPSHOT pointing activemq start script to JDK 1.6.0_33 and the issue is still occurring. Anything else that could be causing such an issue other than activeMQ itself that I can test?
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on JDK 1.7.0_03 with the activemq executable script being pointed towards that version (Instead of "auto").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pedro de Lara updated AMQ-3942:
-------------------------------
Attachment: ExpirationTest.java
Unit Test to show issue
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Pedro de Lara (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pedro de Lara updated AMQ-3942:
-------------------------------
Description:
When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
Test were done on activeMQ running on both JDK 1.7.0_03 and 1.6.0_33 with the activemq executable script being pointed towards those versions (Instead of "auto").
was:
When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
Test were done on activeMQ running on JDK 1.7.0_03 with the activemq executable script being pointed towards that version (Instead of "auto").
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on both JDK 1.7.0_03 and 1.6.0_33 with the activemq executable script being pointed towards those versions (Instead of "auto").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3942) Certain messages do not expire in the
embedded broker
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQ-3942:
------------------------------
Attachment: ExpirationTest.java
Simplified the test case for use as a real AMQ unit test, problem does not appear when run on the support Java v1.6.
> Certain messages do not expire in the embedded broker
> -----------------------------------------------------
>
> Key: AMQ-3942
> URL: https://issues.apache.org/jira/browse/AMQ-3942
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.3, 5.6.0, 5.7.0
> Environment: Red Hat Enterprise Linux Server release 6.1 (Santiago)
> Reporter: Pedro de Lara
> Labels: expiration, timetolive, ttl
> Attachments: ExpirationTest.java, ExpirationTest.java, activemq.xml
>
>
> When sending messages to a queue and waiting for the expiration task to expire them, only some of the expired messages are moved to the DLQ. Other expired messages (With same expiration time as the ones moved to the DLQ) just sit in the queue, stuck until all messages in the queue expire, at which point they are all moved to the DLQ.
> This seems to happen only in the embedded broker (configured in activemq.xml) and only for some messages (It seems the size of the message however I am uncertain if the content could actually cause such an issue).
> A Unit Test is provided that shows the issue. The unit test includes a boolean that can be changed to run it towards a created broker (instead of the embedded one) for comparison purposes.
> An activemq configuration file (activemq.xml) is also provided as it is the only file that has been changed from default installation.
> Test were done on activeMQ running on JDK 1.7.0_03 with the activemq executable script being pointed towards that version (Instead of "auto").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira