2017-09-25 132 views
0

我在(Sterling OMS)EAR文件部署后启动服务器时遇到问题。 我已按照以下步骤操作:异常:javax.management.InstanceNotFoundException SourceId:com.ibm.ws.management.AdminServiceImpl.invoke ProbeId:672

  1. 创建了WAS配置文件。
  2. 部署EAR文件。
  3. 重新启动服务器,然后发生这些错误

注意 - 之前部署EAR文件,那么服务器启动成功没有任何错误,但是当我部署的EAR文件,然后服务器启动,但发生错误:

FFDC Exception:javax.management.InstanceNotFoundException SourceId:com.ibm.ws.management.AdminServiceImpl.invoke ProbeId:672 Reporter:[email protected] 
javax.management.InstanceNotFoundException: com.ibm.sterling:Type=CurrentServerMBean,name=sterling.oms_4 
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1107) 
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBeanInfo(DefaultMBeanServerInterceptor.java:1387) 
at com.sun.jmx.mbeanserver.JmxMBeanServer.getMBeanInfo(JmxMBeanServer.java:932) 
at com.ibm.ws.management.AdminServiceImpl.getMBeanInfo(AdminServiceImpl.java:1542) 
at com.ibm.ws.management.AdminServiceImpl.checkForOpDeprecation(AdminServiceImpl.java:2813) 
at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2420) 
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1327) 
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) 
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1243) 
at com.ibm.ws.management.PlatformMBeanServer.invoke(PlatformMBeanServer.java:749) 
at com.ibm.sterling.afc.jmx.PLTJMXInitializer.registerMBeans(PLTJMXInitializer.java:117) 
at com.ibm.afc.jmx.PLTJMXUtils.initJmxMBeans(PLTJMXUtils.java:37) 
at com.yantra.appserver.PostInitHelper.init(PostInitHelper.java:52) 
at com.yantra.appserver.PostServletInitializer.init(PostServletInitializer.java:45) 
at javax.servlet.GenericServlet.init(GenericServlet.java:161) 
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:344) 
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168) 
at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1368) 
at com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:631) 
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:597) 
at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:425) 
at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88) 
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:170) 
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:904) 
at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:789) 
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:427) 
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:719) 
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1179) 
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1390) 
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:639) 
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:979) 
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:778) 
at com.ibm.ws.runtime.component.ApplicationMgrImpl$5.run(ApplicationMgrImpl.java:2198) 
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5396) 
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5612) 
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255) 
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2203) 
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:435) 
at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123) 
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:378) 
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:126) 
at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:984) 
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:502) 
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892) 

==> Performing default dump from com.ibm.ws.management.dm.JmxDM :Mon Sep 25 
+0

如果我们有亲密看看堆栈跟踪,有人试图调用一个不存在的mbean。这可能是因为它还没有启动的任何耗材。 'javax.management.InstanceNotFoundException:com.ibm.sterling:Type = CurrentServerMBean,name = sterling.oms_4' 粗略的解决方案可能是捕获异常,退出一段时间,然后重试它。更好的解决方案可能是找出为什么这个mbean不存在。 –

回答

0

Sterling Order Management安装MBeans以提供JMX监控。确保java SecurityManager允许MBean注册。

如果您使用的是Java的默认安全管理器,能够在/lib/security/java.policy文件中的下列政策:

许可javax.management.MBeanTrustPermission“注册”