You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Geoff Holden (JIRA)" <ji...@apache.org> on 2008/05/27 14:35:54 UTC
[jira] Created: (AMQ-1748) Deadlock when TempUsage limit reached
Deadlock when TempUsage limit reached
-------------------------------------
Key: AMQ-1748
URL: https://issues.apache.org/activemq/browse/AMQ-1748
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.1.0, 5.0.0
Environment: Tested on Linux
Reporter: Geoff Holden
Attachments: TempUsageDeadlock.patch
If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1748) Deadlock when TempUsage limit reached
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1748.
-----------------------------
Fix Version/s: 5.2.0
Resolution: Fixed
Patch applied in SVN revision 660555
> Deadlock when TempUsage limit reached
> -------------------------------------
>
> Key: AMQ-1748
> URL: https://issues.apache.org/activemq/browse/AMQ-1748
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0
> Environment: Tested on Linux
> Reporter: Geoff Holden
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1748) Deadlock when TempUsage limit reached
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1748.
-----------------------------
Resolution: Fixed
Fixed by SVN revision 661295
> Deadlock when TempUsage limit reached
> -------------------------------------
>
> Key: AMQ-1748
> URL: https://issues.apache.org/activemq/browse/AMQ-1748
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0
> Environment: Tested on Linux
> Reporter: Geoff Holden
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1748) Deadlock when TempUsage limit reached
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1748:
-------------------------------
Assignee: Rob Davies
> Deadlock when TempUsage limit reached
> -------------------------------------
>
> Key: AMQ-1748
> URL: https://issues.apache.org/activemq/browse/AMQ-1748
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0
> Environment: Tested on Linux
> Reporter: Geoff Holden
> Assignee: Rob Davies
> Attachments: TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (AMQ-1748) Deadlock when TempUsage limit reached
Posted by "Geoff Holden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Holden reopened AMQ-1748:
-------------------------------
> Deadlock when TempUsage limit reached
> -------------------------------------
>
> Key: AMQ-1748
> URL: https://issues.apache.org/activemq/browse/AMQ-1748
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0
> Environment: Tested on Linux
> Reporter: Geoff Holden
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: missing-file.patch, TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (AMQ-1748) Deadlock when TempUsage limit reached
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reopened AMQ-1748:
-----------------------------
Regression: [Broken Unit Test]
> Deadlock when TempUsage limit reached
> -------------------------------------
>
> Key: AMQ-1748
> URL: https://issues.apache.org/activemq/browse/AMQ-1748
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0
> Environment: Tested on Linux
> Reporter: Geoff Holden
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1748) Deadlock when TempUsage limit reached
Posted by "Geoff Holden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Holden updated AMQ-1748:
------------------------------
Attachment: missing-file.patch
I had accidentally left a file out of the previous patch.
I've attached a patch for that missing file, which should take care of the unit test regressions.
> Deadlock when TempUsage limit reached
> -------------------------------------
>
> Key: AMQ-1748
> URL: https://issues.apache.org/activemq/browse/AMQ-1748
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0
> Environment: Tested on Linux
> Reporter: Geoff Holden
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: missing-file.patch, TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1748) Deadlock when TempUsage limit reached
Posted by "Geoff Holden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoff Holden resolved AMQ-1748.
-------------------------------
Resolution: Fixed
> Deadlock when TempUsage limit reached
> -------------------------------------
>
> Key: AMQ-1748
> URL: https://issues.apache.org/activemq/browse/AMQ-1748
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0
> Environment: Tested on Linux
> Reporter: Geoff Holden
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: missing-file.patch, TempUsageDeadlock.patch
>
>
> If a SystemUsage limit is set on TempUsage, and that limit is reached, that queue enters a state of deadlock where messages need to be removed so new ones can be added, but they can't be removed because the objects are locked.
> I have a patch attached to this issue where the synchronization in StoreQueueCursor and FilePendingMessageCursor is reworked to get around this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.