Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2530

:read-boot-errors() operation does not follow its operation description

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.0.0.Beta11
    • 3.0.0.Beta7
    • None
    • None
    • Hide

      In domain mode set all ports of full-sockets to 80: 

      <socket-binding-group name="full-sockets" default-interface="public">
    <socket-binding name="ajp" port="${jboss.ajp.port:80}"/>
    <socket-binding name="http" port="${jboss.http.port:80}"/>
    <socket-binding name="https" port="${jboss.https.port:80}"/>
    <socket-binding name="iiop" interface="unsecure" port="80"/>
    <socket-binding name="iiop-ssl" interface="unsecure" port="80"/>
    <socket-binding name="txn-recovery-environment" port="80"/>
    <socket-binding name="txn-status-manager" port="80"/>
    <outbound-socket-binding name="mail-smtp">
        <remote-destination host="localhost" port="80"/>
    </outbound-socket-binding>
</socket-binding-group>

      server-one and server-two will start with boot errors

      Show
      In domain mode set all ports of full-sockets to 80: <socket-binding-group name= "full-sockets" default - interface = " public " > <socket-binding name= "ajp" port= "${jboss.ajp.port:80}" /> <socket-binding name= "http" port= "${jboss.http.port:80}" /> <socket-binding name= "https" port= "${jboss.https.port:80}" /> <socket-binding name= "iiop" interface = "unsecure" port= "80" /> <socket-binding name= "iiop-ssl" interface = "unsecure" port= "80" /> <socket-binding name= "txn-recovery-environment" port= "80" /> <socket-binding name= "txn-status-manager" port= "80" /> <outbound-socket-binding name= "mail-smtp" > <remote-destination host= "localhost" port= "80" /> </outbound-socket-binding> </socket-binding-group> server-one and server-two will start with boot errors

    Description

      The reply properties of the :read-boot-errors() operation lists the attribute missing-transitive-dependency-problems which is defined as 

      "missing-transitive-dependency-problems" => {
    "type" => OBJECT,
    "description" => "Missing transitive dependency issues found during execution of the operation.",
    "expressions-allowed" => false,
    "required" => false,
    "nillable" => true,
    "value-type" => {
        "services-missing-transitive-dependencies" => {
            "type" => LIST,
            "description" => "Services that had a missing transitive dependency.",
            "expressions-allowed" => false,
            "required" => true,
            "nillable" => false,
            "value-type" => STRING
        },
        "possible-causes" => {
            "type" => LIST,
            "description" => "Services that are missing and may be the cause of the missing transitive dependency.",
            "expressions-allowed" => false,
            "required" => true,
            "nillable" => false,
            "value-type" => STRING
        }
    }
}

      However the result uses the strings "Services that were unable to start:" and "Services that may be the cause:" instead of services-missing-transitive-dependencies and possible-causes: 

      ...
    "missing-transitive-dependency-problems" => {
        "Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"],
        "Services that may be the cause:" => [
            "jboss.http-upgrade-registry.default",
            "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
        ]
    }
...

      Attachments

        Activity

          People

            ehugonne1@redhat.com Emmanuel Hugonnet
            hpehl@redhat.com Harald Pehl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: