The container remains stuck after an unusual usage.
- Run the JConsole and onnect to brand new Petals through JMX (start Petals first).
- Load a new installer for a component (e.g. the sample client). Petals is fine with this.
- Invoke the same JMX operation with the same parameter (basially, clcik the button from the JConsole a second time). Peals displays an exception.
- Try to invoke another JMX operation (e.g. startComponent). Nothing happens in the Petals console.
- Try to shutdown Petals from the command line, by invoking the shutdown script. Nothing happens in the Petals console.
- Try to copy a component in the install directory. Five minutes later, it is still here.
The container should handle this without remaining stuck.
It should still react, even if the user makes a mistake (in purpose or not is not the deal here).