1、1.核心业务系统操作系统配置检查系统配置:名称建议值实际值是否符合要求操作系统版本Linux/HpRed Hat AS4Y主机名N/AApp1CPU 1GHZ8*1.9G,存 2G16G磁盘空间20G360G系统核参数:说明文件句柄数4096或更大8192进程的最大文件句柄数JAVA虚拟机配置检查虚拟机安装路径:/opt/jdk1.5.0_17/JVM 版本1.5JDK 1.5.0_17JVM HEAP初始值 -Xms514M1024MJVM HEAP最大值 -Xmx512M-1536M1536MPermsize64M256MOSS配置检查安装路径:/opt/oss/oss-4.2.3.GA参
2、数值线程数400一个CPU对应50个线程左右线程的个数应与CPU的处理能力匹配。JSP编译的调试信息标志false生产环境中建议将JSP编译调试功能关闭,减少因编译占用系统资源对系统的影响。开发模式的设置应用使用的连接池数量生产环境中建议将连接的数量与线程总数保持统一。应用使用的连接池初始值100最小值和最大值保持一致,避免运行状态在创建连接时消耗系统资源。连接池Prepared Statement Cache无10缺省OSS服务器是不会Cache Prepared Statement对象的,为了提高性能我们可以设定每个连接Cache的 Prepared Statement对象的个数运行期系统
3、状态检查平均值峰值是否异常35%以下60%未出现长时间CPU使用率超过100%存使用3.5G以下无页交换的情况20%满足应用日志或者OSS日志所用磁盘空间要求网络流量200K/S800K/S无网络阻塞和网络风暴运行期虚拟机状态检查实际情况JVM HEAP最小值280MJVM HEAP最大值1100M为今天的观察结果运行期OSS组件状态检查正常值线程使用情况使用率50%70%启动目录core文件的检查在OSS启动目录中发现“core”文件和“hs_err_pid*.log”的错误日志文件,说明系统出现过JVM core dump和异常退出故障,故障出现在一个虚拟机的解压缩操作,希望能通过进一步与
4、开发商,维护人员沟通找出具体的故障原因,并提出解决方案。日志检查日志中Error信息检查Review All LogsN对日志中Error消息进行检查,参考下面例子。日志文件中发现错误信息如下:1)启动oss时报如下错误:出现过一次22:53:52,907 ERROR MainDeployer Could not create deployment: file:/D:/新建文件夹/oss-4.2.2.GA/server/default/conf/oss-service.xml org.oss.deployment.DeploymentException: - nested throwable:
5、 (java.lang.reflect.UndeclaredThrowableException) at org.oss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) at org.oss.system.ServiceController.install(ServiceController.java:226) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl
6、.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.oss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.oss.mx.server.Invocation.dispatch(Invocation.java:94) at org.oss.mx.
7、server.Invocation.invoke(Invocation.java:86) at org.oss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.oss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.oss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.install(Unknown Source) at org
8、.oss.deployment.SARDeployer.create(SARDeployer.java:249) at org.oss.deployment.MainDeployer.create(MainDeployer.java:969) at org.oss.deployment.MainDeployer.deploy(MainDeployer.java:818) 782) 766) at org.oss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) 88) at org.oss.mx.in
9、terceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at $Proxy5.deploy(Unknown Source) at org.oss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.oss.system.server.ServerImpl.start(ServerImpl.java:362) at org.oss.Main.boot(Main.java:200) at org.oss.Ma
10、in$1.run(Main.java:508) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.reflect.UndeclaredThrowableException at org.oss.system.ServiceCreator.install(ServiceCreator.java:236) at org.oss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451) 171) . 36 more java.lang.Err
11、or: ERROR: it turns out the root cause is not always a runtime exception! at org.oss.mx.server.MBeanServerImpl.handleInstantiateExceptions(MBeanServerImpl.java:1295) at org.oss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1237) 286) at org.oss.mx.server.MBeanServerImpl.createMBean(MBea
12、nServerImpl.java:344) 157) . 38 moreoss-service.x配置错误,通过修改具体错误配置,并解决了这个问题。2)NoClassDefFoundError错误,当前的类装载器不能找到这个类文件,频率:出现一次java.lang.NoClassDefFoundError: Could not initialize class org.oss.aspects.security.SecurityActions$ContextInfoActions at org.oss.aspects.security.SecurityActions.getContextExce
13、ption(SecurityActions.java:467) at org.oss.aspects.security.AuthenticationInterceptor.authenticate(AuthenticationInterceptor.java:131) at org.oss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:66) at org.oss.e3.security.E3AuthenticationInterceptor.invoke(E3Authentic
14、ationInterceptor.java:110) at org.oss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.oss.e3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.oss.e3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.oss.e3.state
15、less.StatelessContainer.localInvoke(StatelessContainer.java:240) at org.oss.e3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84) at $Proxy147.getInitConfigAsInteger(Unknown Source) at .police.alarm.AlarmAction.execute(AlarmAction.java:28) at org.apache.struts.action.RequestProcessor.
16、processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet. . Servlet.se
17、rvice( Servlet.java:690) 803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at .police.filter.SystemUserFilter.doFilter(SystemUserFilter.java:61) 235) a
18、t .police.filter.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:37) at org.oss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardCont
19、extValve.invoke(StandardContextValve.java:175) at org.oss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.oss.web.tomcat.security.JaccContextValve.invoke(JaccContex
20、tValve.java:at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.oss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:at org.apache.catalina.core.Standard
21、EngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote. 11. 11Processor.process( 11Processor.java:844) at org.apache.coyote. 11. 11Protocol$ 11ConnectionHandler.process( 11Protocol.java:583) at .JIoEndpoint
22、$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619)NoClassDefFoundError错误,通过找到类所在的文件,并通过正确配置或使其在正确的类路径中来解决此问题。故障汇总1)在OSS启动目录中发现“core”文件和“hs_err_pid*.log”的错误日志文件,说明系统出现过JVM core dump和异常退出故障,故障出现在一个虚拟机的解压缩操作,希望能通过进一步与开发商,维护人员沟通找出具体的故障原因,并提出解决方案。2)部署问题,部署描述符配置错误,需仔细检查部署描述符号。3)NoClassDefFoundError,原因为在当前的类装载器路径中,不能找到相关的类文件,需检查类装载路径里面是否存在
copyright@ 2008-2022 冰豆网网站版权所有
经营许可证编号:鄂ICP备2022015515号-1