[jira] [Commented] (FELIX-5975) URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
[
https://issues.apache.org/jira/browse/FELIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669366#comment-16669366
]
Karl Pauls commented on FELIX-5975:
---
Can you use a patched framework?
> URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
> --
>
> Key: FELIX-5975
> URL: https://issues.apache.org/jira/browse/FELIX-5975
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: framework-4.6.1
> Environment: AIX server box, Tomcat 8.0.53
>Reporter: Julien Jalageas
>Priority: Blocker
> Attachments: stacktrace.txt
>
>
> Hi,
> I am running into a blocking issue since I've upgraded from Tomcat 7.0.73 to
> Tomcat 8.0.53, SOAP based web services are failing with the following error:
> java.lang.IllegalStateException: *Stream handler unavailable due to: null*
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:359)
> Using a remote debugger, I was able to find that the real exception is
> actually a Null Pointer Exception thrown from
> *URLHandlersStreamHandlerProxy*.java, line 351:
> return (URLConnection) *OPEN_CONNECTION_PROXY*.invoke(svc, new Object[]\{url,
> proxy});
> where *OPEN_CONNECTION_PROXY* is null (I've attached the full stacktrace).
> Is there a fix available?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (FELIX-5975) URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
[
https://issues.apache.org/jira/browse/FELIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669319#comment-16669319
]
Karl Pauls edited comment on FELIX-5975 at 10/30/18 8:57 PM:
-
Are you really using 4.6.1?
That said, I'm not sure a newer version would help - I guess the question is
why OPEN_CONNECTION_PROXY is null. It should only be null if you run on a very
old java version. Can you set a breakpoint in the static initalizer where we
look up that method and see why it ends-up being nulll?
was (Author: karlpauls):
Are you really using 4.6.1?
> URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
> --
>
> Key: FELIX-5975
> URL: https://issues.apache.org/jira/browse/FELIX-5975
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: framework-4.6.1
> Environment: AIX server box, Tomcat 8.0.53
>Reporter: Julien Jalageas
>Priority: Blocker
> Attachments: stacktrace.txt
>
>
> Hi,
> I am running into a blocking issue since I've upgraded from Tomcat 7.0.73 to
> Tomcat 8.0.53, SOAP based web services are failing with the following error:
> java.lang.IllegalStateException: *Stream handler unavailable due to: null*
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:359)
> Using a remote debugger, I was able to find that the real exception is
> actually a Null Pointer Exception thrown from
> *URLHandlersStreamHandlerProxy*.java, line 351:
> return (URLConnection) *OPEN_CONNECTION_PROXY*.invoke(svc, new Object[]\{url,
> proxy});
> where *OPEN_CONNECTION_PROXY* is null (I've attached the full stacktrace).
> Is there a fix available?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FELIX-5975) URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
[
https://issues.apache.org/jira/browse/FELIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669319#comment-16669319
]
Karl Pauls commented on FELIX-5975:
---
Are you really using 4.6.1?
> URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
> --
>
> Key: FELIX-5975
> URL: https://issues.apache.org/jira/browse/FELIX-5975
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: framework-4.6.1
> Environment: AIX server box, Tomcat 8.0.53
>Reporter: Julien Jalageas
>Priority: Blocker
> Attachments: stacktrace.txt
>
>
> Hi,
> I am running into a blocking issue since I've upgraded from Tomcat 7.0.73 to
> Tomcat 8.0.53, SOAP based web services are failing with the following error:
> java.lang.IllegalStateException: *Stream handler unavailable due to: null*
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:359)
> Using a remote debugger, I was able to find that the real exception is
> actually a Null Pointer Exception thrown from
> *URLHandlersStreamHandlerProxy*.java, line 351:
> return (URLConnection) *OPEN_CONNECTION_PROXY*.invoke(svc, new Object[]\{url,
> proxy});
> where *OPEN_CONNECTION_PROXY* is null (I've attached the full stacktrace).
> Is there a fix available?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FELIX-5975) URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
Julien Jalageas created FELIX-5975:
--
Summary: URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
Key: FELIX-5975
URL: https://issues.apache.org/jira/browse/FELIX-5975
Project: Felix
Issue Type: Bug
Components: Framework
Affects Versions: framework-4.6.1
Environment: AIX server box, Tomcat 8.0.53
Reporter: Julien Jalageas
Attachments: stacktrace.txt
Hi,
I am running into a blocking issue since I've upgraded from Tomcat 7.0.73 to
Tomcat 8.0.53, SOAP based web services are failing with the following error:
java.lang.IllegalStateException: *Stream handler unavailable due to: null*
org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:359)
Using a remote debugger, I was able to find that the real exception is actually
a Null Pointer Exception thrown from *URLHandlersStreamHandlerProxy*.java, line
351:
return (URLConnection) *OPEN_CONNECTION_PROXY*.invoke(svc, new Object[]\{url,
proxy});
where *OPEN_CONNECTION_PROXY* is null (I've attached the full stacktrace).
Is there a fix available?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FELIX-5974) Prototype scope references are not released on deactivation
[ https://issues.apache.org/jira/browse/FELIX-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669018#comment-16669018 ] Timothy Ward commented on FELIX-5974: - I've updated the PR - hopefully this will now release the objects from the MultiplePrototypeRefPair as well as releasing the service instance. > Prototype scope references are not released on deactivation > --- > > Key: FELIX-5974 > URL: https://issues.apache.org/jira/browse/FELIX-5974 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) >Affects Versions: scr-2.1.12 >Reporter: Timothy Ward >Priority: Major > Fix For: scr-2.1.14 > > > Having read the stack overflow question on [Stack > Overflow|https://stackoverflow.com/questions/52839641/osgi-ds-prototype-reference-not-released] > I was pretty certain that the user must be doing something wrong, but in > fact it seems as though SCR does a bad job of releasing Prototype scoped > references when a component is disposed. > I looked into the code, and it seems that there are a lot of conflicting > locations where prototype scope services are obtained and released. I propose > tidying this up so that the ComponentServiceObjects is *always* used > internally regardless of whether it is injected or not. This encapsulates all > the access in a single location so it is less likely that the objects will > leak. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Regarding compiling Apache Felix Deployment Admin from sources
Hi! The main issue is that Eclipse Kura 3.2.0 (the OSGi runtime we're using) came with that particular version, so to retain as much compatibility, behavior wise, as possible, I decided on choosing that particular version. Meanwhile, these are the currently installed bundles that come with eclipse kura by default. osgi> lb > START LEVEL 6 >ID|State |Level|Name > 0|Active |0|OSGi System Bundle (3.11.1.v20160708-1632) > 1|Active |1|Configuration Admin (1.1.200.v20160324-1850) > 2|Resolved |1|System extension fragment for 'sun.misc' (1.0.200) > 3|Active |1|Common Eclipse Runtime (3.8.0.v20160509-1230) > 4|Active |1|Extension Registry Support (3.6.100.v20160223-2218) > 5|Active |1|Http Service Registry Extensions > (1.1.400.v20150715-1528) > 6|Active |1|Console plug-in (1.1.200.v20150929-1405) > 7|Active |1|Declarative Services (1.4.400.v20160226-2036) > 8|Active |1|Event Admin (1.3.200.v20160324-1850) > 9|Active |1|IO Connector Service (1.1.100.v20150430-1834) >10|Active |1|Meta Type (1.4.200.v20160324-1850) >11|Active |1|Equinox Util Bundle (1.0.500.v20130404-1337) >12|Active |2|OSGi Release 4.2.0 Services > (3.5.100.v20160504-1419) >13|Active |2|OSGi Release 4.2.0 Utility Classes > (3.3.100.v20150423-1351) >14|Active |5|Apache Felix Gogo Command (0.10.0.v201209301215) >15|Active |5|Apache Felix Gogo Runtime (0.10.0.v201209301036) >16|Active |5|Apache Felix Gogo Shell (0.10.0.v201212101605) >17|Active |3|KnowHowLab OSGi MonitorAdmin (1.0.2) >18|Active |3|Apache Felix Dependency Manager (3.0.0) >19|Installed |3|Apache Felix Deployment Admin (0.9.5) >20|Active |3|osgi.cmpn (4.3.0.20022214) >21|Active |3|Wire Admin Service (1.0.600.v20150715-1528) >22|Active |5|Jetty Http Service (3.4.0.v20170503-2025) >23|Active |5|Http Services Servlet (1.4.0.v20170524-1452) >24|Active |5|Jetty :: Continuation (9.4.7.v20170914) >25|Active |5|Jetty :: Http Utility (9.4.7.v20170914) >26|Active |5|Jetty :: IO Utility (9.4.7.v20170914) >27|Active |5|Jetty :: Security (9.4.7.v20170914) >28|Active |5|Jetty :: Server Core (9.4.7.v20170914) >29|Active |5|Jetty :: Servlet Handling (9.4.7.v20170914) >30|Active |5|Jetty :: Utilities (9.4.7.v20170914) >31|Active |5|Servlet API Bundle (3.1.0.v201410161800) >32|Active |3|Apache Commons FileUpload (1.3.2) >33|Active |3|Commons IO (2.4.0) >34|Active |3|slf4j-api (1.7.21) >35|Active |3|jcl-over-slf4j (1.7.21) >36|Resolved |3|slf4j-log4j12 (1.7.21) >37|Resolved |3|Apache Log4j (1.2.17) >38|Resolved |3|Kura wrapper for Apache log4j extras (1.1.100) >39|Resolved |5|minimal-json (0.9.4) >40|Active |3|HSQLDB (2.3.0) >41|Active |3|H2 Database Engine (1.4.192) >42|Resolved |3|Native libraries for 'com.codeminders.hidapi' on > ARM 6 HF (1.1.300) >43|Active |3|Java API for working with Human Interface USB > Devices (HID) (1.1.300) >44|Resolved |3|Comm (Incubation) (1.2.300) >45|Active |3|Comm (Incubation) (1.2.300) >46|Active |4|Apache Commons Lang (3.4.0) >47|Active |4|usb4java (1.2.300) >48|Active |4|usb4java-javax (1.2.300) >49|Resolved |3|jdk.dio.armv6hf (1.0.300) >50|Resolved |3|jdk.dio (1.0.300) >51|Resolved |3|Native libraries for 'tinyb' on ARM 6 HF (1.0.100) >52|Active |3|Tiny Bluetooth LE Library (1.0.100) >53|Active |3|Apache Commons Net (3.1.0.v201205071737) >54|Resolved |5|Apache Commons Exec (1.3.0) >55|Active |3|jersey-min (2.22.2) >56|Active |4|OSGi JAX-RS Connector (5.3.1.201602281253) >57|Active |4|JAX-RS Gson Provider (2.3.0.201602281253) >58|Active |4|OSGi - JAX-RS Security Provider > (2.2.0.201602281253) >59|Resolved |3|Gson: Google Json Library for Java > (2.7.0.v20170129-0911) >60|Active |3|org.eclipse.kura.api (1.4.0) >61|Active |4|org.eclipse.kura.core (1.0.300) >62|Active |4|org.eclipse.kura.core.certificates (1.0.300) >63|Active |4|org.eclipse.kura.core.cloud (1.1.200) >64|Active |4|org.eclipse.kura.core.comm (1.0.300) >65|Active |4|org.eclipse.kura.core.configuration (2.0.0) >66|Active |3|org.eclipse.kura.core.crypto (1.0.300) >67|Active |4|org.eclipse.kura.core.deployment (1.1.300) >68|Active |4|org.eclipse.kura.core.log (1.0.300) >69|Active |4|org.eclipse.kura.core.net (1.0.300) >70|Active |4|org.eclipse.kura.core.status (1.0.300) >71|Active
