2 Replies Latest reply on Feb 4, 2013 3:57 PM by chandrup

    Server failing when changing JBoss 7.1.0 to JBoss 7.1.1




      Recently I migrated one application from JBoss 3 to JBoss 7, I used JBoss 7.1.0. When I tried the same just changing to JBoss 7.1.1 I am not getting any errors and even deployment is successful but the server start is failing.


      How to check if anything wrong, do I need to change or configure something?




        • 1. Re: Server failing when changing JBoss 7.1.0 to JBoss 7.1.1
          Wolf-Dieter Fink Master

          Could you share more details?

          What application you migrate, does it work with 7.1.0?

          How do you start the server? If the start fails I suppose you see errors or warnings in the server.log.

          • 2. Re: Server failing when changing JBoss 7.1.0 to JBoss 7.1.1

            I am migrating a Java application which uses liferay portal framework, struts 1.2, hibernate 3, EJB 2.1. Initially we had some Jboss issues which I resolved. Basically my doubt is if I use JBoss 7.1.1 as standalone or with single instance inside Eclipse it works perfectly. But when I add as a new server which already working fine with JBoss 7.1.0 it is not starting and I don't really find any error logs. I doubt if I am missing some configuration changes to be done from Server window.


            Please refer to the screen shot.

            Jboss start error.png

            Steps followed:

            1.Added new server, named it as JBoss 7.1.1 Runtime, configured to point physical path

            2.Modified configuration file standalone-full.xml under JBoss 7.1.1, included necessary modules.

            3.Modified build path inside each of the EJB project to use JBoss 7.1.1 libraries

            4.Clean built the project and started the server(right click and start) after making sure deployments having the .dodeploy marker file


            There were no errors during build or deployment


            Note: When I switch to JBoss 7.1.0 back it works fine and starts successfully both the server and application as well.