Skip to Content
Last modified by David Avendasora on 2010/11/30 06:59
From version 13.1
edited by David Avendasora
on 2010/11/30 06:57
Change comment: There is no comment for this version
To version 14.1
edited by ldemers
on 2009/10/21 21:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Troubleshooting Deployment
1 +Web Applications-Deployment-Common Pitfalls and Troubleshooting
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.ldemers
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  A current app I'm working freezes up for about a minute when calling editingContext.saveChanges. The following message is added to the system output:
4 4  
5 -{{code value="none"}}
5 +{{code}}
6 6  
7 7  <WorkerThread3> <WOWorkerThread id=3 socket=Socket[addr=/xxx.xxx.xxx.xxx,port=51634,localport=51563]>
8 8  Exception while sending response: java.net.SocketException: Broken pipe
... ... @@ -23,12 +23,8 @@
23 23  * Use the WOLongReponsePage to handle long running requests.
24 24  * Increase the Connect Timeout and Receive Timeout values in JavaMonitor so that the woadaptor will wait long enough for your application to provide the response.
25 25  
26 -{{note}}
26 +**Note:** If this message happens in other contexts (i.e. not when a request takes a long time to process) it might just mean that the user hit stop in their browser or clicked another link.
27 27  
28 -If this message happens in other contexts (i.e. not when a request takes a long time to process) it might just mean that the user hit stop in their browser or clicked another link.
29 -
30 -{{/note}}
31 -
32 32  == Where's my stderr? ==
33 33  
34 34  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:
... ... @@ -102,7 +102,7 @@
102 102  
103 103  Running this following command in a terminal window will tell you exactly why wotaskd is not launching...
104 104  
105 -{{code title="Command to Manually Maunch wotaskd"}}
101 +{{code}}
106 106  
107 107  sudo -u appserver /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/javawoservice.sh \
108 108  -appPath /System/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd