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
__