Replies: 29 comments 72 replies
-
That stacktrace does not look like it is coming from a 4.13 release. I could not match the line-numbers with any release above 4.8+ |
Beta Was this translation helpful? Give feedback.
-
Thank you again for your reply. yes, I guess stack trace does not belong to the 4.13 release it is running fine, and just copied the given data on the web apps folder and if I click on it shows birt homepage and after clicking on view example link it shows a fatal error. |
Beta Was this translation helpful? Give feedback.
-
I switched Java version 11 to 1.8 and resulted from stop working Both links that are birt 2.5.1 and 4.13 complete log entries of catalina.2023-06-12.log complete log entries of localhost_access_log.2023-06-12 I have attached log files for further reference. Thanks. |
Beta Was this translation helpful? Give feedback.
-
You should use Java11. |
Beta Was this translation helpful? Give feedback.
-
I am using java 11. one thing I didn't understand that data was copied into web apps folder name bank does not have .war file in it so why does it display BIRT version 2.5.1. reports are in bank folder and should work with latest birt 4.13 version. |
Beta Was this translation helpful? Give feedback.
-
you can see that there is no birt.war file in this folder. |
Beta Was this translation helpful? Give feedback.
-
Note that as we plan to release 4.14 relatively soon, when I see issues like this I wonder "does this actually work for 4.14"? |
Beta Was this translation helpful? Give feedback.
-
index.jsp file is in bank folder that belongs to an older version of birt 2.5.1. should it be replaced with new version of jsp file so by doing this would it work Thanks |
Beta Was this translation helpful? Give feedback.
-
but you need to put the data in the web apps folder that belongs to older version of BIRT |
Beta Was this translation helpful? Give feedback.
-
I am sorry, but I do not understand what it is you are trying to do. Can you explain in detail what you have done? It sounds like you try to have two versions of Birt installed on the same Tomcat. If you are trying that: you are out of luck. All deployed web applications share the same JVM, so you will have classloading issues if you try to do that. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply. no, I am not running two different sessions on the Tomcat server. I just explained in an earlier message that I just copied data into web apps folder which is present on the other server and it has birt older version like 2.5.1. in this data folder no birt.war file is present but it is using an older version of the homepage. |
Beta Was this translation helpful? Give feedback.
-
You will need to provide a detailed description of how to reproduce the encountered issue. You say in one of the comments that the stacktrace probably does not belong to a 4.13 instance since that one is "running fine". And that we should "put the data in the web apps folder that belongs to older version of BIRT" -to make it fail. If that data is needed to reproduce the error you need to provide it. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply. This is a complete status of manager apps you can see that there is two link name birt and bank both displaying together with upper and lower direction. birt has a new version 4.13 and it successfully launched its test report. when I come on the bank link it shows this home page i test this example link then it shows a fatal error so that's why said trace is not belong to 4.13 because it is working fine. according to my understanding if I put two birt.war files into different folders so Tomcat creates multiple sessions against two files. if I am mistaken on this point then please correct me. I have only one birt.war file into the web apps folder. |
Beta Was this translation helpful? Give feedback.
-
Looking at this setup I do not think that this is a bug. You will need to deploy your old report into the new viewer. There is information on how to do that here: If that is not an option for you, you will need to have two Tomcat instances running on the machine. One for every version of Birt that you need to use. I would go for the first option. |
Beta Was this translation helpful? Give feedback.
-
no idea @claesrosell @hvbtup |
Beta Was this translation helpful? Give feedback.
-
@shahzad80 please document how you resolved it. |
Beta Was this translation helpful? Give feedback.
-
If it is not resolved then yes.
|
Beta Was this translation helpful? Give feedback.
-
I am facing two issues after installing Eclipse 2023 in Linux and Windows too, Linux. I mentioned in this thread earlier that there is no run report option in browser view. Windows reports are not opened in a browser view and it displays errors like error 503 and sometimes error 500 |
Beta Was this translation helpful? Give feedback.
-
It works for me installing into the 2023-06 Java package on Windows 10: Given your stack trace, I don't think you really installed the latest 4.14 where we see there versions of GEF and ReportMultiBookPage will not have class cast exceptions: Check what version of GEF is installed (in the help about dialog): And the editor version: |
Beta Was this translation helpful? Give feedback.
-
this is for your further reference. it shows birt 4.14 when I am trying to update the existing version. |
Beta Was this translation helpful? Give feedback.
-
Funny that I see Eclipse 4.29 things but the 2023-06 release was Eclipse 4.28. But then, BIRT's update site pulls in all transitive dependencies, so effective the whole Eclipse Platform. Try unchecking the last two items. Otherwise create a new installation and install into it. |
Beta Was this translation helpful? Give feedback.
-
BIRT 4.14 runtime is not running with Tomcat server 9. does it require the setup of tomcat server 10? I performed the same steps as I did to set up BIRT 4.13 on tomcat server 9 but it failed to run even its home page of BIRT. |
Beta Was this translation helpful? Give feedback.
-
We are done here. |
Beta Was this translation helpful? Give feedback.
-
Hello reports which are built on an older version are not working on BIRT 4.14. do I need to change something on the server or on the reports which are previously built on BIRT 2.4? |
Beta Was this translation helpful? Give feedback.
-
It seems you want to confuse us... |
Beta Was this translation helpful? Give feedback.
-
@shahzad80, you are putting a lot of pressure on us. We all have to help you in our free time, and this has a limit.
I am closing this discussion because the original problem has been solved. |
Beta Was this translation helpful? Give feedback.
-
Hello expert
|
Beta Was this translation helpful? Give feedback.
-
This is my current configuration
Rocky Linux 8.8
Tomcat server 9
Viewer Version: 4.13.0
Engine Version: 4.13.0
JRE version: 11.0.19
I have received data from the MIS dept provided data of birt reporting which was handled by below configuration
Centos 6
Tomcat server 7
Viewer Version: 2.5.1
Engine Version: 2.5.1
java-1.8.0-openjdk.x86_64
Home page is displaying fine but view example link shows this error.
org.eclipse.birt.report.exception.ViewerException: Fatal error occurred when try to startup report engine.
at org.eclipse.birt.report.service.ReportEngineService.setEngineContext(ReportEngineService.java:328)
at org.eclipse.birt.report.service.BirtViewerReportService.setContext(BirtViewerReportService.java:1022)
at org.eclipse.birt.report.servlet.ViewerServlet.__getContext(ViewerServlet.java:148)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doGet(BirtSoapMessageDispatcherServlet.java:151)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:529)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:623)
at org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.service(BirtSoapMessageDispatcherServlet.java:122)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:209)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:673)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:390)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:829)
does this old configuration will not work with my new server
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions