JSF 1.0 on WAS 5.1

Question

hi All,
We are using JSF 1.0 based application in WAS 5.1. During performance testing it is observed that the application is using all available threads in WAS thread pool. E.g. for 300 users all 125 threads are being used which is affecting the response times.
We haven't done any thread specific implementation. Is there anything in JSF or WAS that keeps the thread in wait stage?
regards
Abhay

Answer 1

I've put a breakpoint at the only line in the setter and not instantiated the ArrayList backing the patientsSelected list. The debugger shows the backing Arraylist as null and the parameter as ArraysListArrayList<E>. As we've noted, allowing the assignment produces the exception.
This is the first initiating code. Upon a location selection, the form is submitted and the patientsSelected setter is called like all others. Same thing occurs with any other form submittal (same form), such as a "Select All" command button.
Thanks for your very helpful insights.
<h:panelGroup id="navPG1">
  <h:outputText id="navOT" value="Choose Patient Location" />
  <br />
  <h:selectOneMenu id="locationSelection"
    value="${SelectBean.locationSelected}"
    valueChangeListener="#{SelectBean.onLocationChange}"
    onchange="submit()">
    <f:selectItems id="locationSelects"
    value="#{SelectBean.locationSelects}" />
    </h:selectOneMenu>
</h:panelGroup>