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

Managing
worker
thread
allocation
v
“Configuring
WebSEAL
worker
threads”
on
page
41
v
“Allocating
worker
threads
for
junctions
(junction
fairness)”
on
page
42
v
“Configuration
on
AIX”
Configuring
WebSEAL
worker
threads
The
number
of
configured
worker
threads
specifies
the
number
of
concurrent
incoming
requests
that
can
be
serviced
by
a
server.
Other
connections
that
arrive
when
all
worker
threads
are
busy
will
be
buffered
until
a
worker
thread
is
available.
You
can
set
the
number
of
threads
available
to
service
incoming
connections
to
WebSEAL.
Configuring
the
number
of
worker
threads
should
be
done
carefully
due
to
possible
performance
impacts.
This
configuration
parameter
does
not
impose
an
upper
boundary
on
the
number
of
simultaneous
connections.
This
parameter
simply
specifies
the
number
of
threads
made
available
to
service
a
potentially
unlimited
work
queue.
Choosing
the
optimal
number
of
worker
threads
depends
on
understanding
the
quantity
and
type
of
traffic
on
your
network.
In
all
cases,
you
must
only
enter
a
value
that
is
less
than
the
worker
threads
limit
imposed
by
the
operating
system.
By
increasing
the
number
of
threads,
you
are,
in
general,
decreasing
the
average
time
it
takes
to
finish
the
requests.
However,
increasing
the
number
of
threads
impacts
other
factors
that
could
have
an
adverse
effect
on
server
performance.
WebSEAL
maintains
a
single,
generic
worker
list
and
worker
threads
pool
for
handling
requests
from
clients
using
TCP
or
SSL.
This
enhanced
mechanism
enables
WebSEAL
to
consume
fewer
system
resources
while
handling
significantly
greater
load.
You
can
configure
the
worker
thread
pool
size
by
setting
the
worker-threads
parameter
in
the
[server]
stanza
portion
of
the
WebSEAL
configuration
file.
[server]
worker-threads
=
50
Note:
The
value
of
this
parameter
must
remain
within
the
worker
threads
limits
set
by
the
operating
system.
Configuration
on
AIX
On
AIX
systems
only,
when
the
WebSEAL
worker
threads
limit
in
the
[server]
stanza
of
the
WebSEAL
configuration
file
is
increased
beyond
the
default
of
50
to
a
value
greater
than
800
on
an
AIX
system,
WebSEAL
can
fail
and
produce
a
core
dump.
Workaround:
Increase
the
AIX
process
size
limits
to
unlimited
as
follows:
1.
Locate
the
limits
file
in
the
/etc/security
directory.
2.
Search
for
the
word
default
and
find
parameters
for
cpu,
rss,
and
data.
Default
settings
are
as
follows:
data
=
262144
rss
=
65536
Chapter
2.
WebSEAL
server
configuration
41