Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1726

Internal Error accessing EJB Runtime option at Management Console

    XMLWordPrintable

Details

      1. Start Wildfly 21.0.1.Final with standalone-full.xml configuration
      2. Deploy helloworld-mdb quickstart
      3. Enter Management Console
      4. Select Runtime / EJB option
      5. An Internal error message should appear 
    • Compatibility/Configuration
    • Undefined

    Description

      Hi,

      It seems that EJB Runtime monitor at Management Console is broken.

      I cannot monitor EJBs deployed at server because an error happens when the option is selected.

       

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-14157 Internal Error accessing EJB Runtime option at Management Console

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. HAL-1658 No resource definition registered for ejb deployments on a host slave

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21969 (7.3.z) HAL-1726 - Internal Error accessing EJB Runtime option at Management Console

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: