Problem with BIRT report after installing new version of KNIME

Dear Knimers, in my work I using reports and, until last update to KNIME 4.7, they are working quite well (except one complaine i made it before - problem with generating Report as word documents with two master pages) - now I faced with problem below (as I said, I do not any kind of changes before I
install new version of KNIME):

HTTP ERROR 500 javax.servlet.ServletException: javax.servlet.ServletException: JSP file [/webcontent/birt/pages/layout/FramesetFragment.jsp] not found
URI: /viewer/frameset
STATUS: 500
MESSAGE: javax.servlet.ServletException: javax.servlet.ServletException: JSP file [/webcontent/birt/pages/layout/FramesetFragment.jsp] not found
SERVLET: ViewerServlet
CAUSED BY: javax.servlet.ServletException: javax.servlet.ServletException: JSP file [/webcontent/birt/pages/layout/FramesetFragment.jsp] not found
CAUSED BY: javax.servlet.ServletException: JSP file [/webcontent/birt/pages/layout/FramesetFragment.jsp] not found
Caused by:
javax.servlet.ServletException: javax.servlet.ServletException: JSP file [/webcontent/birt/pages/layout/FramesetFragment.jsp] not found
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:157)
at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:717)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
at org.eclipse.jetty.server.Server.handle(Server.java:562)
at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)
at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:319)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)
at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:894)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1038)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: javax.servlet.ServletException: JSP file [/webcontent/birt/pages/layout/FramesetFragment.jsp] not found
at org.apache.jasper.servlet.JspServlet.handleMissingResource(JspServlet.java:400)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:368)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:327)
at org.eclipse.jetty.jsp.JettyJspServlet.service(JettyJspServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:590)
at org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)
at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1630)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:506)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:131)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:596)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:223)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1571)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1378)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:463)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1544)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1300)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129)
at org.eclipse.jetty.server.Dispatcher.include(Dispatcher.java:119)
at org.eclipse.birt.report.presentation.aggregation.layout.FramesetFragment.service(FramesetFragment.java:89)
at org.eclipse.birt.report.servlet.ViewerServlet.__doGet(ViewerServlet.java:167)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doGet(BirtSoapMessageDispatcherServlet.java:143)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:503)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:332)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:590)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.service(BirtSoapMessageDispatcherServlet.java:115)
at org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419) …

2 Likes

I had the same issue.

Dear Knimers, do you have any explanation/solution? Although this message appears, it is possible to generate docx, pdf documents, the only thing is that it is not possible to open the report directly in a web browser.

Hi @ssimara -

No explanation yet, although you are not the first to have noticed this. I’m asking for more details internally.

Thanks ScottF, glad to hear you are work on solution.

We have an existing ticket for this (AP-19863), so the developers are aware. Can you confirm which operating system you are using - I suspect Mac OS?

No, it is Win10 system.

1 Like

Can you try starting KNIME AP with the -clean parameter in the knime.ini file? (Be sure to remove it afterward, as it increases startup time.)

Alternately, if that doesn’t help, does the situation improve using a new workspace, or fresh installation?

As I said earlier, I did’t make any kind of changes before I star upgrade from 4.6 to 4.7 using default update process from app - and I did allready, after I noticed problem with report creation, start fresh new installation of KNIME. I also, after no success, apply -clean method in ini file - nothing change.
I did not try with using a new workspace - do you mean that I have to create new workflow folder and copy my workflows in it?

I ask because there’s a suspicion internally that this may be caused by a classpath resolution issue caused by the update, not anything you did or didn’t do. We’re still trying to track down what that might be.

Sorry to hear -clean didn’t help. You can create a new workspace by going to File -> Switch Workspaces -> Other... and then just entering a new directory name. If you copy over the workflow in that question to the new workspace, it would be interesting to see if running it from there changes anything.

I just tested with new workspace - nothing change.

OK, thanks for the feedback on the fixes you tried. We’ll keep investigating.

I had the same issue win11