Jump to content
We've recently updated our Privacy Statement, available here ×

s.facchetti

Members
  • Posts

    2
  • Joined

  • Last visited

s.facchetti's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Hi, we've a VM with 32 GB RAM, 4 Core and 200 GB free space. Ram minimum requirements is refered to SO or JRS? Changing Xmx from 2048M to 16384M has resolved the issue. Best regards, Stefano.
  2. Hi, I'm using JasperReport Server v7.2 on Ubuntu 18.04.3 LTS under Tomcat 9.0.24 and OpneJk 1.8.0_312 JVM Arguments: -Xms1024M -Xmx2048M -XX:+UseParallelGC With REST API I generate many small reports (up to 10 pages). I execute one API call a time, so Jasper generates only one report a time. As you can see in attached image (image 1), the used heap space increases until it reaches saturation (after 220/230 reports). It seems that Jasper keeps in memory data of the reports produced and the GC cannot free it. Even interrupting the report generation process, the heap memory is released only after a long time (1 hour after the error/interruption), see image 2. Errors that I cand find in log: ERROR SecureExceptionHandlerImpl,pool-27-thread-1:116 - Java heap space ERROR SqlExceptionHelper,pool-27-thread-1:131 - Ran out of memory retrieving query results. How can I avoid this situation? Any suggestion? Thanks, Stefano.
×
×
  • Create New...