karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (KARAF-273) java.lang.NullPointerException: Inflater has been closed
Date Tue, 25 Oct 2011 22:18:32 GMT

     [ https://issues.apache.org/jira/browse/KARAF-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jamie goodyear closed KARAF-273.
--------------------------------

    
> java.lang.NullPointerException: Inflater has been closed
> --------------------------------------------------------
>
>                 Key: KARAF-273
>                 URL: https://issues.apache.org/jira/browse/KARAF-273
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>         Environment: Windows XP SP3 and JDK 1.6.0_22.
>            Reporter: Bengt Rodehav
>            Assignee: Guillaume Nodet
>             Fix For: 2.1.2, 2.2.0
>
>
> When using pax-web version 0.7.3 (and also 0.8.0) you sometimes get a very strange exception.
Richard S Hall investigated this in FELIX-1032 and came to the conclusion that this is not
a Felix bug but acutally a JRE bug.
> \\
> \\
> It can be reproduced as follows: Install a vanilla Karaf 2.1.0. Then install the webconsole
(features:install webconsole). Click on the Configuration tab in the Webconsole that lists
the configurations, then click on the file install configuration and close it. At this point
I normally get the following stacktrace in the log:
> \\
> \\
> {code}
> java.lang.NullPointerException: Inflater has been closed
> 	at java.util.zip.Inflater.ensureOpen(Inflater.java:364)[:1.6.0_22]
> 	at java.util.zip.Inflater.getBytesWritten(Inflater.java:317)[:1.6.0_22]
> 	at java.util.zip.ZipFile$1.available(ZipFile.java:243)[:1.6.0_22]
> 	at org.apache.felix.framework.URLHandlersBundleURLConnection.connect(URLHandlersBundleURLConnection.java:126)[org.apache.felix.framework-3.0.2.jar:]
> 	at org.apache.felix.framework.URLHandlersBundleURLConnection.getInputStream(URLHandlersBundleURLConnection.java:135)[org.apache.felix.framework-3.0.2.jar:]
> 	at org.mortbay.resource.URLResource.exists(URLResource.java:101)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.ops4j.pax.web.service.jetty.internal.ResourceServlet.doGet(ResourceServlet.java:82)[37:org.ops4j.pax.web.pax-web-jetty:0.7.3]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)[32:org.apache.geronimo.specs.geronimo-servlet_2.5_spec:1.1.2]
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)[32:org.apache.geronimo.specs.geronimo-servlet_2.5_spec:1.1.2]
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.handle(HttpServiceServletHandler.java:64)[37:org.ops4j.pax.web.pax-web-jetty:0.7.3]
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.handle(HttpServiceContext.java:111)[37:org.ops4j.pax.web.pax-web-jetty:0.7.3]
> 	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:68)[37:org.ops4j.pax.web.pax-web-jetty:0.7.3]
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.Server.handle(Server.java:326)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)[33:org.apache.servicemix.bundles.jetty-bundle:6.1.22.2]
> {code}
> Strangely enough (since it's a JRE bug), it disappears if I go back to pax-web 0.7.2.
Also, if I configure Karaf 2.1.0 to use Equinox instead of Felix, the problem disappears.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message