Version 2

    Chinese Version:



               How to create/configure/start/stop JBoss AS 7.2.0 runtime server with Eclipse IDE 4.3(kepler)+jbosstools 4.1 - chinse version


    We described how to install JBoss Tools in Eclipse IDE(eclipse-jee-kepler)安装jbosstools(4.1.0.Beta2)的两种方法. Now, I will show you how to use its "Application Server" view.



    JBoss EAP 6.1 is based on JBoss AS 7.2.0 Final, just like Red Hat Enterprise Linux  is based on Cent OS. Currently, there is ONLY "JBoss EAP 6.1" in JBoss Tools, NO "JBoss AS 7.2.0 Final" Server. We can use ”JBoss EAP 6.1“ to manage "JBoss AS 7.2.0 Final" Server directly, which is recommended by JBoss too.

    Create "JBoss EAP 6.1"

    Entry: click the blue link in the red box:




    Select Server type:



    Set "JBoss EAP 6.1 Runtime Server":



    Set Sever Behavior:







    In above dialog, After push the  “Finish” button, there will be "JBoss EAP 6.1 Runtime Server" in the "Servers" view. Let's double click it, and we will see bellow configuration:





    If we change the "timeout" attribute from 450 to 460, and save it, we will suffer bellow error tip:

    The server cannot be saved for the following reaons:
        [Overview] Your server must have a valid startup poller selected.

    because no option in “Startip Poller” is selected.

    Currently, we do not change any thing.



    Note: In jbosstools-4.1.0.Beta1, “JBoss 7 Manager Service” is selected by default, but this option does NOT exist in  jbosstools-4.1.0.Beta2 any longer.






    Now, let's start this Server:



    We will see an error:




    This error is about memory setting.

    I searched by google many hours, and changed many configuration files, including eclipnse.ini and jboss/standalone.bat, None of them works!


    If we run standalone.bat directly, JBoss Server can be started, so the problem is on Eclipse.

    Let's review the configuration of  “JBoss EAP 6.1 Runtime Server”.




    Start Configuration:



    We can see that, bellow memory setting is much higher than common PC:



    Now, let's change “-Xms1303m -Xmx1303m -XX:MaxPermSize=256m” to “-Xms256m -Xmx512m -XX:MaxPermSize=256m” and restart “JBoss EAP 6.1 Runtime Server”.

    It is started successfully!





    Start timeout configuration

    Although JBoss AS is started,the “Progress” view tell us: it is always in starting states:



    About 5 minutes later,  “JBoss EAP 6.1 Runtime Server” is stoped automatically!




    Now, let's review “JBoss EAP 6.1 Runtime Server”, especially timeouts part:



    Now let's set “Startup Poller” to “Web Port”.

    Problem is resolved!


    (NOTE: I had tried to set timeout to a big value. The result is that eclipse will not close JBoss AS, but the progress is always “starting...”.)