JBoss EAP application deployment by deployment scanner and stadalone.xml persistence

Solution Unverified - Updated -

Issue

  • JBoss EAP's standalone.xml are sometimes persisted when a new application is deployed by the deployment scanner at the start-up, but it is not always. What conditions trigger standalone.xml persistence?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.x
    • 6.4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In