Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22276

was 6.1 server stops itself after Jenkins deploys a java ee application through a ws_ant script

XMLWordPrintable

      A Jenkins instance is deployed through Tomcat 6 in Win7. A Jenkins job is configured by invoking a ws_ant(ibm extension of ant) script to build and deploy a Java ee application to a WAS 6.1 server instance. The ws_ant script runs with same success either at windows terminal or at Jenkins. However, server turns itself into stop state within one minute after it was started up by Jenkins. In contrast, the was server stays on after the script is executed at terminal. I examined the server log. There are exceptions, but the server exception logs are the same for Jenkins and terminal case.

        1. jenkins build fails to keep server alive.png
          jenkins build fails to keep server alive.png
          451 kB
        2. same outputs but server turn-off.png
          same outputs but server turn-off.png
          390 kB
        3. server1_00000013_14.03.18_12.14.01_0.txt
          35 kB
        4. server1_00000027_14.03.18_12.16.47_0.txt
          5 kB
        5. server1_00000027_14.03.18_12.16.47_1.txt
          7 kB
        6. server1_00000027_14.03.18_12.16.47_2.txt
          7 kB

          [JENKINS-22276] was 6.1 server stops itself after Jenkins deploys a java ee application through a ws_ant script

          Milos Svasek added a comment -

          Hi, this is not a bug of AntExec plugin IMHO.
          It seems that WsStartApp return code is "0" even if there is non-zero return code in child java process.

          Milos Svasek added a comment - Hi, this is not a bug of AntExec plugin IMHO. It seems that WsStartApp return code is "0" even if there is non-zero return code in child java process.

            svasek Milos Svasek
            rex_wang Rex Wang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: