WebSphere Classic Error resolution and summarization __web

WebSphere is IBM's software platform. It includes the entire middleware infrastructure needed for Web applications and Cross-platform, cross product solutions, such as servers, services, and tools. In the process of using WebSphere, you will encounter such a problem, this is a common mistake to do a resolution and summary.

One, was application failed to stop normal

Sometimes a normal stop is an application that cannot be stopped because the connection to the process in the system is not released. This time directly in the system to kill the application process.

The SCM01 stop is as follows

First log in 10.8.2.201 and execute the following command

Ps–ef|grep SCMWEB01

Find the application process, there should be two normal, web space, a process for node, a process for the server, as follows

Kill the node process first.

Kill-9 7427

Note://7427 is the PID number of the process

And then kill the server process.

Kill-9 20287//20287 is also the PID number

That's when the application stops.

The startup method is as follows

Execute first

/opt/ibm/websphere/scmweb01/bin/startnode.sh

And then execute

/opt/ibm/websphere/scmweb01/bin/startserver.sh SCM01

When the process's PID number appears, the Hong Kong server is leased, and the server is set to open, which can be accessed by accessing a single server.

Two, is node not synchronized solution

Errors that occur when nodes are not synchronized:

1, the launch of the application of the time is particularly slow, the newspaper "may have started successfully, but did not start at the scheduled time to complete the details please refer to the log."
2, "Enterprise Application" under the status of the application seems to be incorrect, the application launched in the WebSphere enterprise application here is still a "red X" state.
3, the system under the management of the node State is not synchronized, the synchronization node still shows that the synchronization.
4, the deployment of new applications after the launch, will be reported
[12-4-11 20:08:07:127 CST] 0000002b defaulttokenp I hmgr0149e: The connection that attempted to open to the core group Defaultcoregroup was rejected. The name of the send process is called

Fqztestapcell01\fqztestapcellmanager01\dmgr and the IP address is 172.18.251.23. Global security in the local process is Disabled. Global security is Enabled in the send process. Received tags to???? +? Qe?? Beginning. Exception is <null>.
[12-4-11 20:20:40:736 CST] 00000017 adminhelper   a   admn1009i: Try to start the Rews_message_parse application.
[12-4-11 20:20:40:740 CST] 00000017 applicationmg w   wsvr0215w: Failed to launch application Rews_message_parse. The application has not been installed.
[12-4-11 20:42:21:326 CST] 00000016 adminhelper   a   admn1009i: Try to start the Rews_message_parse application.
[12-4-11 20:42:21:330 CST] 00000016 applicationmg w   wsvr0215w: Failed to launch application Rews_message_parse. The application has not been installed.
&NBSP
But during the actual deployment, the logs did not complain and the console prompts for a successful deployment. This was console node shows that the sync state is not working, and the problem is resolved as follows:
1, switch to the bin directory, execute the appropriate command, and then stop the server, node, dmgr (in strict order)
/opt/ibm/websphere/ appserver/profiles/appsrv02/bin/stopserver.sh  server1  
/opt/ibm/websphere/appserver/ profiles/appsrv02/bin/stopnode.sh

/opt/ibm/websphere/appserver/bin/stopmanager.sh

2. Delete temporary files under Wstemp, temp, and Config/temp folders
/opt/ibm/websphere/appserver/profiles/dmgr01/temp, wstemp, tranlog directory content deletion.
The contents of the/opt/ibm/websphere/appserver/profiles/dmgr01/config/temp directory are deleted.

3, synchronization node:
# #同步节点信息
Switch to "/opt/ibm/websphere/appserver/profiles/appsrv02/bin/":
Executive: syncnode.sh kmtest 8879-username Wasadmin-password 000000
where "kmtest" is the hostname that was deployed in the second item of host name

4, sequentially start Dmgr, node, server (in strict order) #依次停止 Server, node, dmgr

/opt/ibm/websphere/appserver/bin/startmanager.sh

/opt/ibm/websphere/appserver/profiles/appsrv02/bin/startnode.sh

/opt/ibm/websphere/appserver/profiles/appsrv02/bin/startserver.sh Server1

Third, the node is not activated

Error tip: Server cannot be started because the node agent for Server Server1 on node server1node01 are not active.

When using startnode.sh nodes under/opt/ibm/websphere/appserver/bin

Admu0111e:program exiting with Error:java.io.FileNotFoundException:

/opt/ibm/websphere/appserver/profiles/dmgr01/config/cells/server1cell01/nodes/server1cellmanager01/servers/ Nodeagent/server.xml

(No such file or directory)

This is due to the fact that the true files for the node start and stop are not in this directory because of the IS management console

can go into this/opt/ibm/websphere/appserver/profiles/appsrv01/bin directory

Start node

Server1:/opt/ibm/websphere/appserver/profiles/appsrv01/bin #./startnode.sh

Admu0116i:tool information is being logged in file

/opt/ibm/websphere/appserver/profiles/appsrv01/logs/nodeagent/startserver.log

Admu0128i:starting tool with the APPSRV01 profile

Admu3100i:reading Configuration for Server:nodeagent

Admu3200i:server launched. Waiting for initialization status.

Admu3000i:server nodeagent open for e-business; Process ID is 5894

Restart Server

Server1:/opt/ibm/websphere/appserver/profiles/appsrv01/bin #./startserver.sh Server1

Admu0116i:tool information is being logged in file

/opt/ibm/websphere/appserver/profiles/appsrv01/logs/server1/startserver.log

Admu0128i:starting tool with the APPSRV01 profile

Admu3100i:reading Configuration for Server:server1

Admu3200i:server launched. Waiting for initialization status.

Admu3000i:server Server1 open for e-business; Process ID is 6121

The node is then added to the was admin console

Server1:/opt/ibm/websphere/appserver/profiles/appsrv01/bin #/addnode.sh 192.168.0.8 8879-username wasadmin- Password 12345

Admu0116i:tool information is being logged in file

/opt/ibm/websphere/appserver/profiles/appsrv01/logs/addnode.log

Admu0128i:starting tool with the APPSRV01 profile

Cwpki0308i:adding signer alias "Datapower" to local KeyStore

"Clientdefaulttruststore" with the following SHA digest:

A9:ba:a4:b5:bc:26:2f:5d:2a:80:93:ca:ba:f4:31:05:f2:54:14:17

Admu0001i:begin Federation of Node SERVER1NODE01 with deployment Manager at

192.168.0.8:8879.

Admu0009i:successfully connected to Deployment Manager Server:

192.168.0.8:8879

Admu0033e:the node server1node01 already has been to the cell.

Admu0027e:an error occurred during Federation admu0033e:the node

SERVER1NODE01 already has been added to the cell. Rolling back to

Original configuration.

Admu0211i:error details May is seen in the file:

/opt/ibm/websphere/appserver/profiles/appsrv01/logs/addnode.log

Admu0111e:program exiting with Error:

Com.ibm.ws.management.tools.DoNotDoAddNodeException:ADMU0033E:The

Node SERVER1NODE01 already has been added to the cell.

Admu1211i:to obtain a full trace of the failure, use the-trace option.

Admu0211i:error details May is seen in the file:

/opt/ibm/websphere/appserver/profiles/appsrv01/logs/addnode.log

Then look at the console and see that the node is normal and running.