![]() |
|
|
|
|
Change By:
|
Rex Wang
(20/Mar/14 5:15 PM)
|
|
Attachment:
|
server1_00000013_14.03.18_12.14.01_0.txt
|
|
Attachment:
|
server1_00000027_14.03.18_12.16.47_0.txt
|
|
Attachment:
|
server1_00000027_14.03.18_12.16.47_1.txt
|
|
Attachment:
|
server1_00000027_14.03.18_12.16.47_2.txt
|
|
Description:
|
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.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
