groovy

Input stream not closed

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.8.7, 2.0.1
  • Fix Version/s: 1.8.8, 2.0.2, 2.1.0-beta-1
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows 7, GlassFish 3.1.2, Java 1.7.0_03
  • Number of attachments :
    0

Description

I am using groovy as a language for jasper reports in an enterprise application. When undeploying the application after having created one or more reports, I get a lot of warnings like the ones that follow (the stack traces are with Groovy 2.0.1; I get similar ones with Groovy 1.8.7).

[#|2012-08-20T12:20:36.250+0300|WARNING|glassfish3.1.2|javax.enterprise.system.core.classloading.com.sun.enterprise.loader|_ThreadID=78;_ThreadName=Thread-7;|Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.ASURLClassLoader$SentinelInputStream.<init>(ASURLClassLoader.java:1230)
at com.sun.enterprise.loader.ASURLClassLoader$InternalJarURLConnection.getInputStream(ASURLClassLoader.java:1338)
at java.net.URL.openStream(URL.java:1035)
at org.codehaus.groovy.control.SourceExtensionHandler.getRegisteredExtensions(SourceExtensionHandler.java:44)
at org.codehaus.groovy.control.CompilerConfiguration.getScriptExtensions(CompilerConfiguration.java:636)
at groovy.lang.GroovyClassLoader$1$1.run(GroovyClassLoader.java:76)
at groovy.lang.GroovyClassLoader$1$1.run(GroovyClassLoader.java:74)
at java.security.AccessController.doPrivileged(Native Method)
at groovy.lang.GroovyClassLoader$1.loadGroovySource(GroovyClassLoader.java:74)
at org.codehaus.groovy.control.ResolveVisitor.resolveToScript(ResolveVisitor.java:385)
at org.codehaus.groovy.control.ResolveVisitor.resolveToClass(ResolveVisitor.java:712)
at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:275)
at org.codehaus.groovy.control.ResolveVisitor.resolveFromModule(ResolveVisitor.java:648)
at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:275)
at org.codehaus.groovy.control.ResolveVisitor.resolve(ResolveVisitor.java:243)
at org.codehaus.groovy.control.ResolveVisitor.resolveOrFail(ResolveVisitor.java:227)
at org.codehaus.groovy.control.ResolveVisitor.resolveOrFail(ResolveVisitor.java:239)
at org.codehaus.groovy.control.ResolveVisitor.resolveOrFail(ResolveVisitor.java:235)
at org.codehaus.groovy.control.ResolveVisitor.visitClass(ResolveVisitor.java:1276)
at org.codehaus.groovy.control.ResolveVisitor.startResolving(ResolveVisitor.java:148)
at org.codehaus.groovy.control.CompilationUnit$9.call(CompilationUnit.java:621)
at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:900)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:564)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:513)
at net.sf.jasperreports.compilers.JRGroovyCompiler.compileUnits(JRGroovyCompiler.java:96)
at net.sf.jasperreports.engine.design.JRAbstractCompiler.compileReport(JRAbstractCompiler.java:188)
at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:212)
at net.sf.jasperreports.engine.JasperCompileManager.compileReport(JasperCompileManager.java:198)
...

[#|2012-08-20T11:05:34.432+0300|WARNING|glassfish3.1.2|javax.enterprise.system.core.classloading.com.sun.enterprise.loader|_ThreadID=73;_ThreadName=Thread-7;|Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace
java.lang.Throwable
at com.sun.enterprise.loader.ASURLClassLoader$SentinelInputStream.<init>(ASURLClassLoader.java:1230)
at com.sun.enterprise.loader.ASURLClassLoader$InternalJarURLConnection.getInputStream(ASURLClassLoader.java:1338)
at java.net.URL.openStream(URL.java:1035)
at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.registerExtensionModuleFromMetaInf(MetaClassRegistryImpl.java:163)
at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.registerClasspathModules(MetaClassRegistryImpl.java:153)
at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:108)
at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(MetaClassRegistryImpl.java:70)
at groovy.lang.GroovySystem.<clinit>(GroovySystem.java:33)
at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:162)
at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:192)
at Blank32A4_1345449884504_251660.$getStaticMetaClass(calculator_Blank32A4_1345449884504_251660)
at Blank32A4_1345449884504_251660.<init>(calculator_Blank32A4_1345449884504_251660)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at java.lang.Class.newInstance0(Class.java:372)
at java.lang.Class.newInstance(Class.java:325)
at net.sf.jasperreports.engine.design.JRAbstractJavaCompiler.loadEvaluator(JRAbstractJavaCompiler.java:98)
at net.sf.jasperreports.engine.design.JRAbstractCompiler.loadEvaluator(JRAbstractCompiler.java:320)
at net.sf.jasperreports.engine.JasperCompileManager.loadEvaluator(JasperCompileManager.java:237)
at net.sf.jasperreports.engine.fill.JRFillDataset.createCalculator(JRFillDataset.java:428)
at net.sf.jasperreports.engine.fill.JRBaseFiller.<init>(JRBaseFiller.java:363)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:77)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:87)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:57)
at net.sf.jasperreports.engine.fill.JRFiller.createFiller(JRFiller.java:142)
at net.sf.jasperreports.engine.fill.JRFiller.fillReport(JRFiller.java:52)
at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:417)
....

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Paul King added a comment -

