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 15.1
edited by David Avendasora
on 2010/11/30 06:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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"}}
105 +{{code title="Manually Launch wotaskd"}}
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
... ... @@ -131,7 +131,7 @@
131 131  
132 132  There are several techniques for dealing with deadlocks and application hangs.
133 133  
134 -If you are using a [[profiler>>Programming__WebObjects-Web_Applications-Development-Profiling_WO_Apps]] or debugger, you can generally pause execution and see where exactly your application is dying.
134 +If you are using a [[profiler>>WO:Programming__WebObjects-Web_Applications-Development-Profiling_WO_Apps]] or debugger, you can generally pause execution and see where exactly your application is dying.
135 135  
136 136  If you are using JDK 1.4, you can send your application a QUIT signal and it will dump all active threads. On OS X, find the pid of your application, then execute a 'kill QUIT yourAppPID'. The thread stack traces will dump out to the log files. If you do not see any output in your logs, see the //Where's my stderr?// above for possible reasons.
137 137