javydreamercsw Posted May 12, 2007 Share Posted May 12, 2007 Here's the server stack trace after a report is ran using the scheduler (either run now or scheduling a job):Code:10:57:33,367 ERROR ReportExecutionJob,JasperServerScheduler_Worker-1:186 - org.acegisecurity.AccessDeniedException: Access is deniedorg.acegisecurity.AccessDeniedException: Access is denied at org.acegisecurity.vote.AffirmativeBased.decide(AffirmativeBased.java:68) at org.acegisecurity.intercept.AbstractSecurityInterceptor.beforeInvocation(AbstractSecurityInterceptor.java:275) at org.acegisecurity.intercept.method.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:63) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210) at $Proxy2.getResource(Unknown Source) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.saveToRepository(ReportExecutionJob.java:441) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.sendToDestinations(ReportExecutionJob.java:295) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.execute(ReportExecutionJob.java:138) at org.quartz.core.JobRunShell.run(JobRunShell.java:195) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) This might be related to:http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=215&func=view&id=25141&catid=10Post edited by: javydreamercsw, at: 2007/05/11 17:02 Link to comment Share on other sites More sharing options...
lovetide Posted May 14, 2007 Share Posted May 14, 2007 I have encountered the same error after upgrade 1.2.0 to 1.2.1, see here:http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=215&func=view&id=23723&catid=10 Link to comment Share on other sites More sharing options...
lucianc Posted May 14, 2007 Share Posted May 14, 2007 The exception stacktrace seems to indicate that the user who created the report job does not have write permission on the folder where the job results are to be saved. Could you confirm that this is the case? Regards,Lucian Link to comment Share on other sites More sharing options...
javydreamercsw Posted May 14, 2007 Author Share Posted May 14, 2007 Haven't thought of that. But sadly it's not the case. If you mean by the user the user that schedules the job it's part of the ROLE_ADMIN and in top of that has explicit permissions in the target folder (Administer). Post edited by: javydreamercsw, at: 2007/05/14 12:14 Link to comment Share on other sites More sharing options...
lucianc Posted May 14, 2007 Share Posted May 14, 2007 I'm not able to replicate this issue. Do you have a step-by-step scenario on how to do it? Link to comment Share on other sites More sharing options...
javydreamercsw Posted May 14, 2007 Author Share Posted May 14, 2007 I did nothing special. Basically I have a target folder with the following permissions: ROLE_USER- ReadROLE_ADMIN - Administer, ROLE_ANONYMOUS- No Access, a report with the same permissions and attempted a scheduled report or a run in background link. Both with same results. If you need more specific data just let me know. I can provide the jasperserver db contents if you need them. Link to comment Share on other sites More sharing options...
lucianc Posted May 14, 2007 Share Posted May 14, 2007 A DB dump would hopefully allow us to replicate this. Upload it here or send it to lucianc@users.sourceforge.net. Link to comment Share on other sites More sharing options...
javydreamercsw Posted May 14, 2007 Author Share Posted May 14, 2007 Check your email... Link to comment Share on other sites More sharing options...
lucianc Posted May 15, 2007 Share Posted May 15, 2007 We've identified the cause. This bug manifests when you set the "Overwrite Files" flag for a report job. The bug has been fixed after 1.2.1 was released. Workarounds:If you don't actually need to set "Overwrite Files", don't.Apply the attached patch either by unpacking it into WEB-INF/classes or by copying it to WEB-INF/lib.[/ul] Regards,Lucian [file name=0jasperserver_api_metadata_impl_1.jar size=16378]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/0jasperserver_api_metadata_impl_1.jar[/file] Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now