1） An error occurred while deleting the server. ADMG0011E: An unexpected exception occurred com.ibm.websphere.management.exception.AdminException: Exception in removeTargetFromCUs().. Try to delete the server again. If the error persists, see the problem determination on the WebSphere Application Server Support Web page on http://www.ibm.com/software/webservers/appserv/was/support/."
原因及解決辦法：后經查，是因為原cell里有相關的應用已經被刪除，但是原來cell時有配置沒有清除。清除dmgr cell下的廢棄的文檔。刪除dmgr/config/cellName/bla目錄下和cus目錄下的所有內容。（注：ibmasyncrsp/isclite/WebSphereWSDM不能刪除，否則會造成dmgr管理控制台無法使用）
2) 無法停止server，用命令stopServer.sh同樣如此。
報錯信息：
[4/2/13 10:21:15:612 CST] 00000000 WsServerStop E ADMU3007E: Exception com.ibm.websphere.management.exception.ConnectorException: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host vm-vmw233-t.travelsky-op.com at port 8885.
[4/2/13 10:21:15:614 CST] 00000000 WsServerStop A ADMU3007E: Exception com.ibm.websphere.management.exception.ConnectorException: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host vm-vmw233-t.travelsky-op.com at port 8885.
at com.ibm.ws.management.connector.ConnectorHelper.createConnector(ConnectorHelper.java:579)
at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:367)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:269)
at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:107)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:330)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:108)
Caused by: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host vm-vmw233-t.travelsky-op.com at port 8885.
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:529)
at com.ibm.ws.management.connector.ConnectorHelper.tryProtocol(ConnectorHelper.java:616)
at com.ibm.ws.management.connector.ConnectorHelper.createConnector(ConnectorHelper.java:548)
... 24 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:45)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:515)
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:358)
... 26 more
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host vm-vmw233-t.travelsky-op.com at port 8885.
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:377)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:197)
... 31 more
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host vm-vmw233-t.travelsky-op.com at port 8885.
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:1308)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.access$300(SOAPConnectorClient.java:123)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(SOAPConnectorClient.java:341)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:334)
... 32 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
at java.net.Socket.connect(Socket.java:530)
at java.net.Socket.connect(Socket.java:480)
at java.net.Socket.<init>(Socket.java:377)
at java.net.Socket.<init>(Socket.java:220)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:1288)
... 36 more
[4/2/13 10:21:15:628 CST] 00000000 AdminTool A ADMU0509I: The server "aesServer1" cannot be reached. It appears to be stopped.
原因及解決辦法：本人遇到問題是節點未與dmgr同步導致，停止node，對節點進行同步，然后再對server操作，問題解決。
請參考：
http://stackoverflow.com/questions/9774899/websphere-application-server-exception-admc0016e-the-system-cannot-create-a-soa
3) was7 syncNode時報錯：ADMU0005E: Error synchronizing repositories {0}
報錯信息：
[4/2/13 15:30:22:246 CST] 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[4/2/13 15:30:22:423 CST] 00000000 AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile
[4/2/13 15:30:22:472 CST] 00000000 ModelMgr I WSVR0801I: Initializing all server configuration models
[4/2/13 15:30:25:198 CST] 00000000 SSLConfig W CWPKI0041W: One or more key stores are using the default password.
[4/2/13 15:30:25:208 CST] 00000000 SSLConfigMana I CWPKI0027I: Disabling default hostname verification for HTTPS URL connections.
[4/2/13 15:30:26:628 CST] 00000000 AdminTool E ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU0005E: Error synchronizing repositories {0}
at com.ibm.ws.management.tools.NodeSyncUtility.runTool(NodeSyncUtility.java:161)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:269)
at com.ibm.ws.management.tools.NodeSyncUtility.main(NodeSyncUtility.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:330)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:108)
[4/2/13 15:30:26:645 CST] 00000000 AdminTool A ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU0005E: Error synchronizing repositories {0}
at com.ibm.ws.management.tools.NodeSyncUtility.runTool(NodeSyncUtility.java:161)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:269)
at com.ibm.ws.management.tools.NodeSyncUtility.main(NodeSyncUtility.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:330)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:108)
[4/2/13 15:30:26:649 CST] 00000000 AdminTool A ADMU1211I: To obtain a full trace of the failure, use the -trace option.
[4/2/13 15:30:26:650 CST] 00000000 AdminTool A ADMU0211I: Error details may be seen in the file: /opt/app/WebSphere/profiles/AppSrv01/logs/syncNode.log
原因及解決辦法：ADMU0005E: 對存儲庫 {0} 進行同步時出錯
| Explanation |
配置同步期間發生錯誤。如果在 addNode 期間出現此錯誤，配置將回滾為基本配置。如果在 syncNode 期間發生此錯誤，那么節點和單元存儲庫可能彼此不同步。 |
| Action |
請查看日志文件以獲取其他的問題確定信息。 |
主要是該節點 不是dmgr受管節點，導致無法同步。
4) WAS ND節點同步問題
處理思路(更多請參考http://blog.csdn.net/jaminwm/article/details/7261103)：
1. 禁用全局安全性（即去掉訪問控制台的密碼），重啟dmgr；
2. 停止所有節點；
3. 進到節點的bin目錄下，做手動強制同步；
4. 啟用全局安全性並重啟dmgr和所有節點；
5. 登陸管理控制台做全部再同步；
6. 如果上一步做完還是不能同步，停止所有節點，到命令行下做手動強制同步；
7. 重啟dmgr，啟動節點。
處理過程：
1、編輯/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/app1Cell01/security.xml
將第三行useLocalSecurityServer="true" useDomainQualifiedUserNames="false" enabled="true"中的enabled="true"改為enabled="false"
或登陸管理控制台，導航到安全性，安全管理、應用程序和基礎結構，將啟用管理安全性前的勾去掉
2、然后重啟dmgr服務，並停止所有節點服務；
3、停止所有節點服務 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/stopNode.sh
4、做手動強制同步 ./syncNode.sh dmgr_hostname 8879
5、啟用全局安全性，並重啟dmgr和所有節點
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/startNode.sh
6、登陸管理控制台，依次點擊系統管理，節點，選擇所有節點，點擊全部再同步；
7、停止所有節點，到命令行下做手動全部再同步（建議每個節點都做）
./syncNode.sh dmgr_hostname 8879 -username wasadmin -password *****
8、重啟dmgr和所有節點
5) WAS ND集群的Node Agent 不活動的問題
問題症狀：登陸DM控制台，
系統管理->Node Agent,看到兩個nodeagent，其中app server上的nodeagent狀態為“已停止”。
進入"系統管理->Node",選擇app server節點，點擊同步，提示：
無法在節點 Default02Node 上執行同步操作，因為它的 Node Agent 不是活動的。
進入“服務器->集群",在集群配置頁點擊”集群成員，詳細信息”，選擇app server對應的成員，點擊啟動，提示：因為節點 Default02Node 上服務器 node_02 的 Node Agent 不活動，所以不能啟動服務器。
解決思路及辦法：
1、首先查看這個node當時是addNode成功的，這一點可以通過addNode.log來看。
2、如果從命令行也啟動不了node agent的話，你可以在startNode之前先運行一下：syncNode.sh or syncNode.bat命令，將node跟dmgr同步一下，在運行./startNode.sh或startNode.bat
3、如果命令行啟動節點成功，無報錯信息，但是控制台顯示Node Agent不活動的話，可以查看dmgr的日志和node的日志，查看是否防火牆的原因，禁用防火牆，然后重新啟動node查看。
Ø 應用部署
1) 應用打包：
1、從CC上更新最新的代碼，在RAD中打包。
Ear包名：aeswmfet
Application.XML配置文件如下：
<?xml version="1.0" encoding="UTF-8"?>
<application id="Application_ID" version="5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>aeswmfet</display-name>
<module id="Module_1365560011251">
<web>
<web-uri>AESW.war</web-uri>
<context-root>aeswmfet</context-root>
</web>
</module>
<module id="Module_1365560011350">
<web>
<web-uri>AESS.war</web-uri>
<context-root>aessmfet</context-root>
</web>
</module>
</application>
2) 啟動報錯：java.lang.NoClassDefFoundError: com.travelsky.b2bplatform.persist.cabin.dao.CabinDAO (initialization failure)
報錯信息如下：
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cabinManager' defined in class path resource [b2bplatform-applicationContext-config.xml]: Cannot resolve reference to bean 'cabinDAO' while setting bean property 'cabinDAO'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cabinDAO' defined in class path resource [b2bplatform-applicationContext-config.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: com.travelsky.b2bplatform.persist.cabin.dao.CabinDAO (initialization failure)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1325)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1086)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
... 74 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cabinDAO' defined in class path resource [b2bplatform-applicationContext-config.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: com.travelsky.b2bplatform.persist.cabin.dao.CabinDAO (initialization failure)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:965)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:911)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
... 84 more
Caused by: java.lang.NoClassDefFoundError: com.travelsky.b2bplatform.persist.cabin.dao.CabinDAO (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:140)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:45)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
at java.lang.reflect.Constructor.newInstance(Constructor.java:515)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:74)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:958)
... 92 more
原因及解決辦法：
原因是B2B平台中DAO文件需要加載aeswmfet_config.properties文件，雖然在ear包含有，但是啟動的時候仍然無法找到（這個可能是JVM類加載的問題），需要對共享庫重新進行配置。
測試共享庫如下所示（供參考）：
/opt/shared/WebSphere/lib/shared/aes_mfb2b/aessmfet_config.properties
/opt/shared/WebSphere/lib/shared/aes_mfb2b/aeswmfet_config.properties
/opt/shared/WebSphere/lib/shared/aes_mfb2b/b2b_service.jar
/opt/shared/WebSphere/lib/shared/aes_mfb2b/b2b_interface.jar
/opt/shared/WebSphere/lib/shared/aes_mfb2b/aes
/opt/shared/WebSphere/lib/shared/aes_mfb2b/b2bplatform
/opt/shared/WebSphere/lib/shared/aes_mfb2b/
3) 啟動報錯： SRVE0293E: [Servlet 錯誤]-[null]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport
報錯信息：[13-4-9 17:23:42:960 CST] 0000002d webapp E com.ibm.ws.webcontainer.webapp.WebApp logError SRVE0293E: [Servlet 錯誤]-[null]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport:
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:624)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1071)
at org.apache.struts2.dispatcher.Dispatcher.sendError(Dispatcher.java:839)
at org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:533)
at org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:434)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:852)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:917)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.invokeFilters(DefaultExtensionProcessor.java:924)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:852)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3610)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:274)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:926)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1557)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:173)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:202)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:766)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:896)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)
原因及解決辦法：對AESW打包是lib中需包含struts2-core-2.3.1.2.jar、struts2-spring-plugin-2.3.1.2.jar、xwork-core-2.3.1.2.jar。
如圖所示：
總結：該問題的解決辦法，是因為struts的標簽庫找不到導致的，上面這種做法就是把struts的jar包放到lib中，然后這樣就可以找到項目中的struts-tags.tld。
解決這個問題，有一個更好的辦法，就是把所有的struts的jar包放到共享庫中，同時把標簽庫struts-tags.tld也放到共享庫中，這樣在系統進行啟動的時候就進行編譯，這樣就沒問題，省得jar放到好多位置不便管理！
4) 用戶登陸無法訪問，頁面也沒提示報錯信息
報錯信息：[13-4-10 11:01:32:662 CST] 00000031 SystemOut O - select * from MFB2B.B2B_L_FRONT_USER where USERID = ?{[AES01]}
[13-4-10 11:01:35:853 CST] 00000037 Dispatcher W com.opensymphony.xwork2.util.logging.commons.CommonsLogger warn Could not find action or result
No result defined for action com.travelsky.aesw.front.user.action.FrontUserLoginAction and result comerror
at com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:376)
at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:278)
at org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:54)
at org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:510)
at org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:434)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:852)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:917)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.invokeFilters(DefaultExtensionProcessor.java:924)
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:852)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3610)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:274)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:926)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1557)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:173)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:202)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:766)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:896)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)
原因及解決辦法：AJAX內部錯誤，缺少AJAX相關的包，請參照第七點關於共享庫的配置。
該問題造成所有關於AJAX請求相關都無法操作，關於類似操作都是這個問題。
5) 訪問時報錯：SRVE0255E: A WebGroup/Virtual Host to handle aeswmfet/index.jsp has not been defined.
報錯信息：
SRVE0255E: A WebGroup/Virtual Host to handle 10.6.159.96:9085 has not been defined.
IBM WebSphere Application Server
解決辦法及思路：虛擬主機未正確配置，一般應用默認采用的Websphere自帶的 default_host。
進入 虛擬主機 > default_host > 主機別名
增加server對應的端口，如圖所示：
設置成功后，重新啟動集群，再次訪問正常。
6) 關於查看server的端口和JVM日志信息：
n 如何查看server的端口
1、控制台查看：
進入如下目錄：應用程序服務器 > aesServer1
在通信欄，點開端口，查看各端口詳情，如圖所示：
2、配置文件查看
目錄如下：/opt/app/WebSphere/profiles/AppSrv01/config/cells/vm-vmw233-tCell01/nodes/vm-vmw233-tNode01/
選擇serverindex.xml 配置文件，找到對應server，查看端口信息，如圖所示：
n 關於JVM日志配置及查看
1、關於systemOut.log、systemErr.log查看及配置進入如下目錄：
應用程序服務器 > aesServer1 > 進程定義 > 記錄和跟蹤 > JVM 日志
這里可以設置日志文件的大小及歷史日志文件個數。
如果需要查看具體日志的地址，需要結合websphere變量來查看。
如測試系統上面，這里配置的地址：${SERVER_LOG_ROOT}/SystemErr.log
打印出來的路徑是在：/opt/applog/WebSphere/AppSrv01/logs/aesServer1/ 下面。
7) 發布或更新應用程序時報WKSP0009E錯誤
應用在程序發布的最后一步出現WKSP0009E錯誤。
報錯信息：
com.ibm.ws.sm.workspace.WorkSpaceException: WKSP0009E Workspace is invalid
at com.ibm.ws.sm.workspace.impl.WorkSpaceLogger.createException(WorkSpaceLogger.java:85)
at com.ibm.ws.sm.workspace.impl.WorkSpaceLogger.createException(WorkSpaceLogger.java:57)
at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.checkValid(WorkSpaceImpl.java:170)
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.create(RepositoryContextImpl.java:300)
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.create(RepositoryContextImpl.java:284)
at com.ibm.ws.management.application.task.ConfigureTask.performTask(ConfigureTask.java:249)
at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:262)
at java.lang.Thread.run(Thread.java:797)
解決辦法：
1、該問題是由於控制台session超時造成的，首先確定你的WAS用戶是否登錄，有可能是同一個賬號被別人登錄。
2、如果用戶是登錄，重新部署扔出現問題，則通過修改config\cells\xxxxxxxxCell\applications\isclite.ear\deployments\isclite下的配置文件deployment.xml中屬性invalidationTimeout增加session超時時間
8) WAS刪除應用出錯
問題症狀：進入DMGR控制台，發現那個應用在【websphere企業應用程序】中看不到了，但是在【企業級應用程序】中可以看到該應用，狀態為未知，其余應用狀態為正在運行，刪除該應用時報錯，報錯信息如下：
CWWMH0149E: 無法刪除業務級應用程序“WebSphere:blaname=aeswmfet”，這是因為它包含組合單元。請先刪除所有屬於該業務級應用程序的組合單元，然后再刪除該業務級應用程序。 請檢查日志以了解詳細信息。
無法除去 WebSphere:blaname=aeswmfet。
問題原因及解決辦法：這個問題其實跟第一個問題有類似之處，出現這種問題，刪除應用會報這個錯，刪除server會報問題1這個錯誤。主要原因是應用沒有刪除干凈。造成該問題的有可能是安裝的時候突然斷電或者被別人踢出控制台等（如問題12就會造成這個問題）。
刪除dmgr/config/cellName/bla目錄下和cus目錄下中aeswmfet文件夾，重新刷新【企業級應用程序】，如果不含該應用則表示正常。