Hi Jeff,
Thanks for the info, we are running Oracle and using OCI to connect to
it.
thanks,
ezra
-- Original Message --
From: Jeffrey Bohmer <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Thu, 12 Jun 2003 11:15:39 -0600
>
>Someone has mentioned on
Someone has mentioned on the list that turning caching on can help
avoid crashes. Make sure you have LOGGINGLEVEL=2 to see all the
actions executed. In addition to looking for a similar taf or action
for each crash, note the number of active threads when a crash occurs.
We sometimes get crash
I was talking editor, not server. My apologies. Looks like something
you might want to submit as a bug report to Witango as well.
I am guessing that you're trying to do something that is bringing the
server to its knees. Is there any consistency in terms of when this
crash occurs? (e.g., a p
Hi Dale,
Its the server which crashes, not the editor, did you have the same
issue with your server as well or your editor?
thanks,
ezra
-- Original Message --
From: Dale Graham <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Wed, 11 Jun 2003 07:40:
I have had this problem (twice), and solved it by
1] killing my editor preferences
2] removing the dev studio receipt from /Library/Receipts
3] reinstalling the editor
Something got corrupted somewhere; I didn't bother tracking it down,
since the "start over" method works just fine.
On Wednesda
Witango on osx seems to be crashing a lot with the following crash
entry and wondering if anyone else seen the following before:
OSX: 10.2.4
WITANGO: 5.0.1.054
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x01483fff
Thread 0:
#0 0x90042668 in semaphore_tim
