Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InputStream never closed when using JasperReports 3.x [SPR-7048] #11709

Closed
spring-projects-issues opened this issue Mar 29, 2010 · 1 comment
Closed
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Leandro Borges opened SPR-7048 and commented

At org.springframework.web.servlet.view.jasperreports.AbstractJasperReportsView the method:

"protected final JasperReport loadReport(Resource resource)"

should close the InputStream (from resource.getInputStream()) after load the JasperReport.
This cause a warning:
"WARNING: Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace"
at glassfish after redeploy.


Affects: 2.5.6

Referenced from: commits fba8bcc

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

This seems to be an issue with the JasperReports 3.x generation only. With JasperReports 2.0.5 (which is still the version that we officially support), the JRLoader class did close a given InputStream itself.

So to some degree, this is about general support for JasperReports 3.x in Spring. I'll try to roll that into Spring 3.0.2 still. Let me know if you are indeed using that version of JasperReports...

Juergen

@spring-projects-issues spring-projects-issues added type: bug A general bug in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0.2 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants