Fellow wmUsers:
I’ve have a frustrating problem with MWS 7.1.1 and Monitor 7.1 on Solaris Unix.
The WmMonitor 7.1 package loads fine on IS 7.1.1, but whenever I attempt to view the WmMonitor homepage, the following error occurs:
2009-01-12 16:39:10 CST [MON.0119.0000E] Error while saving Monitor configuration: com.webMethods.sc.security.passman.PasswordManagerException: Wrapped Exception:
at com.webMethods.sc.security.passman.PasswordManagerFactory.getSharedComponentPasswordManager(PasswordManagerFactory.java:135)
at wm.monitor.util.instance(util.java:563)
at wm.monitor.util.getPassword(util.java:573)
at wm.monitor.util.configSettings(util.java:190)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:403)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:631)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:241)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:228)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:624)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:536)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:237)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:119)
at com.wm.app.b2b.server.ns.Namespace.invoke(Namespace.java:604)
at com.wm.util.template.Reporter.invoke(Reporter.java:964)
at com.wm.util.template.InvokeToken.eval(InvokeToken.java:75)
at com.wm.util.template.TemplateToken.evalChild(TemplateToken.java:234)
at com.wm.util.template.TemplateToken.eval(TemplateToken.java:200)
at com.wm.util.template.Reporter.reportNoReset(Reporter.java:1300)
at com.wm.util.template.Reporter.reportToOutput(Reporter.java:1275)
at com.wm.util.template.Reporter.reportIData(Reporter.java:1164)
at com.wm.app.b2b.server.HTTPDocHandler._process(HTTPDocHandler.java:516)
at com.wm.app.b2b.server.HTTPDocHandler.process(HTTPDocHandler.java:130)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:199)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:327)
at com.wm.util.pool.PooledThread.run(PooledThread.java:118)
at java.lang.Thread.run(Thread.java:595)
I have reported this problem to webMethods support a few weeks ago, but they act like they have no idea what the problem is. This problem also appears to be preventing me from enabling Business Process Analysis in MWS 7.1.1.
This problem appears to be fixed in Monitor 7.1.2, but we cannot move to 7.1.2 soon enough. Has anyone seen this problem before?
No we have not came across this error before…But tech support have to give you some support on this issue with either a fix/patch etc…stay on it…
Did you try reload the package and increase the logging level to TRACE or DEBUG while reloading? Do you see any other dependency packages loaded partial??
In addition I did notice WmMonitor had a dependency on WmPRT 7.1. WmPRT 7.1.1 was actually the version that was fully loaded. So I updated the dependency on WmMonitor to just WmPRT . and reloaded WmMonitor, but this has not helped resolve the problem.
I installed a debug jar provided from webMethods support and provided stdout output of the error from IS 7.1.1. The trace pointed to a custom logging package we had running that was not allowing Monitor 7.1 to log when it wanted to. This was corrected in a new of the logging package.