[jboss-jira] [JBoss JIRA] (WFLY-5092) Can't start server in --admin-only with EAP 6.4 configuration

[Ladislav Thon (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105682#comment-13105682 ] 

Ladislav Thon edited comment on WFLY-5092 at 9/18/15 10:08 AM:
---------------------------------------------------------------

-Because comments to this issue contain pre-migrate steps, I'm adding post-migrate steps that are needed in standalone:-

{noformat}
/extension=org.jboss.as.web:remove
/extension=org.jboss.as.messaging:remove
/extension=org.jboss.as.jacorb:remove
{noformat}

-This is because the {{:migrate}} operations do not remove the extension (even though they remove the subsystem). And they can't in domain, per http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004287.html (if they could in standalone, I'm not sure).-

The above is no longer true. WFLY-5306 has been resolved in WildFly 10.0.0.CR1, so the extensions are now removed automatically during {{:migrate}} in standalone.


was (Author: lthon):
Because comments to this issue contain pre-migrate steps, I'm adding post-migrate steps that are needed in standalone:

{noformat}
/extension=org.jboss.as.web:remove
/extension=org.jboss.as.messaging:remove
/extension=org.jboss.as.jacorb:remove
{noformat}

This is because the {{:migrate}} operations do not remove the extension (even though they remove the subsystem). And they can't in domain, per http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004287.html (if they could in standalone, I'm not sure).

> Can't start server in --admin-only with EAP 6.4 configuration
> -------------------------------------------------------------
>
>                 Key: WFLY-5092
>                 URL: https://issues.jboss.org/browse/WFLY-5092
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Ladislav Thon
>            Assignee: Stuart Douglas
>            Priority: Blocker
>             Fix For: 10.0.0.Beta2
>
>
> When starting WildFly 10.0.0.Beta1 in {{--admin-only}} mode to perform {{:migrate}} operations on old subsystems, using an unmodified {{standalone-full-ha.xml}} configuration file from EAP 6.4.0, I'm getting errors.
> Based on http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004306.html, I'm expecting that I don't have to perform any changes to the EAP 6.4 configuration file, yet in order to successfully boot the new server with the old configuration file, I have to perform the following set of changes:
> - remove the {{cmp}}, {{jaxr}} and {{threads}} extensions and subsystems (this seems to be already covered by WFCORE-875)
> - copy the entire configuration of the {{ejb3}} subsystem (version 3.0) from a new {{standalone-full-ha.xml}} to the old one, because I'm not able to fix the old subsystem (version 1.5) from the error message \[1\]
> - add the {{io}} extension and subsystem from a new {{standalone-full-ha.xml}} to the old one, because {{remoting}} needs it to boot \[2\]
> \[1\] {code}16:31:35,167 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: "WFLYEJB0451: Attribute 'default-clustered-sfsb-cache' is not supported on current version servers; it is only allowed if its value matches 'default-sfsb-cache'"{code}
> \[2\] {code}16:34:35,376 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=remoting' are not available:
>     org.wildfly.io.worker.default
> {code}
> In http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004303.html, I also mentioned {{datasources}}, but that was a false alarm -- that was from normal server boot, not {{--admin-only}}, and hence invalid.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)