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 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 crashes in OS X and it seems to be a threading >issue. When most crashes occur, at least two threads are active and >I haven't been able to identify any faulty action or taf. > >Also, I believe that when a crash occurs, under certain >circumstances, all log data may not be written to disk. You might >miss a little at the end. I also think newer app servers than 054 >are better about this. But I don't know for sure. I'm about to put >059 in production and will post to the list if it is clearly less >crash-prone than previous versions. > >Out of curiosity, what database and connection method are you using? > >- Jeff > > > >>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 particular TAF or particular type of >>activity) >> >>On Wednesday, June 11, 2003, at 07:27 PM, ezra wrote: >> >>>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:01 -0400 >>> >>>>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 Wednesday, June 11, 2003, at 01:19 AM, ezra wrote: >>>> >>>>>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_timedwait_signal_trap >>>>> >>>>>other threads like above with same kind of error. >>>>> >>>>>thanks, >>>>>Ezra >-- > >Jeff Bohmer >VisionLink, Inc. >_________________________________ >303.402.0170 >www.visionlink.org >_________________________________ >People. Tools. Change. Community. > _______________________________________________________ _________________ >TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > _____________________________________ Sent via TamilCafe.com WebMail System Get yours at http://www.TamilCafe.com Questions? mailto:[EMAIL PROTECTED] ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
