This should only happen if you add WSRL ScheduledTermination (not
ImmediateTermination) to your resources. In this case, we have one timer
for each resource, since each may have a separate termination time. I'm
open to optimizing the implementation, but don't have any ideas for how to
do this and still get the correct termination behavior. Perhaps the first
question you should ask is: is it necessary to have *scheduled* termination
on this particular resource type?
Dan
"Srinivasan Packirisamy \(spackiri\)" <[EMAIL PROTECTED]> wrote on
05/30/2007 07:59:11 PM:
> Hi,
> When a resource is created with WS-RL capabilities, a timer
> thread created for each resource. So, if we create 1000s resources
> with WS-RL capabilities, the TimerThread count just keeps increasing
> and eventually causes issues in the WebServer. Can this be optimized?
>
> ~Srini
>
