Back to bug 1021018

Who When What Removed Added
mark yarborough 2013-10-25 14:19:45 UTC Target Release --- JON 3.2.0
CC myarboro
Severity unspecified high
Larry O'Leary 2014-01-08 22:21:37 UTC Target Release JON 3.2.0 JON 3.2.1
Stefan Negrea 2014-02-11 19:42:47 UTC Status NEW ASSIGNED
CC snegrea
Assignee rhq-maint snegrea
Larry O'Leary 2014-02-14 01:54:38 UTC Target Release JON 3.2.1 JON 3.2.2
Radim Hatlapatka 2014-04-18 12:15:30 UTC CC rhatlapa
Stefan Negrea 2014-05-22 19:37:08 UTC Status ASSIGNED ON_QA
Target Milestone --- ER01
Stefan Negrea 2014-05-22 19:39:21 UTC Blocks 1100432
Simeon Pinder 2014-05-22 21:37:00 UTC Status ON_QA MODIFIED
CC spinder
Target Milestone ER01 DR02
Simeon Pinder 2014-05-30 15:54:41 UTC Target Release JON 3.2.2 One-off release
Blocks 1088652
Larry O'Leary 2014-07-03 20:55:02 UTC Target Release One-off release JON 3.3.0
CC loleary
Target Milestone DR02 ---
Larry O'Leary 2014-07-14 23:24:45 UTC Blocks 1119501
Larry O'Leary 2014-07-14 23:27:53 UTC Blocks 1088652
Simeon Pinder 2014-07-31 15:52:08 UTC Status MODIFIED ON_QA
Target Milestone --- DR01
Armine Hovsepyan 2014-09-11 13:12:14 UTC Status ON_QA VERIFIED
CC ahovsepy
Jared MORGAN 2014-10-26 23:28:11 UTC Doc Text ==DRAFT WRITTEN BY JMORGAN==
It was discovered that the EAP 6 plug-in's method execution timeout ignored the rhq.agent.plugins.availability-scan.timeout setting. It persisted the EAP 6 scan timeout setting, which made the behavior of the scan timeout unpredictable. The fix now uses the container's availability timeout for sync availability checks and improves the usage plug-in configuration settings for asynchronous availability of server components.
Flags needinfo?(snegrea)
Jared MORGAN 2014-11-04 03:57:59 UTC Doc Text ==DRAFT WRITTEN BY JMORGAN==
It was discovered that the EAP 6 plug-in's method execution timeout ignored the rhq.agent.plugins.availability-scan.timeout setting. It persisted the EAP 6 scan timeout setting, which made the behavior of the scan timeout unpredictable. The fix now uses the container's availability timeout for sync availability checks and improves the usage plug-in configuration settings for asynchronous availability of server components.
==NEEDINFO: DRAFT WRITTEN BY JMORGAN==

It was discovered that the EAP 6 plug-in's method execution timeout ignored the rhq.agent.plugins.availability-scan.timeout setting. It persisted the EAP 6 scan timeout setting, which made the behavior of the scan timeout unpredictable. The fix now uses the container's availability timeout for sync availability checks and improves the usage plug-in configuration settings for asynchronous availability of server components.
Jared MORGAN 2014-11-18 06:24:55 UTC Doc Text ==NEEDINFO: DRAFT WRITTEN BY JMORGAN==

It was discovered that the EAP 6 plug-in's method execution timeout ignored the rhq.agent.plugins.availability-scan.timeout setting. It persisted the EAP 6 scan timeout setting, which made the behavior of the scan timeout unpredictable. The fix now uses the container's availability timeout for sync availability checks and improves the usage plug-in configuration settings for asynchronous availability of server components.
It was discovered that the EAP 6 plug-in's method execution timeout ignored the rhq.agent.plugins.availability-scan.timeout setting. It persisted the EAP 6 scan timeout setting, which made the behavior of the scan timeout unpredictable. The fix now uses the container's availability timeout for sync availability checks and improves the usage plug-in configuration settings for asynchronous availability of server components.
Flags needinfo?(snegrea)
mark yarborough 2014-12-11 14:04:33 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-12-11 09:04:33 UTC

Back to bug 1021018