Petals Web-Console

Unable to usethe web console

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.4
  • Fix Version/s: 2.0.6
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When we acces to the web console (started into tomcat 6), at the fisrt, we've got a stacktrace. So we fully can't use the ui (sniff).Exactly the same error (and nothing more) is found into the tomcat logs:
    30 sept. 2010 17:07:55 org.ow2.opensuit.xml.base.error.ErrorHandler servePage
    GRAVE: Error while rendering error page:
    org.ow2.opensuit.cel.impl.tree.ExpressionEvaluationException: Error while evaluating expression 'managementUIBean': null
    at org.ow2.opensuit.cel.impl.tree.impl.ast.AstIdentifier.invoke(AstIdentifier.java:72)
    at org.ow2.opensuit.cel.impl.tree.impl.ast.AstDot.invoke(AstDot.java:133)
    at org.ow2.opensuit.cel.impl.tree.impl.ast.AstEval.invoke(AstEval.java:59)
    at org.ow2.opensuit.core.expression.ExpressionUtils.invokeExpression(ExpressionUtils.java:119)
    at org.ow2.opensuit.xml.base.binding.Expression.invoke(Expression.java:147)
    at org.ow2.opensuit.xml.base.html.menu.SubMenu.render(SubMenu.java:158)
    at org.ow2.opensuit.xml.base.html.menu.Menu.render(Menu.java:132)
    at org.ow2.opensuit.xml.base.html.layout.Div.render(Div.java:110)
    at org.ow2.opensuit.xml.base.html.layout.Div.render(Div.java:110)
    at org.ow2.opensuit.xml.base.html.Frame.render(Frame.java:93)
    at org.ow2.opensuit.xml.base.error.ErrorHandler.servePage(ErrorHandler.java:174)
    at org.ow2.opensuit.xml.base.Application.service(Application.java:581)
    at org.ow2.opensuit.core.impl.j2ee.OpenSuitServlet.service(OpenSuitServlet.java:155)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
    at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
    at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
    at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
    at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706)
    at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677)
    at org.apache.jsp.index_jsp._jspService(index_jsp.java:54)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.NullPointerException
    at org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.connect(ManagementUIBean.java:296)
    at org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.<init>(ManagementUIBean.java:178)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at org.ow2.opensuit.xml.base.binding.Bean.getObject(Bean.java:126)
    at org.ow2.opensuit.xml.base.binding.JavaBeans.getBeanValue(JavaBeans.java:105)
    at org.ow2.opensuit.xml.base.Application.getBeanValue(Application.java:806)
    at org.ow2.opensuit.xml.interfaces.BaseBeanProvider.getParentBeanValue(BaseBeanProvider.java:101)
    at org.ow2.opensuit.xml.base.html.menu.SubMenu.getBeanValue(SubMenu.java:347)
    at org.ow2.opensuit.core.expression.OpenSuitEvaluationContext.getVariable(OpenSuitEvaluationContext.java:68)
    at org.ow2.opensuit.cel.impl.tree.impl.ast.AstIdentifier.invoke(AstIdentifier.java:68)
    ... 40 more

    Error while evaluating expression 'managementUIBean': null

    NB: petals view 1.2 is OK under the same environment.

    Show
    When we acces to the web console (started into tomcat 6), at the fisrt, we've got a stacktrace. So we fully can't use the ui (sniff).Exactly the same error (and nothing more) is found into the tomcat logs: 30 sept. 2010 17:07:55 org.ow2.opensuit.xml.base.error.ErrorHandler servePage GRAVE: Error while rendering error page: org.ow2.opensuit.cel.impl.tree.ExpressionEvaluationException: Error while evaluating expression 'managementUIBean': null at org.ow2.opensuit.cel.impl.tree.impl.ast.AstIdentifier.invoke(AstIdentifier.java:72) at org.ow2.opensuit.cel.impl.tree.impl.ast.AstDot.invoke(AstDot.java:133) at org.ow2.opensuit.cel.impl.tree.impl.ast.AstEval.invoke(AstEval.java:59) at org.ow2.opensuit.core.expression.ExpressionUtils.invokeExpression(ExpressionUtils.java:119) at org.ow2.opensuit.xml.base.binding.Expression.invoke(Expression.java:147) at org.ow2.opensuit.xml.base.html.menu.SubMenu.render(SubMenu.java:158) at org.ow2.opensuit.xml.base.html.menu.Menu.render(Menu.java:132) at org.ow2.opensuit.xml.base.html.layout.Div.render(Div.java:110) at org.ow2.opensuit.xml.base.html.layout.Div.render(Div.java:110) at org.ow2.opensuit.xml.base.html.Frame.render(Frame.java:93) at org.ow2.opensuit.xml.base.error.ErrorHandler.servePage(ErrorHandler.java:174) at org.ow2.opensuit.xml.base.Application.service(Application.java:581) at org.ow2.opensuit.core.impl.j2ee.OpenSuitServlet.service(OpenSuitServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302) at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:706) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:677) at org.apache.jsp.index_jsp._jspService(index_jsp.java:54) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.connect(ManagementUIBean.java:296) at org.ow2.petals.tools.webconsole.uibeans.ManagementUIBean.<init>(ManagementUIBean.java:178) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.ow2.opensuit.xml.base.binding.Bean.getObject(Bean.java:126) at org.ow2.opensuit.xml.base.binding.JavaBeans.getBeanValue(JavaBeans.java:105) at org.ow2.opensuit.xml.base.Application.getBeanValue(Application.java:806) at org.ow2.opensuit.xml.interfaces.BaseBeanProvider.getParentBeanValue(BaseBeanProvider.java:101) at org.ow2.opensuit.xml.base.html.menu.SubMenu.getBeanValue(SubMenu.java:347) at org.ow2.opensuit.core.expression.OpenSuitEvaluationContext.getVariable(OpenSuitEvaluationContext.java:68) at org.ow2.opensuit.cel.impl.tree.impl.ast.AstIdentifier.invoke(AstIdentifier.java:68) ... 40 more Error while evaluating expression 'managementUIBean': null NB: petals view 1.2 is OK under the same environment.
  • Environment:
    petals-platform 3.1.x (maintenance branch) put into attachments, jdk 1.6, tomcat 6, RHEL 5

