Petals ESB Container

Lack of robustness if we play with JMX

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Trivial Trivial
  • Resolution: Fixed
  • Affects Version/s: 3.1.1
  • Fix Version/s: 3.1.2, 4.0.0
  • Security Level: Public
  • Description:
    Hide

    The container remains stuck after an unusual usage.

    1. Run the JConsole and onnect to brand new Petals through JMX (start Petals first).
    2. Load a new installer for a component (e.g. the sample client). Petals is fine with this.
    3. Invoke the same JMX operation with the same parameter (basially, clcik the button from the JConsole a second time). Peals displays an exception.
    4. Try to invoke another JMX operation (e.g. startComponent). Nothing happens in the Petals console.
    5. Try to shutdown Petals from the command line, by invoking the shutdown script. Nothing happens in the Petals console.
    6. 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).

    Show
    The container remains stuck after an unusual usage.
    1. Run the JConsole and onnect to brand new Petals through JMX (start Petals first).
    2. Load a new installer for a component (e.g. the sample client). Petals is fine with this.
    3. Invoke the same JMX operation with the same parameter (basially, clcik the button from the JConsole a second time). Peals displays an exception.
    4. Try to invoke another JMX operation (e.g. startComponent). Nothing happens in the Petals console.
    5. Try to shutdown Petals from the command line, by invoking the shutdown script. Nothing happens in the Petals console.
    6. 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).
  • Environment:
    Windows XP

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
171d 23h 9m
1
Christophe DENEUX
Fri, 29 Apr 2011 - 16:49:38 +0200
Open Open In Progress In Progress
5s
1
Christophe DENEUX
Fri, 29 Apr 2011 - 16:49:43 +0200
In Progress In Progress Resolved Resolved
7s
1
Christophe DENEUX
Fri, 29 Apr 2011 - 16:49:50 +0200

People

Dates

  • Created:
    Mon, 8 Nov 2010 - 16:40:25 +0100
    Updated:
    Fri, 29 Apr 2011 - 16:55:40 +0200
    Resolved:
    Fri, 29 Apr 2011 - 16:49:50 +0200