Set LOGGINGLEVEL=3 in the witango.ini file. This will log the debug like information to the witango log. Stop and start the server with the following terminal command:
sudo SystemStarter restart WITANGO5
It will ask for an admin password. Once the command has finished you will see some output like this:
Welcome to Macintosh.
Stopping Witango server
Waiting for WITANGO5
Starting Witango Application Server
[ 4106] 2003-12-05 13:49:58 START INFO Starting Witango Application Server Process
Startup complete.
Hangup
This indicates that the server has restarted.
Now run the taf again and have a look in the witango.log file. You should be able to see what the error is that is causing the server to return an incorrect response to the web plugin. What is the error message?
Witango Support
On 05/12/2003, at 1:44 PM, MJPinckard wrote:
Actually when this occurs, I get no debugging, even though it is turned on... so no debugging is available to peruse.
witangoevents.log shows nothing after the last time the server started up...
any other ideas on where to look?
Maggie
Jon van der Raadt wrote:
Do you have debug turned on -- sometimes that will help determine the problem. You can also look in the witangoevents.log It will record a crash if that is happening...
On Dec 4, 2003, at 7:26 PM, MJPinckard wrote:
I'm getting a Client/Plug-in error message and hope someone knows what's going on. Here's the message.
Client/Plug-in Error
The response received from the application server is invalid.
It always happens at the same location in my application process, but doesn't seem to be tied to any specific code (e.g. if I remove the search action causing the error, the next search action fails, if I duplicate a earlier successful search action right before the failing action then it fails on the duplicated action).
It seems as if it is something like a maxaction limitation but I've got maxaction set to 0, which if I understand correctly is unlimited (I tested setting maxaction to 4000, way more than I need, but that didn't change anything). The failure is happening quickly which rules out time out problems, and it is not deep in branch actions which rules that out.
If I look on the console, I see the SQL query being parsed, then a line including system information and the License number.
Mac OX 10.3 running Witango 5.0.x (current version) under Apache. I don't see a response from the database.
Anyone know what this is and how to fix or can steer me towards more diagnostics?
Thanks,
Maggie
* * * * * * * * * * * * * * * * * * * * * Margaret Pinckard * [EMAIL PROTECTED] * Principal Research Associate * End-use Forecasting Group * E.O. Lawrence Berkeley National Laboratory
_____________________________________________________________________ __ _
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
-- * * * * * * * * * * * * * * * * * * * * * Margaret Pinckard * [EMAIL PROTECTED] * Principal Research Associate * End-use Forecasting Group * E.O. Lawrence Berkeley National Laboratory
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
