On 5-Apr-08, at 5:18 PM, Yury Peskin wrote:
Did I mention I'm running the app on 10.3.9?
Hey, this sounds familiar! I was doing exactly this on solaris 2
days ago! :-)
When I encounter situations like this, I (sometimes only temporarily)
modify the SpawnOfWotaskd.sh script.
It's located inside wotaskd.woa and on MacOSX that would typically be
somewhere like:
/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/
Resources/SpawnOfWotaskd.sh
Note, on Windows SpawnOfWotaskd.exe in the same folder is used.
When you ask JavaMonitor.woa to launch an application, it passes a
message to wotaskd.woa and the above script is what actually launches
the WOF application.
Anyway, the default version of that script redirects all the startup
messages to /dev/null and it's usually those messages which you need
to debug situations like this.
At the minimum, change /dev/null to /tmp/SpawnOfWotaskd.log and try
to launch the application again. For me, there hasn't been a need to
restart wotaskd.woa for the modified script to be used. I usually
change the script to append to the log file and record all the given
arguments so that I can see exactly what's being passed in.
Something like this is a place to start:
#!/bin/sh
LOG=/tmp/SpawnOfWotaskd.log
echo "****" >>$LOG
date >> $LOG
echo $@ >> $LOG
$@ 1>>$LOG 2>&1 &
Good luck and post back any error messages from the
SpawnOfWotaskd.log which you can't figure out!
Mark
__
Mark Ritchie
Cocoa and WebObjects Developer
Diamond Lake Consulting Inc.
Toronto, Ontario, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