Activity

Hide
Adrien Ruffie added a comment - Thu, 25 Nov 2010 - 15:45:35 +0100

This issue is also corrected with the bug correction for JIRA ISSUE 32

Show
Adrien Ruffie added a comment - Thu, 25 Nov 2010 - 15:45:35 +0100 This issue is also corrected with the bug correction for JIRA ISSUE 32
Hide
Adrien Ruffie added a comment - Mon, 18 Oct 2010 - 11:13:28 +0200

I will investigate this problem

Show
Adrien Ruffie added a comment - Mon, 18 Oct 2010 - 11:13:28 +0200 I will investigate this problem
Hide
Frédéric Gardes added a comment - Tue, 5 Oct 2010 - 10:57:07 +0200 - edited

I always feel I talk lonely myself afterwards: 4 comments following one another .
I found: there a "by default connection" to an ESB on localhost. But when we don't have this connection but another on an IP (not localhost)...it failes... We've got the same thing with any connection registered into the webconsole (with the radio button checkbox "Save server") automatically trying to connect to non existent ESB server...
Do you have the same problem under Ubuntu, or is there a RHEL specific crash?
The solution today is:
1) remove the default localhost server into WEB-INF/classes/webconsole.xml
2) ignite a candle to hope that nobody try to connect to the webconsole with the ESB stopped .

Show
Frédéric Gardes added a comment - Tue, 5 Oct 2010 - 10:57:07 +0200 - edited I always feel I talk lonely myself afterwards: 4 comments following one another . I found: there a "by default connection" to an ESB on localhost. But when we don't have this connection but another on an IP (not localhost)...it failes... We've got the same thing with any connection registered into the webconsole (with the radio button checkbox "Save server") automatically trying to connect to non existent ESB server... Do you have the same problem under Ubuntu, or is there a RHEL specific crash? The solution today is: 1) remove the default localhost server into WEB-INF/classes/webconsole.xml 2) ignite a candle to hope that nobody try to connect to the webconsole with the ESB stopped .
Hide
Frédéric Gardes added a comment - Tue, 5 Oct 2010 - 09:07:57 +0200

Arff bad new: I already have got the same error on some servers, and not on others. I tried with local host, IP host (configurated into the topology.xml):it's the same issue. I'm investigating...
Can I have just some help about this NPE into ManagementUIBean.connect(ManagementUIBean.java:296)? It means that it can found the ESB? The server IP? What? Is it the first bean called or others beans are OK before? Are you really using tomcat 6? I don't know how to search today...
Thank you!

