Application Server 3  4  5 and 6
  1. Application Server 3 4 5 and 6
  2. JBAS-6620 JON/Open Console Issues
  3. JBAS-6939

after stopping a Topic or Queue via the stop operation, calling getRunState() on the corresponding component returns RunState.RUNNING, rather than RunState.STOPPED

    Details

    • Similar Issues:
      Show 10 results 

      Gliffy Diagrams

        Issue Links

          Activity

          Hide
          Scott Stark added a comment -

          The ManagedComponentImpl.getRunState() is not being updated after the component creation. There is a updateRunState() method on ManagedComponentImpl, but the ManagedComponent.getRunState() implementation is not using this. It would require that the run state be mapped to a property in order for it to work, so we should be proxying the getRunState back to the server to retrieve the current status.

          Show
          Scott Stark added a comment - The ManagedComponentImpl.getRunState() is not being updated after the component creation. There is a updateRunState() method on ManagedComponentImpl, but the ManagedComponent.getRunState() implementation is not using this. It would require that the run state be mapped to a property in order for it to work, so we should be proxying the getRunState back to the server to retrieve the current status.
          Hide
          Scott Stark added a comment -

          Another issue with operations that map to lifecycle methods is that this should be sent through the component controller so that dependencies are properly handled.

          Show
          Scott Stark added a comment - Another issue with operations that map to lifecycle methods is that this should be sent through the component controller so that dependencies are properly handled.
          Hide
          Jason Greene added a comment -

          Moving to 5.1.1

          Show
          Jason Greene added a comment - Moving to 5.1.1
          Hide
          Jason Greene added a comment -

          There will not be a 5.1.1, moving to 5.2 for now

          Show
          Jason Greene added a comment - There will not be a 5.1.1, moving to 5.2 for now

            People

            • Assignee:
              Emanuel Muckenhuber
              Reporter:
              Ian Springer
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development