[
https://issues.apache.org/jira/browse/FELIX-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Zdila updated FELIX-1032:
--------------------------------
Attachment: hack.patch
I am forced to use hacked version of the framework (1.8.0). See the attached
patch. If m_is.available() throws NPE, it is necessary to call "m_is =
m_targetModule.getInputStream(..." again. Sometimes it is necessary to retry
multiple times, but mostly only once.
Could it be really possible to call Inflater.ensureOpen method on the Inflater
that has been akready finalized? Because that's what I actually observe. This
is very frustrating.
Please provide me some hints what tests should I try to run. Thanks in advance.
> NPE on URL#openStream()
> -----------------------
>
> Key: FELIX-1032
> URL: https://issues.apache.org/jira/browse/FELIX-1032
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-1.4.1, felix-1.6.0, felix-1.6.1
> Environment: Linux bono 2.6.28-6-generic #17-Ubuntu SMP Fri Jan 30
> 15:34:36 UTC 2009 i686 GNU/Linux
> java version "1.6.0_13"
> Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
> Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
> Reporter: Martin Zdila
> Priority: Critical
> Attachments: hack.patch
>
>
> Note that also affected is felix-1.6.0 (it is not in the list).
> I am often getting NPE with the following code:
> new URL("bundle://66.0:0/somewhere/my.resource" /* or any other bundle:// URL
> */).openStream();
> java.lang.NullPointerException
> at java.util.zip.Inflater.ensureOpen(Inflater.java:336)
> at java.util.zip.Inflater.getBytesWritten(Inflater.java:296)
> at java.util.zip.ZipFile$1.available(ZipFile.java:243)
> at
> org.apache.felix.framework.URLHandlersBundleURLConnection.connect(URLHandlersBundleURLConnection.java:125)
> at
> org.apache.felix.framework.URLHandlersBundleURLConnection.getInputStream(URLHandlersBundleURLConnection.java:134)
> at java.net.URL.openStream(URL.java:1009)
> It is not allways reproducible. The first call causes the NPE and the second
> call with the same URL string goes without problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
