Forum

This content is now out of date.

Visit Our Community

Getting error while logging out after upgrading to Yellowfin BI 7.1 – build 20150501

12 May, 2015

Hello,

After upgrading to Yellowfin BI 7.1 - build 20150501 we are getting this error while logout. We are on Amazon Linux

Exception:
org.apache.jasper.JasperException: The absolute uri: http://jakarta.apache.org/struts/tags-html cannot be resolved in either web.xml or the jar files deployed with this application
Stacktrace:
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:56)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:445)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:117)
org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:325)
org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:154)
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:410)
org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1427)
org.apache.jasper.compiler.Parser.parse(Parser.java:138)
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:242)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:102)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:373)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
Hello Muthu,

Is there is a chance that this issue was also put in by your colleague (Dieter)? If so, there should be
a response to him today. If not, it looks like you are facing the same issue and our team came up
with this as a resolution;

This is an artefact of upgrading to Struts 1.4

Change all instances of:

jakarta.apache.org/struts/

to

struts.apache.org/

in all custom JSPs.



Can you please make these changes and let us know how it all goes?

Thank you,

Kyle

Hi Kyle,

Dieter is not my colleague though in any case I changed custom_index_mi.jsp to reflect struts.apache.org, logoff issue has been resolved.

Thanks for your help.

Cheers
Hi Muthu,

OK, well I am glad to hear that this worked for you and now I know that
you and Dieter do not work together!

Thank you for getting back to me and letting me know this worked.

Cheers,

Kyle

Also worth reading: