APAR status
Closed as program error.
Error description
addnode.shh command works fine when invoked locally on the
application node but when we invoke it using ourself it does all
the intended work but it does not exit .. the rshell is not
coming back and giving the shell prompt ... tested remote node
command ... it works locally and works as expected using r shell
command and the exit prompt comes back ... only when invoke by
rshell has a problem ... like to automate administration .. user
needs to be able to add the node using rshell command and needs
assistance in making it work
bypassing the problem by adding it by hand ... trying to get it
to work with remote shell ..
The problem is clearly understood now. What was happening is
something like:
1) client runs "rsh someHost $WAS_HOME/bin/startServer.sh
server1"
2) On server side, stdin for startServer.sh is created and
connected
to the rsh client.
3) WSLauncher is started by startServer.sh and, since it
inherits
file descriptors from it's parent (startServer.sh), it also is
connected (via stdin) to the rsh client.
4) WSLauncher starts server1 which inherits file descriptors
from
WSLauncher so server1 (via stdin) also has open connections to
rsh
client.
5) WSLauncher detects that server1 has initialized so it exits.
6) startServer.sh, which was waiting for WSLauncher, resumes
and
exits.
7) However, server1, still has open connections to rsh client
so rsh
client thinks it still needs to wait.
Fix will be in the native code to close stdin before launching
JVM to
run server1.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 5.0 users of *
* remote shell ( rsh ) to execute WebSphere *
* scripts. *
****************************************************************
* PROBLEM DESCRIPTION: Certain scripts within WebSphere hangs *
* when using rsh. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When certain scripts are executed remotely through rsh,
rsh will hang. This occurs when the script in question
leaves a running process on the system when it exists.
Examples of such scripts are addNode.sh, startServer.sh,
and so on.
Problem conclusion
The hang was caused by an inadvertant inheritance of the
'stdin' file descriptor from rsh to the spawned
process. Since the descriptor remained in use, the rsh
call would not exit even though the script it called had
completed its task.
Temporary fix
Fix is available on
pq99999.
Comments
APAR information |
APAR number |
PQ76804 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-07-25 |
Closed date |
2003-09-18 |
Last modified date |
2003-09-18 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
|