• Type: Bug
• Resolution: Not A Defect
• Priority: Major
• Component/s: antexec-plugin, post-completed-build-result-plugin
• Labels:

  • build
  • job
• Environment:

  Windows 7, Tomcat 6, IBM WAS 6.1,Jenkins 1.532.2

1. server1_00000013_14.03.18_12.14.01_0.txt

   35 kB

   2014-03-20 17:15

2. server1_00000027_14.03.18_12.16.47_0.txt

   5 kB

   2014-03-20 17:15

3. server1_00000027_14.03.18_12.16.47_1.txt

   7 kB

   2014-03-20 17:15

4. server1_00000027_14.03.18_12.16.47_2.txt

   7 kB

   2014-03-20 17:15

5. 

   jenkins build fails to keep server alive.png

   451 kB

   2014-03-20 16:38

6. 

   same outputs but server turn-off.png

   390 kB

   2014-03-20 16:38

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

Rex Wang created issue - 2014-03-20 16:38

Rex Wang made changes - 2014-03-20 17:15

Attachment		New: server1_00000013_14.03.18_12.14.01_0.txt [ 25580 ]
Attachment		New: server1_00000027_14.03.18_12.16.47_0.txt [ 25581 ]
Attachment		New: server1_00000027_14.03.18_12.16.47_1.txt [ 25582 ]
Attachment		New: server1_00000027_14.03.18_12.16.47_2.txt [ 25583 ]
Description	Original: 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.	New: 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.

Milos Svasek made changes - 2016-04-18 18:21

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Milos Svasek made changes - 2016-04-18 18:21

Assignee

New: Milos Svasek [ svasek ]

R. Tyler Croy made changes - 2016-07-25 23:56

Workflow

Original: JNJira [ 154357 ]

New: JNJira + In-Review [ 194884 ]