Error using the RAM setup application on a WebSphere cluster
I installed the RAM setup application to a WebSphere NS 6.1.0.29 cluster using the deployClusterSetup.py script. Following this, I started up the setup application from the admin console. Then I tried to access the RAM setup application. The Introduction page does not show. In its place is a stack trace indicating that some prerequisites have not been installed. Except I am not sure what.
java.lang.NullPointerException at com.ibm.ram.repository.setup.web.WASServer.getInstallPrerequisiteStatus(WASServer.java:2127) at com.ibm.ram.repository.setup.web.access.RAMConfigurationBean.getInstallPrerequisiteStatus(RAMConfigurationBean.java:750) at com.ibm.ram.repository.setup.web.access.RAMConfigurationBean.getSettingsSelectionStatus(RAMConfigurationBean.java:710) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.commons.el.ArraySuffix.evaluate(ArraySuffix.java:314) at org.apache.commons.el.ComplexValue.evaluate(ComplexValue.java:145) at org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:263) at org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:190) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:754) at com.ibm._jsp._index._jspx_meth_c_set_14(_index.java:902) at com.ibm._jsp._index._jspService(_index.java:492) at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:87) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1152) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) at com.ibm.ram.repository.setup.web.wizard.servlets.main.SetupAssistantFilter.doFilter(SetupAssistantFilter.java:66) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:837) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:680) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:525) at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:232) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:751) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1478) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:126) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818) 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:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497) |
2 answers
I installed the RAM setup application to a WebSphere NS 6.1.0.29 cluster using the deployClusterSetup.py script. Following this, I started up the setup application from the admin console. Then I tried to access the RAM setup application. The Introduction page does not show. In its place is a stack trace indicating that some prerequisites have not been installed. Except I am not sure what. what version of RAM are you running, from the exception log , it appears that you are running RAM 7.2 base version on WAS 6.1.0.29 . There is a known problem with RAM 7.2 Setup on running it on any WAS version higher than the supported version for 7.2 base(which is 6.1.0.27), since you are on 29, its recommended that you upgrade to 7202 7202 is available externally at http://www-01.ibm.com/support/docview.wss?uid=swg24026093&rs=0&cs=utf-8&context=SSUS84&dc=D400&loc=en_US&lang=en&cc=US |
|
Thanks. Moving to RAM 7202 did help with that problem
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.