IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

3.
Change
the
settings
for
the
data
and
rss
parameters
to
unlimited
using
the
–1
value.
The
–1
setting
specifies
unlimited
or
is
bounded
by
the
capabilities
of
the
operating
system
and
the
CPU.
data
=
-1
rss
=
-1
4.
Reboot
the
system
for
these
changes
to
take
effect.
Allocating
worker
threads
for
junctions
(junction
fairness)
You
can
configure
the
allocation
of
WebSEAL
worker
threads
used
to
process
requests
across
multiple
junctions
on
a
global
or
per-junction
basis.
The
configuration
mechanism
maintains
a
″fair″
distribution
of
worker
threads
across
all
junctions
and
prevents
depletion
of
the
worker
thread
pool
by
any
one
junction.
Background
WebSEAL
draws
from
its
pool
of
worker
threads
to
process
multiple
requests.
The
number
of
worker
threads
available
to
WebSEAL
is
specified
by
the
worker-threads
parameter
in
the
WebSEAL
configuration
file.
You
can
adjust
the
worker-threads
value
to
best
serve
your
particular
WebSEAL
implementation.
When
no
worker
threads
are
available
to
handle
incoming
requests,
users
experience
a
WebSEAL
server
that
is
not
responding.
Worker
threads
are
used
to
handle
incoming
requests
to
applications
residing
on
multiple
junctioned
back-end
servers.
However,
the
worker
thread
pool
can
be
quickly
drained
if
a
particular
back-end
application
is
unusually
slow
when
responding
to
and
processing
a
high
volume
of
requests.
A
depletion
of
the
worker
thread
pool
by
this
one
application
renders
WebSEAL
incapable
of
responding
to
requests
for
services
on
the
remaining
junctioned
application
servers.
You
can
configure
global
or
per-junction
limits
on
the
number
of
worker
threads
used
to
service
applications
on
multiple
junctions.
These
limits
allow
″fairness″
to
prevail
for
all
junctions
and
prevents
any
one
application
from
claiming
more
than
its
share
of
worker
threads.
Note:
For
information
on
worker
thread
resource
usage
limits,
and
for
instructions
on
detecting
worker
thread
starvation,
see
the
IBM
Tivoli
Access
Manager
for
e-business
Performance
Tuning
Guide
Global
allocation
of
worker
threads
for
junctions
Two
parameters
located
in
the
[junction]
stanza
of
the
WebSEAL
configuration
file
control
the
global
allocation
of
worker
threads
across
all
junctions
for
a
particular
WebSEAL
server.
The
values
used
for
these
parameters
are
expressed
as
percentages
within
the
range
of
0
to
100.
v
worker-thread-soft-limit
This
parameter
is
set
to
send
a
warning
before
the
″hard″
limit
is
reached.
When
the
worker-thread-soft-limit
is
exceeded,
warning
messages
are
sent
(every
30
seconds)
to
the
WebSEAL
error
log
file.
For
example,
when
worker-threads
=
50,
a
setting
of
60
(%)
causes
warning
messages
to
be
issued
when
the
junction
consumes
more
than
30
worker
threads.
All
requests
above
30
worker
threads
are
still
processed,
until
the
″hard″
limit
is
reached.
The
default
value
is
90
percent.
v
worker-thread-hard-limit
42
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide