Sometimes wildfly start fails because of missing deployment

Gepardec / sy-poc

Switchyard Proof Of Concept (Example Project)

1 stars 2 forks source link

Sometimes wildfly start fails because of missing deployment #4

Open cchet opened 7 years ago

cchet commented 7 years ago

I have the issue that wildfly cannot be started again after ./sy-poc-build.sh --configure (needed for system properties to be set), because in the standalone.xml has a deployment defined, which is not available anymore on next start. I'm not quite sure why this is, will investigate it.

Maybe anyone got a hint why the deployment is not available anymore.

ErhardSiegl commented 7 years ago

The deployment files should be in the data directory within a hash-structure.