Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildfly10 fails to start when adding standalone.xml to configuration directory via configFile closure #145

Open
robjinman opened this issue Mar 7, 2016 · 1 comment

Comments

@robjinman
Copy link

I expect it's a problem with Cargo itself rather than this plugin. Manually copying the file to wildfly-10.0.0.Final/wildfly-10.0.0.Final/standalone/configuration/ works fine, however adding the following to the build script causes the task cargoStartLocal to hang indefinitely.

cargo {
  containerId = "wildfly10x"

  ...

  local {
    configFile {
      file = file("containerConfig/wildfly/standalone.xml")
      toDir = "configuration"
    }

The file is correctly copied to /tmp/cargo/conf/configuration/standalone.xml and none of the log files reports any errors. The app appears to deploy, but all connections are refused.

The last line in the log is:

INFO [org.jboss.as](Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 9460ms - Started 444 of 739 services (394 services are lazy, passive or on-demand)

@robjinman
Copy link
Author

I thought I'd try a different container, yet the problem persists with each one I've tried: TomEE, Wildfly 9, Wildfly 10, Glassfish 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant