We also use ND 4.1.3 on NT 4.0 SP3 accessing DB2 on MVS.
We have also observed the same behavior, and it occurs whenever DB2 gets
recycled and the connections to DB2 are been broken.
We know this because DB2 gets recycled once a week on the weekend
and this problem always occurs on Monday morning.
Our answer is to basically recycle the DS whenever DB2 gets recycled.
It's not much of an answer, but whoever monitors DB2 during offhours
could also monitor ND.
Johnny Wong
Yes -- and no.
We have DB2 database with ND 4.1.3 on NT 4.0 SP 3 and our DB2 DSWorkers
behave
similarly.
Our best *guess* is that is has to do with the worker getting caught in an
infinite loop of unsuccessfully connecting to the database. That's not a
very
well-informed guess, but we've noticed that sometimes when this is occurring
other applications connecting to the same database (e.g., Access through
ODBC)
will come back with a connection failure; we speculate that this may be from
the
DB being overloaded by zillions of connect requests from ND.
As for resolution, our "answer" is to kill the runaway DSWorker, which
solves
the problem. However, if you don't have the luxury of monitoring the CPU 24
hours a day, I have no real suggestions.
Our deployment platforms are Solaris; I don't know whether they have the
same
problem there, and if they do, how they cope with it. I'm sure I could find
out
for you, though; you don't make mention of the OS under which the ND server
is
running.
The only other thing to note is that we *are* running 4.1.3, and it doesn't
solve the problem.
-- David.
(Embedded
image moved [EMAIL PROTECTED]
to file: 04/29/99 07:15 PM
pic03249.pcx)
To: [EMAIL PROTECTED]
cc: (bcc: David P Caldwell/GL/KSC/KeyCorp)
Subject: [ND] nd_DSWorker_41 using excess CPU on NT - NetD Version 4.1.24
We have noticed that sometimes the nd_DSWorker_41 starts to use up a large
amount of CPU and the application server
is unable to process any pages. We are going against a DB2 database on AIX
and
have the NetD Application configured so
the RDBMS Service had 3 worker process with a maximum number of clients per
worker set to 1. We were told by
NetDynamics that we should upgrade to 4.1.3 which would correct this
problem.
We have done so and still see the problem
occurring. Has anyone else seen this problem and were you able to get it
resolved?
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
<< File: pic03249.pcx >>
The opinions expressed here are not necessarily those my employer and
_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
