This content has been marked as final. Show 1 reply
I've the same issue. I'm my case, I think it is produced by the use of jasperreports, but in others threads that I've read, they say that may be cause for the use of @Scheduller. Sorry but I can't find a solution yet. I've found one, I tell you.