Skip to main content
avillanueva
avillanueva23-Emerald II
23-Emerald II
February 20, 2013
Question

Background MS out to lunch

  • February 20, 2013
  • 1 reply
  • 584 views
Anyone know what Method Context Concurrency stat is in Server Status page? For 9.1. Stat is red for my background MS and at 74. Does this mean too many connections to it? How does this occur? Result is workflows and publishing have stalled. What is odd is that CPU is low for that process, GC is low and memory appears in line. Looking for insight to this issue. Think a restart is in order for the short term.

Antonio Villanueva - Sr. Software Engineer - ISR Systems
UTC AEROSPACE SYSTEMS
100 Wooster Heights Road, Danbury, CT 06804
Tel: +1 203 797 5682
antonio.villanueva@utas.utc.com<">mailto:antonio.villanueva@utas.utc.com> www.utcaerospacesystems.com
CONFIDENTIALITY WARNING: This message may contain proprietary and/or privileged information of UTC Aerospace Systems and its affiliated companies. If you are not the intended recipient please 1) do not disclose, copy, distribute or use this message or its contents, 2) advise the sender by return e-mail, and 3) delete all copies (including all attachments) from your computer. Your cooperation is greatly appreciated.

1 reply

jessh12-Amethyst
12-Amethyst
February 21, 2013
A background method server doesn't have foreground connections.

A method context is the method server's term for a body of work. For
foreground requests, there's a method context for each RMI request, for
instance. The same concept applies to background work, e.g. queue tasks.

Trying to do 74 things at once but not managing to use much CPU is a bad
sign. I'm inclined to suspect a deadlock. I assume the server status
page isn't noting a deadlock, but that just means there's no simple
thread deadlock. This could well be a more complex deadlock -- for
instance, one where 'n' threads holding database connections are all
waiting for a lock that's held by another thread which is itself waiting
for a database connection.

The key here is to get and analyze thread dumps for the method server in
question. Unfortunately at R9.1 we don't yet add extra information
about database connection usage, etc, to JMX-based thread dump output --
as we do in more recent releases. Thus even with a thread dump, it may
be a bit tricky to find the culprit.

--
Jess Holle
Terms & ConditionsAccessibility statement