Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Deployments Caching Managed Domain

    Posted on

    Using Jboss 6 EAP, EWS Apache 2.2. Managed mode with one domain controller and four Jboss App Servers and two Apache webservers and one Barracuda Load Balancer.

    I created a new EAR for our Jboss EAP 6 servers that had small jsp changes. I used the management console to deploy the app. I disabled the app and did a replace to update the EAR then enabled the application.

    The deployment looked like it went successfully. Logged onto our load balancer to check to see if the changes were present and they weren't. I then logged onto each EAP server to verify if all these servers had the change and they didn't. I navigated to each of the servers domain/data/content folder to see if the EAR had the changes I expected and of course they did have the changes.

    I did several things such as restarting the jboss App Servers. Removing and Add the application back then assigning it to the server group. But nothing has worked.

    The last thing I did to fix this was to turn off all the EAP servers and delete all the tmp data and content folders on all app servers and controller. I also had to update the domain.xml on the controller so that it wasn't expecting a deployment. Then redeployed the app. This worked but I would not expect to have to do this at all.

    Any thoughts on why this might be happening?

    Thanks

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat