Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-18910

[GSS](7.3.z) HAL-1658 - No resource definition registered for ejb deployments on a host slave

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.3.1.CR1, 7.3.1.GA
    • 7.3.0.GA.CR3
    • Web Console
    • None

      This is the downstream description:

      Using the reproducer application from playground.zip, the deployed application cannot be inspected navigating to > Runtime > Server Groups > target-ha-server-group > target-ha-node-2 (on host-controller-1) > EJB > TargetBean > View

      An error occurs, viewing the error message shows:

        Outcome:
    "WFLYCTL0030: No resource definition is registered for address [
        (\"deployment\" => \"playground-roc-target-server.ear\"),
        (\"subdeployment\" => \"playground-roc-target-ejb.jar\"),
        (\"subsystem\" => \"ejb3\"),
        (\"stateless-session-bean\" => \"TargetBean\")
    ]"

      The playground.zip contains a README.md that explains how to use the project to reproduce the issue.

      Note: The issue seems to be fixed already upstream as it does not occur anymore with WildFly 20.0.0.Beta1-SNAPSHOT from commit 87c4841536f7b3e6b208872aa3ab880d80e0eca

      This is a clone of the upstream Jira HAL-1658.

      The Description of the upstream Jira is:

      After deploying an application containing an EJB, the deployed application cannot be inspected navigating to Runtime -> hosts -> slave -> server -> ejb

      The following error is thrown:

      "WFLYCTL0030: No resource definition is registered for address [
    (\"deployment\" => \"ejb-in-war.war\"),
    (\"subsystem\" => \"ejb3\"),
    (\"stateful-session-bean\" => \"GreeterEJB\")
]"

        1. playground.zip
          30 kB

            thofman Tomas Hofman
            rhn-support-jbaesner Joerg Baesner
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: