APAR status |
Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)
| Error description
Environment
.
Solaris
WebSphere 3.5.1
Admin database Oracle 8.1.6i
.
The Sysadmin Guide suggests that when you select "Stop" on "an
administrative server node, this action stops the administrative
server running on the node", but in the reported case the admin
server stays alive although all other Java processes on the node
terminate.
It is possible to reconnect to the admin server by running
./adminclient.sh again, but the "+" icon to expand the tree is
not available, and the message "InstanceTree W Failed to get the
root instances" is received. Killing the server processes and
restarting returns normal behaviour. The tracefile reports
nothing unusual, just the AppServer start and stop messages.
Problem re-creation:
In a single node environment, with a servlet AppServer and an
EJB AppServer:Problem re-creation:In a single node environment, with a servlet AppServer and an
- Issue ./startupServer.sh &, which creates processes 1 and 2.
- Issue ./adminclient.sh &, which creates process 3.
- Use the console to start the servlet AppServer, creates
process 4.
- Use the console to start the EJB AppServer, creates process
5.
- Right click on the node and select "Stop" (or use the Stop
button on the console), and processes 3, 4, and 5 die;
processes 1 and 2 persist. EJB AppServer: - Issue ./startupServer.sh &, which creates processes 1 and 2., - Issue ./adminclient.sh &, which creates process 3.- Use the console to start the servlet AppServer, createsprocess 4.- Use the console to start the EJB AppServer, creates process5.- Right click on the node and select "Stop" (or use the Stopbutton on the console), and processes 3, 4, and 5 die;processes 1 and 2 persist. Local fix
If the app server is stopped before stopping the node, then all
the Java processes disappear as they should. Problem summaryProblem conclusionTemporary fixComments
Problem re-creation:
In a single node environment, with a servlet AppServer and an
EJB AppServer:Problem re-creation:In a single node environment, with a servlet AppServer and an
- Issue ./startupServer.sh &, which creates processes 1 and 2.
- Issue ./adminclient.sh &, which creates process 3.
- Use the console to start the servlet AppServer, creates
process 4.
- Use the console to start the EJB AppServer, creates process
5.
- Right click on the node and select "Stop" (or use the Stop
button on the console), and processes 3, 4, and 5 die;
processes 1 and 2 persist.
Developer note:EJB AppServer: - Issue ./startupServer.sh &, which creates processes 1 and 2., - Issue ./adminclient.sh &, which creates process 3.- Use the console to start the servlet AppServer, createsprocess 4.- Use the console to start the EJB AppServer, creates process5.- Right click on the node and select "Stop" (or use the Stopbutton on the console), and processes 3, 4, and 5 die;processes 1 and 2 persist.
I tried to reproduce it in advanced Version 3.5.0 and 12/06/2000
build advanced version. I failed both times.
I need customer to do a ps -ef before they start the node.
I need customer to do a ps -ef after they stop the node.
I also need customer to turn on traceString=com.ibm.ejs.sm.*=all
run admin server. I also need customer to send me the trace
file output.
Final note: Customer failed to provide info after 2 months
to help reproduce.. closing apar. Developer note:I tried to reproduce it in advanced Version 3.5.0 and 12/06/2000build advanced version. I failed both times.I need customer to do a ps -ef before they start the node.I need customer to do a ps -ef after they stop the node.I also need customer to turn on traceString=com.ibm.ejs.sm.*=allrun admin server. I also need customer to send me the tracefile output.Final note: Customer failed to provide info after 2 monthsto help reproduce.. closing apar.
APAR information | APAR number | PQ43223 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED RET | PE | NoPE | HIPER | NoHIPER | Submitted date | 2000-11-08 | Closed date | 2001-03-06 | Last modified date | 2001-03-06 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|