rvypandey

Hi there, Continuing on the thread - , but creating a new one because this would require a different implementation. --- So I see that within JasperServer UI, when a scheduled report fails, it publishes message under the Message section. PFA image - Is it possible to extend this implementation to also publish these failure messages to a custom queue? The requirement is to intercept these messages and have a custom functionality on top of this in a different application. Thanks, Ravi Pandey

Thanks for your response @ddonofr, but this I've already tried: - get list of all jobs - http://<host>:<port>/jasperserver[-pro]/rest_v2/jobs?<arguments> - get each jobs details - http://<host>:<port>/jasperserver[-pro]/rest_v2/jobs/<jobID> - get each jobs state - http://<host>:<port>/jasperserver[-pro]/rest_v2/jobs/<jobID>/state But this only tells us what happened with the job, and not whether report was generated when this job ran or not. ---- As a POC, I altered the code to throw error (created custom function) and used that in jrxml. The error is successfully thrown for the report (when run via scheduler), and the report never generates. Error - But the job still is in NORMAL state - I want to know that when the job ran, was the report generated or was there any error? Thanks, Ravi Pandey

Hi there, I'm looking for a solution where I'm creating schedules in JasperServer UI, and I need to poll (on a scheduled basis) whether job was successful - report generated, or job failed. In case of job failed, I'm recording the instance via a NodeJS app into my DB, and providing a capability to re-trigger these failed jobs. I understand that there is already a support for restarting failed jobs - , but my requirement is also to track these separately. I've tried reportsExecution Service and it does not return any content - 204. Is there a way to achieve this? Thanks, Ravi Pandey

I'm also stuck at this. Any help would be appreciated.

Worked out the issue, the directory has to be either / or actual directory created inside the container (under blob), it cannot be just the container name - I was passing container name. After creating a new directory under container (named test), and passing it in directory field worked. Also tested by just passing / (which means container level directory.

Worked out the issue, the directory has to be either / or actual directory created inside the container (under blob), it cannot be just the container name - I was passing container name. After creating a new directory under container (named test), and passing it in directory field worked. Also tested by just passing / (which means container level directory.

Unable to create Azure blob SFTP connection from schedules ( > Output Options), giving error - Connection failed The same works on terminal and even file push is successful. Version - JasperServer 6.20.5