Skip to Content
Last modified by David Avendasora on 2010/11/30 06:59
From version 6.1
edited by lexlimo
on 2008/10/07 18:59
Change comment: There is no comment for this version
To version 8.1
edited by Pascal Robert
on 2010/09/12 23:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Web Applications-Deployment-Common Pitfalls and Troubleshooting
1 +Deployment-Common Pitfalls and Troubleshooting
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.lexlimo
1 +XWiki.probert
Content
... ... @@ -27,7 +27,7 @@
27 27  
28 28  == Where's my stderr? ==
29 29  
30 -Wotaskd launches new WOA instances using a script called SpawnOfWotaskd.sh that is located in /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/SpawnOfWotaskd.sh on OS X. For some reason, this script was written to throw away stderr. This means that if you ever want to get a thread stack dump, you're out of luck. Fortunately this is an easy fix. If you edit SpawnOfWotaskd.sh, the stock version looks like:
30 +Wotaskd launches new WOA instances using a script called SpawnOfWotaskd.sh that is located in /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/SpawnOfWotaskd.sh on OS X. For some reason, this script was written to throw away stdout and redirrect stderr to stdout. This means that if you ever want to get a thread stack dump, you're out of luck. Fortunately this is an easy fix. If you edit SpawnOfWotaskd.sh, the stock version looks like:
31 31  
32 32  {{code}}
33 33  
... ... @@ -100,7 +100,8 @@
100 100  
101 101  {{code}}
102 102  
103 -sudo -u appserver /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/javawoservice.sh -appPath /System/ Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd
103 +sudo -u appserver /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/javawoservice.sh \
104 +-appPath /System/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd
104 104  
105 105  {{/code}}
106 106