I just got the same thing. Here's the explanation:
Verbose logging is on (level 3 I think). I'm debugging a database update -- it's removing CR & LF from the end of PDF files stored in the db (I'll post the reason separately, as I think it's of general use).
Anyway, I was writing the pdf data out as results, which was okay for debugging. But I forgot when I ran my test on ALL the db records. Though the database is fully updated, the logging is lagging. And if I tail it, I'll see it is way behind.
So witangod is just filling up my disk at 99% CPU utilization.
On Tuesday, February 22, 2005, at 03:21 PM, Customer Support wrote:
You can install the openlink iodbc sdk. This is a double clickable installer.
Witango Support
On 23/02/2005, at 10:16 AM, Roland Dumas wrote:
Hmm.. I think I see. The installation instructions I used to get witango up
and running initially specified using myodbc installer. I go and check and
it's still at 3.5.1.
Then I search around and see that it's at 3.52.2, but it's a pile of files
with instructions to get some developer tools to create installers. Are
there instructions for installing 3.52.2 somewhere or an installer? This is
a bit on the arcane side for me.
I'm kind of torn now because something about iodbc is causing witango to
crash on one server. The test of jdbc on a test machine worked, except that
the first time I did a transaction, it crashed witango. (it worked a dozen
times after, but when your first process crashes the server, you do wonder.)
So, is there an installer or English installation instructions for 3.52.2??
On 2/22/05 2:51 PM, "Customer Support" <[EMAIL PROTECTED]> wrote:
Yes that is out of date. There has been releases for 3.51.2, 3.52.1 and iodbc is currently sitting at 3.52.2
3.52.2 was released a few weeks ago, 3.52.1 was released in sept '04,
3.51.2 in Feb '04 so the version you are running is probably over 12-18
months old.
Witango Support
On 23/02/2005, at 6:10 AM, Roland Dumas wrote:
On 2/18/05 7:04 PM, "Customer Support" <[EMAIL PROTECTED]>
wrote:
Use your db admin tool to see what connections are active on the db.
If one is active shut it down. if this does not fix it try stopping
your db and see if the thread goes into a wait state.
Also download and install the latest iodbc driver manager.
The driver is 3.5.1 That's out of date?
Witango Support
On 19/02/2005, at 1:33 PM, Roland Dumas wrote:
On 2/18/05 4:28 PM, "Customer Support" <[EMAIL PROTECTED]>
wrote:
Load up the Apple Development tools. In it you will find an
application called Thread Viewer. Open it from the command line
with
a
sudo command. Once it is open attach it to the witangod process and
see what the threads are doing.
Hmmm. So with thread viewer, I can see all these threads, one of
which
is
continuously active, never letting go. Always green, an iodbc related
thread. Wish I knew what this stuff means.
You can also install the latest CHUD if you are an Apple connect
member
which has an application called Shark which will profile a process
and
show you if a thread is in an infinite loop.
These two applications are the only way to see what the server process is doing on OS X.
Witango Support
_____________________________________________________________________ ___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
----------------------------------------- Roland Dumas Roberts Information Services 310 W. Bellevue Avenue San Mateo CA 94402 650-347-1373 415-412-9300 (cell) [EMAIL PROTECTED] SMS: http://new.servqual.com/html/sms.tml
______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
