Dear List, Every so often we get 1 or more db2jd processes which appear to go off the deep end and chew up cpu and disk. We're running V7.1 on Solaris 5.8. The processes are listenerchilds started by the jdbc server or listener. Has anyone else seen this. Can anyone imagine how a listener process can bring a box to its knees? Any and all input would be appreciated. Victor McDonnell ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
