??xml version="1.0" encoding="utf-8" standalone="yes"?>
后来(g)查plugin-cfg.xml文gQ发现有如下节点比较怪异Q?br />
<ServerCluster CloneSeparatorChange="false" LoadBalance="Round Robin" Name="RptWXCluster" PostBufferSize="64" PostSizeLimit="-1" RemoveSpecialHeaders="true" RetryInterval="60">
<Server CloneID="115gjg4rf" ConnectTimeout="0" ExtendedHandshake="false" LoadBalanceWeight="2" MaxConnections="-1" Name="appwx2_rptwx2" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="appwx2" Port="9085" Protocol="http"/>
<Transport Hostname="appwx2" Port="9448" Protocol="https">
<Property Name="keyring" Value="/IBM/W/IBM/WebSphere/AppServer/etc/plugin-key.kdb"/>
<Property Name="stashfile" Value="/IBM/W/IBM/WebSphere/AppServer/etc/plugin-key.sth"/>
</Transport>
</Server>
<Server CloneID="12kr342rp" ConnectTimeout="0" ExtendedHandshake="false" LoadBalanceWeight="2" MaxConnections="-1" Name="appwx1_rptwx1" ServerIOTimeout="0" WaitForContinue="false">
<Transport Hostname="appwx1" Port="9453" Protocol="https">
<Property Name="keyring" Value="/IBM/W/IBM/WebSphere/AppServer/etc/plugin-key.kdb"/>
<Property Name="stashfile" Value="/IBM/W/IBM/WebSphere/AppServer/etc/plugin-key.sth"/>
</Transport>
</Server>
<PrimaryServers>
<Server Name="appwx2_rptwx2"/>
<Server Name="appwx1_rptwx1"/>
</PrimaryServers>
</ServerCluster>
同ؓ(f)集中的两个节点成员rptwx2、rptwx1Q没有启用ssl的Transport rptwx2有,rptwx1却没有!Q!我赶紧回L查rptwx1的web container里http transport的配|,赫然发现rptwx1没有启用ssl的Transport 为:(x)9090Q刚好与admin console的没有启用ssl的Transport 重了(jin)Q?br />
由此q道解军_法ؓ(f)Q?br />
1、检查群集节Ҏ(gu)员的Transport Q是否与admin console的Transport Q?090Q未启用sslQ?043Q启用sslQ相互重复,如有冲突Q则需把节Ҏ(gu)员的Transport 改ؓ(f)其他90XX?br />
注意Q在修改配置后,需要更新插件和重启apacheQ重启serverQ方可生效:(x)
1、更?Web 服务器插仉|;
2、重启apacheQ?br />
3、重启修改httptransport的server实例?
]]>
先查log得知Q?br>Exception: WUPD0248E: Fix pack update failure: The processing of fix pack was51_fp1_hpux, component plugins.http failed. See the log file /IBM/WebSphere/AppServer/logs/update/20070709_093535_was51_fp1_hpux_plugins.http_install.log for processing details.
后查log得知Q?br>/IBM/WebSphere/AppServer//bin/mod_app_server_http.sl忙?无法dD更新Q?怪象叠出Q!Q?br>
H然Q灵光一闪,赶紧用ps -ef|grep httpd查看一下进E,发现apache虽然停止?jin),但是httpd instanceD留有,没有释放掉。赶紧大手大脚的把这些该ȝ挂死httpd instanceq程一把kill -9掉?br>
然后安装风水Q^淡无奇了(jin)?br>
lg所qͼ我的一点徏议是Q在q行W(xu)AS升打补丁之前,请严格按照要求,对照问题Q执行自(g)Q?br>1、应用服务器全部停掉?jin)吗Q也是WAS的instanceQؓ(f)javaq程Q?br>2、WAS的nodeagentq程停掉?jin)吗Q其为javaq程Q?br>3、WAS的dmgrq程停掉?jin)吗Q其为javaq程Q?br>4、IBM HttpServer停掉?jin)吗Q请用ps -ef|grep root|grep httpd认Q?br>5、在IBM HttpServer停掉以后Q请再确认有无挂ȝhttpdq程Q也是apache的httpd instanceQ子q程。请用ps -ef|grep httpd认?br>
1??可以单的使用ps -ef|grep root|grep java认有无q程存在?br>
刀不误砍柴工,执行以上五步(g)查法之后QW(xu)AS升打补丁的先决条g有?jin)保证?br>
目 数?br>OS 名称 Microsoft Windows 2000 Server
版本 5.0.2195 Service Pack 4 内部版本?2195
OS 刉商 Microsoft Corporation
pȝ刉商 Dell Computer Corporation
pȝ型号 PowerEdge 4600
pȝcd Z X86 ?PC
处理?nbsp;x86 Family 15 Model 2 Stepping 7 GenuineIntel ~2783 Mhz
处理?nbsp;x86 Family 15 Model 2 Stepping 7 GenuineIntel ~2783 Mhz
处理?nbsp;x86 Family 15 Model 2 Stepping 7 GenuineIntel ~2783 Mhz
处理?nbsp;x86 Family 15 Model 2 Stepping 7 GenuineIntel ~2783 Mhz
物理内存总量 3,866,096 KB
2、stopServer.log抛出异常Q无法创?SOAP q接器连接端?8882 ?br>************ Start Display Current Environment ************
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = d:\WebSphere\AppServer
user.install.root = null
Java Home = d:\WebSphere\AppServer\java\jre
ws.ext.dirs = d:\WebSphere\AppServer\java\lib;d:\WebSphere\AppServer\classes;d:\WebSphere\AppServer\lib;d:\WebSphere\AppServer\lib\ext;d:\WebSphere\AppServer\web\help;d:\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime
Classpath = d:\WebSphere\AppServer\properties;d:\WebSphere\AppServer\lib\bootstrap.jar;d:\WebSphere\AppServer\lib\j2ee.jar;d:\WebSphere\AppServer\lib\lmproxy.jar;d:\WebSphere\AppServer\lib\urlprotocols.jar
Java Library path = d:\WebSphere\AppServer\java\bin;.;C:\WINNT\system32;C:\WINNT;d:\WebSphere\AppServer\bin;d:\WebSphere\AppServer\java\bin;d:\WebSphere\AppServer\java\jre\bin;C:\sybase\ADO.NET\dll;C:\sybase\OLEDB;C:\sybase\ODBC;C:\sybase\OCS-12_5\lib3p;C:\sybase\OCS-12_5\dll;C:\sybase\OCS-12_5\bin;C:\sybase\SQLRemote\dll;C:\sybase\RPL-12_5\bin;C:\sybase\EFTS-12_5_2\verity\_nti40\filters;C:\sybase\EFTS-12_5_2\verity\_nti40\bin;C:\sybase\EFTS-12_5_2\bin;C:\sybase\JS-12_5\bin;C:\sybase\ASE-12_5\dll;C:\sybase\ASE-12_5\bin;c:\sybase\CFG-1_0\bin;c:\sybase\OCS-12_5\dll;c:\sybase\OCS-12_5\lib3p;c:\sybase\OCS-12_5\bin;c:\sybase\ASE-12_5\dll;c:\sybase\ASE-12_5\bin;C:\j2sdk1.4.2\bin;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;c:\sybase\OCS-12_0\dll;c:\sybase\OCS-12_0\bin;c:\sybase\ASEP;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;c:\sybase\SQLRemote\dll;C:\j2sdk1.4.2
Current trace specification = *=all=disabled
************* End Display Current Environment *************
[07-6-26 20:52:16:016 CST] 31134186 ManagerAdmin I TRAS0017I: 启动跟踪状态是 *=all=disabled?br>[07-6-26 20:52:16:047 CST] 31134186 AdminTool A ADMU3100I: 正在从服务器d配置Qserver1
[07-6-26 20:52:24:938 CST] 31134186 WsServerStop E ADMU3002E: 试处理服务?server1 时发生异?br>[07-6-26 20:52:24:938 CST] 31134186 WsServerStop E ADMU3007E: 异常 com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: 无法创徏 SOAP q接器连接端?8882 上的L
[07-6-26 20:52:24:938 CST] 31134186 WsServerStop A ADMU3007E: 异常 com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: 无法创徏 SOAP q接器连接端?8882 上的L
3、startServer.log抛出异常Q服务器已启动,但是初始化失败。服务器日志文g应该包含故障信息?br>************ Start Display Current Environment ************
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = d:\WebSphere\AppServer
user.install.root = null
Java Home = d:\WebSphere\AppServer\java\jre
ws.ext.dirs = d:\WebSphere\AppServer\java\lib;d:\WebSphere\AppServer\classes;d:\WebSphere\AppServer\lib;d:\WebSphere\AppServer\lib\ext;d:\WebSphere\AppServer\web\help;d:\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime
Classpath = d:\WebSphere\AppServer\properties;d:\WebSphere\AppServer\lib\bootstrap.jar;d:\WebSphere\AppServer\lib\j2ee.jar;d:\WebSphere\AppServer\lib\lmproxy.jar;d:\WebSphere\AppServer\lib\urlprotocols.jar
Java Library path = d:\WebSphere\AppServer\java\bin;.;C:\WINNT\system32;C:\WINNT;d:\WebSphere\AppServer\bin;d:\WebSphere\AppServer\java\bin;d:\WebSphere\AppServer\java\jre\bin;C:\sybase\ADO.NET\dll;C:\sybase\OLEDB;C:\sybase\ODBC;C:\sybase\OCS-12_5\lib3p;C:\sybase\OCS-12_5\dll;C:\sybase\OCS-12_5\bin;C:\sybase\SQLRemote\dll;C:\sybase\RPL-12_5\bin;C:\sybase\EFTS-12_5_2\verity\_nti40\filters;C:\sybase\EFTS-12_5_2\verity\_nti40\bin;C:\sybase\EFTS-12_5_2\bin;C:\sybase\JS-12_5\bin;C:\sybase\ASE-12_5\dll;C:\sybase\ASE-12_5\bin;c:\sybase\CFG-1_0\bin;c:\sybase\OCS-12_5\dll;c:\sybase\OCS-12_5\lib3p;c:\sybase\OCS-12_5\bin;c:\sybase\ASE-12_5\dll;c:\sybase\ASE-12_5\bin;C:\j2sdk1.4.2\bin;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;c:\sybase\OCS-12_0\dll;c:\sybase\OCS-12_0\bin;c:\sybase\ASEP;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;c:\sybase\SQLRemote\dll;C:\j2sdk1.4.2
Current trace specification = *=all=disabled
************* End Display Current Environment *************
[07-6-26 20:51:56:047 CST] 3113407c ManagerAdmin I TRAS0017I: 启动跟踪状态是 *=all=disabled?br>[07-6-26 20:51:56:062 CST] 3113407c AdminTool A ADMU3100I: 正在从服务器d配置Qserver1
[07-6-26 20:51:58:016 CST] 3113407c AdminTool A ADMU3200I: 服务器已启动。等待初始化状态?br>[07-6-26 20:52:01:219 CST] 3113407c AdminTool A ADMU3011E: 服务器已启动Q但是初始化p|。服务器日志文g应该包含故障信息?br>************ Start Display Current Environment ************
4、分?br>刚开始以为是SOAP_CONNECTOR_ADDRESS端口8878被占用,修改?jin)?f)8881?882后,仍然不能启动serverQ后回忆h障h员提赯内存?sh)的问题,q回L查jvm的配|server.xmlQinitialHeapSize="1536" maximumHeapSize="1536"Q立卛_位出原因为初始堆大小、最大堆大小讄q大所致。修改ؓ(f)initialHeapSize="1024" maximumHeapSize="1024"后,server立即能够实现正常启停?br>
5、后?br>“ADMC0016E: 无法创徏 SOAP q接器连接端?8882 上的L”在初始乍看之下,首先L?x)想到端口号是否被占用能否通过换用端口解决问题Q但是一改再改还是没有解决问题;q时候,p请用环境的人员回忆最q是否修改了(jin)WAS的配|,我也是如此。在修改端口号仍然不能解决问题后Q回惌v报障人员提到q内存(sh)的问题Q抓住这个突破口Q检查了(jin)jvm的堆讄Q果焉题就q刃而解?jin)?br>
6、tips
在windows32位操作系l环境下QW(xu)AS的堆讄不能过2048MQ我到qƈ解决?jin)两ơ;从上q案例看Q堆讄g也不能超q?536M?/p>