This seems like a good approach, although I admit the details are not
really familiar to me. My only concern is whether this in any way will
adversely affect the start/deploy/undeploy/stop cycle in the
Arquillian-based itest-2 modules, or any of our related test services.
We may not know until we try.
On 5/23/2013 11:03 AM, Michael Foley wrote:
Thomas,
The regression risk on this approach is much much less than the
previous approach. I am therefore +1 on this approach.
Regards,
Michael Foley
QE Lead, JBoss Operations Network
------------------------------------------------------------------------
*From: *"Thomas Segismont" <tsegismo(a)redhat.com>
*To: *rhq-devel(a)lists.fedorahosted.org
*Sent: *Thursday, May 23, 2013 6:47:12 AM
*Subject: *BZ957689 Unable to complete tasks when server is shutdown
Hi everyone,
Lately I have been working on BZ957689 (Unable to complete tasks when
server is shutdown)
https://bugzilla.redhat.com/show_bug.cgi?id=957689
I have captured my findings and made a proposal in a wiki page:
https://docs.jboss.org/author/display/RHQ/Shutdown+process+on+AS7
Please read it and tell me if you think there is a better way to fix the
issue.
Thanks and regards,
Thomas
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel