Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Intelligence (Analytics)
Error daylight saving time in Birt
davidsinge
Since the daylight saving time, all dates were treated with Birt are showing a difference of one hour when compared to the server datetime. To fix the problem of the day differences, I modified the variables from date type to string type. I had changed more than 50% of my reports to correct this problem. But the problem still occurs respecting to hours, causing all my reports to show time containing the hours with one hour difference.
The problem occurs because the daylight saving time in Brazil changes across the years; it is not fixed.
Someone who had this problem could help me?
Sorry for the deficiencies in English.
Find more posts tagged with
Comments
mwilliams
Hi davidsinge,
What version of BIRT are you using? I believe there had briefly been a DST issue with an older version of BIRT.
davidsinge
mwilliams,
Thanks for the help, but I am still with some doubts, now to update the version of Birt.
Once you update files, to run the report, the following is displayed below:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet execution threw an exception
org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.IllegalAccessError: tried to access method org.eclipse.birt.report.model.metadata.ExtensionManager.initialize()V from class org.eclipse.birt.report.model.api.impl.DesignEngineImpl
org.eclipse.birt.report.model.api.impl.DesignEngineImpl.initialize(DesignEngineImpl.java:106)
org.eclipse.birt.report.model.api.impl.DesignEngineImpl.newSessionHandle(DesignEngineImpl.java:149)
org.eclipse.birt.report.model.api.DesignEngine.newSessionHandle(DesignEngine.java:108)
org.eclipse.birt.report.engine.parser.ReportParser.getDesignHandle(ReportParser.java:143)
org.eclipse.birt.report.engine.api.impl.ReportEngineHelper.openReportDesign(ReportEngineHelper.java:251)
org.eclipse.birt.report.engine.api.impl.ReportEngine.openReportDesign(ReportEngine.java:550)
org.eclipse.birt.report.service.ReportEngineService.openReportDesign(ReportEngineService.java:390)
org.eclipse.birt.report.utility.BirtUtility.getRunnableFromDesignFile(BirtUtility.java:595)
org.eclipse.birt.report.context.ViewerAttributeBean.getDesignHandle(ViewerAttributeBean.java:643)
org.eclipse.birt.report.context.ViewerAttributeBean.__init(ViewerAttributeBean.java:228)
org.eclipse.birt.report.context.BaseAttributeBean.init(BaseAttributeBean.java:233)
org.eclipse.birt.report.context.ViewerAttributeBean.<init>(ViewerAttributeBean.java:113)
org.eclipse.birt.report.context.BirtContext.__init(BirtContext.java:44)
org.eclipse.birt.report.context.BaseContext.<init>(BaseContext.java:69)
org.eclipse.birt.report.context.BirtContext.<init>(BirtContext.java:30)
org.eclipse.birt.report.servlet.ViewerServlet.__getContext(ViewerServlet.java:150)
org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.doGet(BirtSoapMessageDispatcherServlet.java:137)
javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.eclipse.birt.report.servlet.BirtSoapMessageDispatcherServlet.service(BirtSoapMessageDispatcherServlet.java:112)
org.eclipse.birt.report.filter.ViewerFilter.doFilter(ViewerFilter.java:68)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
note The full stack trace of the root cause is available in the JBossWeb/2.0.0.GA logs.
JBossWeb/2.0.0.GA
I wish you could help me find where the problem is because the engine design is ok.
What could be the problem?
mwilliams
davidsinge,
Could you include the entire stack trace? Is this error only happening in the deployed viewer? Or do you get errors in the designer as well?