You are not logged in.
Hi ReportServer
When using docker image reportserver community edition, latest version from dockerhub (as of 2019-10-18), i cannot execute any reports from schedulers.
I tried with the enterprise edition docker image, and it works fine.
Can you help ?
Here is the stacktrace triggered when a report is executed from a scheduler
Error-Details: net.datenwerke.scheduler.service.scheduler.exceptions.JobExecutionException: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Guice provision errors:
1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot access scoped object. Either we are not currently inside an HTTP Servlet request, or you may have forgotten to apply com.google.inject.servlet.GuiceFilter as a servlet filter for this request.
at net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer.class(SaikuSessionContainer.java:15)
while locating net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer
for parameter 5 at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.<init>(SaikuReportEngine.java:63)
while locating net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine
1 error
at net.datenwerke.rs.scheduler.service.scheduler.jobs.report.ReportExecuteJob.doExecute(ReportExecuteJob.java:140)
at net.datenwerke.scheduler.service.scheduler.entities.AbstractJob.execute(AbstractJob.java:184)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeJob(SchedulerTask.java:646)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:208)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:103)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Guice provision errors:
1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot access scoped object. Either we are not currently inside an HTTP Servlet request, or you may have forgotten to apply com.google.inject.servlet.GuiceFilter as a servlet filter for this request.
at net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer.class(SaikuSessionContainer.java:15)
while locating net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer
for parameter 5 at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.<init>(SaikuReportEngine.java:63)
while locating net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine
1 error
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:218)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:119)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:106)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:101)
at net.datenwerke.rs.scheduler.service.scheduler.jobs.report.ReportExecuteJob.doExecute(ReportExecuteJob.java:135)
... 9 more
Caused by: com.google.inject.ProvisionException: Guice provision errors:
1) Error in custom provider, com.google.inject.OutOfScopeException: Cannot access scoped object. Either we are not currently inside an HTTP Servlet request, or you may have forgotten to apply com.google.inject.servlet.GuiceFilter as a servlet filter for this request.
at net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer.class(SaikuSessionContainer.java:15)
while locating net.datenwerke.rs.saiku.service.saiku.SaikuSessionContainer
for parameter 5 at net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine.<init>(SaikuReportEngine.java:63)
while locating net.datenwerke.rs.saiku.service.saiku.reportengine.SaikuReportEngine
1 error
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:177)
... 13 more
Caused by: com.google.inject.OutOfScopeException: Cannot access scoped object. Either we are not currently inside an HTTP Servlet request, or you may have forgotten to apply com.google.inject.servlet.GuiceFilter as a servlet filter for this request.
at com.google.inject.servlet.GuiceFilter.getContext(GuiceFilter.java:135)
at com.google.inject.servlet.GuiceFilter.getRequest(GuiceFilter.java:121)
at com.google.inject.servlet.ServletScopes$2$1.get(ServletScopes.java:114)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38)
at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:84)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.InjectorImpl$4$1.call(InjectorImpl.java:978)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:974)
... 15 more
Last edited by eaydsv (2019-10-18 08:12:30)
Offline
Hi eaydsv,
this is a known issue with the current version: RS-3732. We are releasing a patch this week or in the beginning of next week at the latest so it should be available by the end of next week in the docker version.
-> As the issue is not deterministic, the fact that sometimes it works fine doesn't mean that the version is different : the bug is in both places. We are releasing a patch in order to fix this.
Regards,
Eduardo
Offline
Hi eaydsv,
we released the 3.1.0-6011 patch today which includes this bugfix. You can download the patch from our homepage. The bitnami builds including the docker version should be finished by next week.
Regards,
Eduardo
Offline
Hi eaydsv,
we released the 3.1.0-6015 patch today which includes a bugfix of Apache POI 4. You can download the patch from our homepage. The bitnami builds including the docker version should be finished by next week.
Regards,
Eduardo
Offline
Hi easydsv,
the 3.1.0-6015 docker images are ready.
Regards,
Eduardo
Offline
thanks - i confirm the issue of scheduler is now fixed
Offline