Hi,

how can I monitor memory usage on the MWS?
I’ve tried to use the wm_memorymonitor portlet but it throws an exception.

java.lang.NullPointerException
at ui.portlets.wm_memorymonitor._default._jspService(_default.java:676)
at com.webMethods.portal.framework.presentation.handlers.Jsp.render(Jsp.java:288)
at com.webMethods.portal.framework.presentation.handlers.Jsp.render(Jsp.java:228)
at com.webMethods.portal.framework.portlet.beans.JspPortletBean.generateContent(JspPortletBean.java:147)
at com.webMethods.portal.framework.portlet.beans.JspPortletBean.getContentInternal(JspPortletBean.java:76)
at com.webMethods.portal.framework.portlet.beans.BasicPortletBean.getContent(BasicPortletBean.java:143)
at com.webMethods.portal.mech.portlet.impl.PortletMechanics.getPortletContent(PortletMechanics.java:96)
at com.webMethods.portal.mech.storage.page.PortletHelper.renderContent(PortletHelper.java:428)
at com.webMethods.portal.mech.storage.page.PortletHelper.renderContent(PortletHelper.java:400)
at com.webMethods.portal.framework.presentation.renderers.DefaultRenderer.renderPageContent(DefaultRenderer.java:304)
at com.webMethods.portal.framework.presentation.renderers.DefaultRenderer.render(DefaultRenderer.java:215)
at com.webMethods.portal.framework.presentation.PresentationManager.handlePres(PresentationManager.java:370)
at com.webMethods.portal.framework.dispatch.DispatchManager.pres(DispatchManager.java:620)
at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:460)
at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:370)
at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:50)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:42)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)

Thanks
Bruno

Could you do me a quick favor? Could you tell me what version of MWS you are using and how you accessed the wm_memorymonitor?

Thanks,
–mark

Hi,

I logged in as sysadmin and on the Analysis window selected “Memory Monitor”. That’s it.

Here’s the version:
Version: 8.0.2.0.50
Build Date: 2010-05-18
Installed Fixes: MWS_8.0_SP2_Fix2_MWS-5264,MWS_8.0_SP2_Fix2

Thanks
Bruno

That seems straightforward enough It is clearly a defect. If you’d like to get a fix for this, please file an SR.

Hi,

ok, I’ll do that.
Is this the way recommended by SAG to monitor memory usage on MWS?

Thanks
Bruno

With 8.x, you can attach a JMX monitor which will give you richer information and integrate with your JMX tools (if you use any). In our upcoming 8.2 release we have a new suite of diagnostic tools and portlets that will allow for more interactive examination and investigation of the MWS runtime as well.