Solution, Cause, Websphere – IBM 51 User Manual
Page 84: Application, Server, Linux, Remains, Paused, When, Stop
Solution
From
the
Microsoft
Visual
C++
6.0
Support
Web
site
available
at
follow
the
instructions
to
download
the
Vcredist.exe
installer.
The
installer
will
place
the
msvcp60.dll
file
at
the
correct
location
on
your
computer.
WebSphere
Application
Server
on
Linux
remains
paused
when
you
try
to
stop
the
JMS
pub
sub
broker
The
last
line
in
the
log
is:
1b2ddb28
JMSEmbeddedPr
A
MSGS0054I:
Stopping
the
Broker
When
you
run
ps
-ef
|
grep
java
it
returns
only
one
process:
stopServer
.
Cause
A
problem
occurred
in
the
Linux
libstdc++
library.
Solution
Stop
the
server
process
to
stop
the
broker.
1.
From
download
the
libstdc++
RPM.
2.
Rename
the
existing
libstdc++-3-libc6.2.2-2.10.0.so
3.
Extract
the
library
from
the
rpm
using
rpm2cpio
and
replace
the
existing
library.
For
detailed
procedures,
go
to:
Do
not
follow
the
instructions
in
the
WebSphere
Application
Server
5.0.2
release
notes
that
tell
you
to
upgrade
to
the
latest
level
of
libstdc
.
That
instruction
is
incorrect.
On
Windows,
the
remote
connection
to
the
database
hangs
when
the
database
server
is
on
a
multiprocessor
machine
When
the
database
server
is
on
a
multiprocessor
machine,
the
remote
connection
to
the
database
might
hang,
in
which
case
the
database
server
logs
the
following
error
in
the
db2diag.log
file:
DIA3208E
Error
encountered
in
TCP/IP
protocol
support.
TCP/IP
function
"accept".
Socket
was
"920".
Errno
was
"10061".
Cause
Not
enough
connection
managers
are
allocated
from
the
database
server.
Solution
1.
Update
the
database
registry,
DB2TCPCONNMGRS
,
to
enable
the
database
server
to
provide
additional
connection
managers.
2.
Considering
that
DB2TCPCONNMGRS
takes
values
between
1
and
8,
use
the
following
formula
to
determine
the
value
of
a
given
computer:
Calculate
the
square
root
of
the
number
of
processors
and
round
up
to
a
maximum
value
of
8.
3.
Run
the
following
command
to
update
the
registry:
db2set
DB2TCPCONNMGRS=
4.
After
changing
the
registry
value,
restart
DB2
as
follows:
db2stop
force
db2start
72
Tivoli
Intelligent
Orchestrator
Problem
Determination
and
Troubleshooting
Guide