I've seen this behavior previously on OS X. Once we setup 062 and iODBC driver manager 3.0.6 (a level 3 manager, OS X comes with 2.1.6) the problem seems to have gone away. Now, if the app server is using all the CPU, it's always because there's a thread running.
When you see this, there are better ways of checking for activity than the Witango log. You can use @SERVERSTATUS to see the active query threads (1=no other threads active). You can also stop the app server and check witangoevents.log for a "waiting for active threads ..." message.
- Jeff
Just started getting strange results. top shows--
19:57:10 up 20 days, 10:02, 1 user, load average: 3.87, 4.16, 2.45 66 processes: 64 sleeping, 2 running, 0 zombie, 0 stopped CPU states: 100.0% user 0.0% system 0.0% nice 0.0% iowait 0.0% idle Mem: 251272k av, 208820k used, 42452k free, 0k shrd, 40812k buff 138168k actv, 18572k in_d, 3284k in_c Swap: 522104k av, 64048k used, 458056k free 107852k cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 1953 witango 15 0 28484 14M 2316 S 99.8 5.8 45:41 0 witangod 7616 root 15 0 1188 1188 864 R 0.1 0.4 0:00 0 top
Looking back 45 minutes in Witango.log, I see nothing except my once-a-minute cron job, which shows that it ends successfully.
This is a big problem as we move into production!!!!!
Anyone have any clues?
Bill Conlon
To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306
office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com
Jeff Bohmer VisionLink, Inc. _________________________________ 303.402.0170 www.visionlink.org _________________________________ People. Tools. Change. Community. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
