[jboss-jira] [JBoss JIRA] (WFCORE-2530) :read-boot-errors() operation does not follow its operation description

Harald Pehl (JIRA) issues at jboss.org
Tue Mar 14 08:30:00 EDT 2017


     [ https://issues.jboss.org/browse/WFCORE-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harald Pehl updated WFCORE-2530:
--------------------------------
    Steps to Reproduce: 
In domain mode set all ports of {{full-sockets}} to 80: 

{code}
<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>
{code}

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


> :read-boot-errors() operation does not follow its operation description
> -----------------------------------------------------------------------
>
>                 Key: WFCORE-2530
>                 URL: https://issues.jboss.org/browse/WFCORE-2530
>             Project: WildFly Core
>          Issue Type: Bug
>    Affects Versions: 3.0.0.Beta7
>            Reporter: Harald Pehl
>            Assignee: ehsavoie Hugonnet
>
> The reply properties of the {{:read-boot-errors()}} operation lists the attribute {{missing-transitive-dependency-problems}} which is defined as 
> {code}
> "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
>         }
>     }
> }
> {code}
> 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}}: 
> {code}
> ...
>     "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"
>         ]
>     }
> ...
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list