Customer is benchmarking their application with J2SE1.4.1 fcs. They're
app is hanging when their object LoadIS(524) is trying to access the
java.util.Hashtable.

The offending thread is stuck waiting on the Hashtable monitor.
"Configuration Instructions Executor - executing: LoadIS(524)" prio=5
tid=0x10578b940 nid=0x28 waiting for monitor entry
...
at java.util.Hashtable.get(Hashtable.java:328)
- waiting to lock <fffffffef783f5c8> (a java.util.Hashtable)

This thread in turn has locked a customer monitor that is needed by many other
application threads thus causing the customer application to hang:
- waiting to lock <fffffffef4099448> (a
com.xacct.xacctusage.gatherer.GathererRuntimeEnvironment)

In the Java thread dumps it's not known who has locked the Hashtable monitor. The customer is synchronizing on an object before accessing the Hashtable and
their code snippet tracing the execution to java.util.Hashtable.get is available
upon request.

The entire instance of this thread dump "ThreadDump" and the pstack
output is in the attachments. There are more threads dumps in the
Gatherer_stdout.log file.