runing reports asynchronously (reportExecutions Service)

Hi there,

Just a quick question please. In version 6.2 of jasper server I am testing the async methods of the reportExecutions Service using Jmeter.

I have noticed that I can successfully do the following

Test One result Success

  • Login as jasperadmin
  • Run report asynchronously (save returned request and export ids in variables)
  • get staus using the request id
  • Wait for the report status to equal "Ready"
  • get the output
  • save to disk
  • logout

Test Two Result: fails

  • Login as jasperadmin
  • Run report asynchronously (save returned request and export ids in variables)
  • logout
  • Login as jasperadmin
  • wait 10 seconds
  • Get status using the same request ID (http: resource not found 404)
  • get the output
  • save to disk
  • logout

Test Three Result: Success

  • Login as jasperadmin
  • Run report asynchronously (save returned request and export ids in variables)
  • Login as jasperadmin
  • wait 10 seconds
  • Get status using the same request ID
  • Wait for the report status to equal "Ready"
  • get the output
  • save to disk
  • logout

Summary

From my observations is appears as soon as a logout command is issued the request ID is lost
and so therefore it is not possible to use the async reportExecutions services, as you always have to
remain logged in, which defeats the whole purpose of running a report asynchronously

Can someone please let me know if I am missing something, I can supply the JMeter scripts if required

clive.haynes_1's picture
Joined: Sep 11 2013 - 6:40am
Last seen: 1 year 11 months ago

Its ok problem solved, Logging out frees resources on the server, resources being the report which is a resource.

clive.haynes_1 - 7 years 4 months ago

i had the same problem, use  cookies it will resolve the problem.

 

wailinho20 - 6 years 12 months ago

0 Answers:

No answers yet
Feedback
randomness