Description of problem: jboss hooks (particularly configure) doesn't output anything back to the broker Instead they redirect output to a log. This is problematic if a failure occurs since the app is immediately destroyed. I don't think there is a technical reason we want jboss to behave differently than the other types. Although I know this was done originally because of output streams being left open by starting jboss. We need to find a solution that can solve the steam being left open issue and still return the output to the caller. Note: A simple hack might be to just cat the current log at the end. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 852524 has been marked as a duplicate of this bug. ***
Any update here? Will the new cartridge format fix this?
This will be corrected when ported to new cartridge format.
If a bug is fixed you can mark it ON_QA. Shouldn't close a bug without it going through QE.
We think this is going to be as fixed as possible. It's not perfect but it's better than it was before as a result of some re-work with the v2 format.