Hey Joe-

I would look into the SDK docs. There may be a way you can manually do this
via JMX. If you aren't familiar with JMX, check out my article in DevNet:

http://www.macromedia.com/devnet/java/articles/jmx.html

Then refer to the SDK documentations at:

http://livedocs.macromedia.com/jrun/4/JRun_SDK_Guide/contents.htm

As a worst-case scenario, you could probably set up an even listener that
would auto-restart the JRun server whenever you had a db lockup.

Hope this helps.

-Drew Falkman
Team Macromedia ..  JRUN
  -----Original Message-----
  From: Joe Eugene [mailto:[EMAIL PROTECTED]
  Sent: Monday, October 18, 2004 9:52 AM
  To: JRun-Talk
  Subject: Re: JRun Threads

  Anybody got any ideas on this one?

  Joe

  ----- Original Message -----
  From: "Joe Eugene" <[EMAIL PROTECTED]>
  To: "JRun-Talk" <[EMAIL PROTECTED]>
  Sent: Monday, October 18, 2004 10:07 AM
  Subject: JRun Threads

  > Is there a way to force kill JRun Threads without restarting CFMX/Jrun
  > Service?
  >
  > Occasionally, we get locked threads due a rare db interface programming
  > environment(RedBack) locking up.
  >
  > 10/18 09:57:41 metrics (busy/total/listen/idle/delay/handled/dropped),
  > 22/30/1/7/0/14/0 Sessions:522
  >
  > The 22 busy threads above wont get released unless i restart the
service,
  > they got locked when
  > the DB interface failed to respond. Normally we only need 10-12 threads
  > total to process around 600 sessions.
  >
  > Appreciate any help.
  >
  > Joe Eugene
  >
  >
  >
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to