4 Replies Latest reply on Jul 28, 2017 4:39 AM by jiseb

    Conflict between applications' instances  in WildFly

    jiseb

      Hello,

      We have a problem with WildFly in domain mode. WildFly contains multiple application instances (up to 4) for different regions (same war files, just a different configuration). Our app is a common Spring web application which connects to Oracle db. When we deploy all applications with different Runtime Name at once, everything is OK. But when we change something in a configuration for a concrete instance and restart this server then other instances crash. We have to undeploy all apps and re-deploy them again to work correctly. In the future we plan to switch to standalone mode (instances will be separated), but is there any advice for the existing solution? When other servers crash, they report errors indicating some xml files conflicting each other. We guess that their context path could collide, but Runtime Name is different...

      Here is an example of log after the instance crash:

       

      DEBUG [default task-20] 25.7.2017 14:03:38 TemplateEngine:process(line 1051) - [THYMELEAF][default task-20] STARTING PROCESS OF TEMPLATE “welcome” WITH LOCALE en

      ERROR [default task-20] 25.7.2017 14:03:38 TemplateEngine:process(line 1085) - [THYMELEAF][default task-20] Exception processing template “welcome”: Error resolving template “welcome”, template might not exist or might not be accessible by any of the configured Template Resolvers

      DEBUG [default task-20] 25.7.2017 14:03:38 DispatcherServlet:render(line 1261) - Error rendering view [org.thymeleaf.spring4.view.ThymeleafView@733bbe98] in DispatcherServlet with name ‘web’

      org.thymeleaf.exceptions.TemplateInputException: Error resolving template “welcome”, template might not exist or might not be accessible by any of the configured Template Resolvers

          at org.thymeleaf.TemplateRepository.getTemplate(TemplateRepository.java:246)

          at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1104)

          at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1060)

          at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1011)

          at org.thymeleaf.spring4.view.ThymeleafView.renderFragment(ThymeleafView.java:335)

          at org.thymeleaf.spring4.view.ThymeleafView.render(ThymeleafView.java:190)

       

      Versions we are using: 

      WildFly 10.1.0.Final

      Spring 4.3.2.RELEASE

       

      We will be happy for any idea that will help us to solve this. Thank you in advance,

       

      Jiri

        • 1. Re: Conflict between applications' instances  in WildFly
          jaikiran

          Can you add details about what tool you use to deploy these apps and what command you use? Also how do you update that configuration which trigger this error?

          • 2. Re: Conflict between applications' instances  in WildFly
            jiseb

            We are using web management console to deploy apps. Changing of configuration was just an example - we change JNDI in domain.xml and restrt the server. But the same crash is caused by restarting server without any configuration change. So we believe it is not caused by the change of configuration but by the restart of the server.

            • 3. Re: Conflict between applications' instances  in WildFly
              jaikiran

              Can you attach us the domain.xml file that's persisted when the applications are deployed?

              • 4. Re: Conflict between applications' instances  in WildFly
                jiseb

                domain.xlm attached

                 

                Just a liitle bit more explanation about applications deployed in this WildFly instance:

                1) application called "core" - not a web appliaction, no spring - we have no issues with this appliaction - restart of one instance has no influence on other instances

                2) application called "webapp1" - web application, spring is used - restart of one instance of "webapp1" causes crash of all other instances of "webapp1" (no influence to instances of "core" or "webapp2")

                2) application called "webapp2" - another web application, spring is used - restart of one instance of "webapp2" causes crash of all other instances of "webapp2" (no influence to instances of "core" or "webapp1")