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://*.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文件夹，重新刷新【企业级应用程序】，如果不含该应用则表示正常。