Bug 1063864 - Backport of HornetQ-1278 into JBoss EAP
Summary: Backport of HornetQ-1278 into JBoss EAP
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.1.0
Hardware: All
OS: All
Target Milestone: DR2
: EAP 6.3.0
Assignee: Clebert Suconic
QA Contact: Martin Svehla
Russell Dickenson
Depends On: 998823 1064596
TreeView+ depends on / blocked
Reported: 2014-02-11 14:57 UTC by Tom Ross
Modified: 2018-12-02 15:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In older versions of JBoss EAP 6, Scheduled Delivery Handling did a full cycle of serial search on a List for Scheduled Deliveries. This could cause performance issues as the system could use high CPU resources to proceed with many scheduled deliveries under load. This release of the product has implemented a sorted list and proper search up to the expired times. The list search now runs much faster without the high CPU burden.
Clone Of: 998823
Last Closed: 2014-08-06 14:40:02 UTC
Type: Bug

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat One Jira Issue Tracker HORNETQ-1278 Major Closed Full scheduledReferences traversal in every call to ScheduledDeliveryHandlerImpl$ScheduledDeliveryRunnable.run() 2017-10-17 07:37:20 UTC

Description Tom Ross 2014-02-11 14:57:38 UTC
+++ This bug was initially created as a clone of Bug #998823 +++

Description of problem:
Back port of HornetQ-1047 into SOA 5.3.1

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

--- Additional comment from JBoss JIRA Server on 2013-08-23 21:30:38 BST ---

Justin Bertram <jbertram@redhat.com> updated the status of jira HORNETQ-1047 to Resolved

Comment 1 Clebert Suconic 2014-02-12 20:37:21 UTC

Comment 2 Kabir Khan 2014-04-04 14:47:27 UTC
Setting to ON_QA since upgrade should fix this

Comment 4 Martin Svehla 2014-04-22 07:20:23 UTC
Verified with EAP 6.3.0.ER1 / HornetQ 2.3.18

Note You need to log in before you can comment on or make changes to this bug.