Show
Frédéric Gardes added a comment - Tue, 5 Oct 2010 - 09:07:57 +0200 Arff bad new: I already have got the same error on some servers, and not on others. I tried with local host, IP host (configurated into the topology.xml):it's the same issue. I'm investigating... Can I have just some help about this NPE into ManagementUIBean.connect(ManagementUIBean.java:296)? It means that it can found the ESB? The server IP? What? Is it the first bean called or others beans are OK before? Are you really using tomcat 6? I don't know how to search today... Thank you!
Hide
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 17:17:08 +0200

It's ok. I compiled again the platform 3.1.x...and it failed again. I think you're going to delete the platform 3.1.x branch. So you can close this track: thank you very much!

Show
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 17:17:08 +0200 It's ok. I compiled again the platform 3.1.x...and it failed again. I think you're going to delete the platform 3.1.x branch. So you can close this track: thank you very much!
Hide
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 14:57:12 +0200

Okay : I'm going to test together:
-platform 3.1.1
-webconsole 2.0.4
-jdk 1.6
-tomcat 6
-RHEL 5
See you...

Show
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 14:57:12 +0200 Okay : I'm going to test together: -platform 3.1.1 -webconsole 2.0.4 -jdk 1.6 -tomcat 6 -RHEL 5 See you...
Hide
Roland Naudin added a comment - Mon, 4 Oct 2010 - 14:35:00 +0200

Container 3.1.1 is released. I think it's released...to be used
The Web Console 2.0.4 has been tested successfully on container 3.1.1.

Show
Roland Naudin added a comment - Mon, 4 Oct 2010 - 14:35:00 +0200 Container 3.1.1 is released. I think it's released...to be used The Web Console 2.0.4 has been tested successfully on container 3.1.1.
Hide
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 11:01:07 +0200

Another way : I can use the 3.1.1 instead of 3.1.x? If you say me ok it's tested and ready, I can (like each week) change my version...

Show
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 11:01:07 +0200 Another way : I can use the 3.1.1 instead of 3.1.x? If you say me ok it's tested and ready, I can (like each week) change my version...
Hide
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 10:56:54 +0200 - edited

mmmh...
I think that the main difference is...the platform. I don't care about the 3.1.1, but the 3.1.x...like announced into the webconsole log. You need to drop down the 3.1: there is a big leak (each message increase the heap, because it passes throught the priority queue). Can I put the platform zip 3.1.x here? It's very buzy this fucking 29 Mo limitation under Jira.
Olivier, I'm going to send you directly the zip used. You can also see internally to get this maintenance version.

Show
Frédéric Gardes added a comment - Mon, 4 Oct 2010 - 10:56:54 +0200 - edited mmmh... I think that the main difference is...the platform. I don't care about the 3.1.1, but the 3.1.x...like announced into the webconsole log. You need to drop down the 3.1: there is a big leak (each message increase the heap, because it passes throught the priority queue). Can I put the platform zip 3.1.x here? It's very buzy this fucking 29 Mo limitation under Jira. Olivier, I'm going to send you directly the zip used. You can also see internally to get this maintenance version.
Hide
Olivier Fabre added a comment - Fri, 1 Oct 2010 - 18:01:57 +0200

I've tried with a petals platform 3.1.1 (last maintenance release), jdk 1.6, tomcat 6 and petals webconsole 2.0.4, ubuntu 9.10. It works fine.

The only difference is linux distrib. We must mount a test env with this RHEL 5 distrib and test...

Show
Olivier Fabre added a comment - Fri, 1 Oct 2010 - 18:01:57 +0200 I've tried with a petals platform 3.1.1 (last maintenance release), jdk 1.6, tomcat 6 and petals webconsole 2.0.4, ubuntu 9.10. It works fine. The only difference is linux distrib. We must mount a test env with this RHEL 5 distrib and test...
Hide
Frédéric Gardes added a comment - Fri, 1 Oct 2010 - 09:56:01 +0200

I can't put the platform 3.1.x used :the fucking size limit to 29 Mo blockes me. I can provide it if needed.

Show
Frédéric Gardes added a comment - Fri, 1 Oct 2010 - 09:56:01 +0200 I can't put the platform 3.1.x used :the fucking size limit to 29 Mo blockes me. I can provide it if needed.

People

Dates

  • Created:
    Fri, 1 Oct 2010 - 09:53:54 +0200
    Updated:
    Thu, 25 Nov 2010 - 15:45:35 +0100
    Resolved:
    Thu, 25 Nov 2010 - 15:45:35 +0100