We're updating the issue view to help you get more done. 

Using more advanced technique to test wildfly availability

Description

See: https://github.com/codehaus-cargo/cargo/pull/106

Wildfly starts management interface too early: when server is not yet fully booted management interface is already reachable in terms of tcp connectivity. The idea is to ping wildfly via CLI API to determine whether it is fully booted or not:

1 2 3 4 5 6 7 8 9 10 ~$ java -jar jboss-modules.jar -mp modules org.jboss.as.cli --file=connect.cli INFO [org.jboss.modules] JBoss Modules version 1.5.2.Final INFO [org.xnio] XNIO version 3.4.0.Final INFO [org.xnio.nio] XNIO NIO Implementation Version 3.4.0.Final INFO [org.jboss.remoting] JBoss Remoting version 4.0.21.Final ERROR [org.jboss.as.cli.CommandContext] Timeout waiting for the system to boot. Timeout waiting for the system to boot. ~$ echo $? 1 ~$

Status

Assignee

Unassigned

Reporter

S. Ali Tokmen

Components

Fix versions

Priority

Major