As a workaround, if you are not using Groovy++ or supplying a user modified set of extensions, you can probably just hack/remove the "META-INF/services/org.codehaus.groovy.source.Extensions" file from the groovy jar. It contains the "groovy" extension but that is the default anyway.

Show
Paul King added a comment - As a workaround, if you are not using Groovy++ or supplying a user modified set of extensions, you can probably just hack/remove the "META-INF/services/org.codehaus.groovy.source.Extensions" file from the groovy jar. It contains the "groovy" extension but that is the default anyway.
Hide
Permalink
Christina Kaskoura added a comment -

Thank you for the suggestion. Unfortunately this is not very practical in my case since we're using Maven to manage all the project's dependencies so this would mean having to manually install the "patched" jar on every machine where we need to build to project, which is a bit of a hassle...

Show
Christina Kaskoura added a comment - Thank you for the suggestion. Unfortunately this is not very practical in my case since we're using Maven to manage all the project's dependencies so this would mean having to manually install the "patched" jar on every machine where we need to build to project, which is a bit of a hassle...
Hide
Permalink
Paul King added a comment -

Sure, the suggestion wasn't meant as a long-term approach - more as added feedback that if we fixed the stream closing that the problem would go away for you. In any case, I have applied a fix which should be in the snapshots repos shortly once the CI server gets to do its thing - so perhaps that is more worthy of testing if temporarily pointing to the codehaus snapshots repo is viable for you. Otherwise, it will hopefully be there when we next do a release (no finalised schedule at this point).

Show
Paul King added a comment - Sure, the suggestion wasn't meant as a long-term approach - more as added feedback that if we fixed the stream closing that the problem would go away for you. In any case, I have applied a fix which should be in the snapshots repos shortly once the CI server gets to do its thing - so perhaps that is more worthy of testing if temporarily pointing to the codehaus snapshots repo is viable for you. Otherwise, it will hopefully be there when we next do a release (no finalised schedule at this point).
Hide
Permalink
Christina Kaskoura added a comment -

Thanks a lot for your feedback. I tried the workaround you proposed and I no longer get the first stack trace above, but I am still getting the second one. I might also give the snapshot a try later on if we don't manage to find any other alternative.

Show
Christina Kaskoura added a comment - Thanks a lot for your feedback. I tried the workaround you proposed and I no longer get the first stack trace above, but I am still getting the second one. I might also give the snapshot a try later on if we don't manage to find any other alternative.
Hide
Permalink
Paul King added a comment -

Yes, I couldn't think of a quick workaround for the second case but it shouldn't occur for the 1.8.7 jar. In any case, if you get a chance to try the 2.0.2 or 2.1.0 snapshot jars (as of a few hours ago) they should have both problems fixed.

Show
Paul King added a comment - Yes, I couldn't think of a quick workaround for the second case but it shouldn't occur for the 1.8.7 jar. In any case, if you get a chance to try the 2.0.2 or 2.1.0 snapshot jars (as of a few hours ago) they should have both problems fixed.
Hide
Permalink
Paul King added a comment -

I think it should be fixed now but please provide feedback if you find any issues. Thanks for reporting the issue.

Show
Paul King added a comment - I think it should be fixed now but please provide feedback if you find any issues. Thanks for reporting the issue.

People

  • Assignee:
    Paul King
    Reporter:
    Christina Kaskoura
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: