RE: Error with UPnP Base driver
Ok thanks a lot Stefano I ll try this. Kind regards, Charbel Date: Fri, 11 Jun 2010 12:09:25 +0200 From: le...@apache.org Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org Dear Charbel, Sorry for the late answer, I really believe that is a problem related from the wiring. Actually, the problem is not caused by bundle 20 and 22 but to others bundle on your configuration. If you want to find the source of the problem you should inspect the import/export tree for the packages org.xml.sax and org.xml.sax Nevertheless, I believe that easier for you to force the wiring of the org.w3c.dom and org.xml.sax packages of the UPnP Base Driver to the framework bundle. If you want to try this solution, you have to: 1 - download the UPnP bundle sources 2 - modify the pom.xml by replacing the content of the Import-Package tag org.osgi.*, javax.xml.parsers;bundle-symbolic-name=org.apache.felix.framework, org.w3c.dom;bundle-symbolic-name=org.apache.felix.framework, org.xml.sax;bundle-symbolic-name=org.apache.felix.framework 3 - package the bundle with maven, by executing mvn install 4 - replace the UPnP Base Driver bundle with the one just created, that is located inside target folder As additional note, you should be aware that inspect command shows only the actual wiring of the bundle which may be different from the content of the Import/Export-Pacakge headers of the bundle you are inspecting ( Richard would you mind to correct me if I'm wrong?) Ciao, Stefano Kismet Lenzi On 02/06/2010 11.18, charbel el_kaed wrote: Hi Stefano, I inspected the packages and this is what I found. (The inspection result are below) Bundle 20 ONLY imports org.w3c.dom and org.xml.sax while Bundle 22 imports and exports org.xml.sax In your previous reply you mentioned the correct configuration as: I think that the correct configuration of bundle 20 and 22 are: - bundle 20 and 22 import and export the packages: org.w3c.dom and org.xml.sax - bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax So I am not sure if it is correct. I am really new to this. I am looking at the OSGi Service Platform Release 4 core, Version 4.2 page 52 - inspect package c 20 org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] exports packages: -- org.jdom; version=0.0.0 org.jdom.adapters; version=0.0.0 org.jdom.filter; version=0.0.0 org.jdom.output; version=0.0.0 org.jdom.output.sax; version=0.0.0 org.jdom.output.stax; version=0.0.0 org.jdom.input.stax; version=0.0.0 - inspect package r 20 org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] imports packages: -- javax.xml.stream; version=1.6.0 - org.apache.felix.framework [0] org.xml.sax.ext; version=1.6.0 - org.apache.felix.framework [0] org.w3c.dom; version=2.0.0 - org.soa4d.forge.osgi.xml.dom.l2.core.api.osgi [19] org.xml.sax; version=2.0.2 - org.soa4d.forge.osgi.xml.sax2.api.osgi [21] org.xml.sax.helpers; version=2.0.2 - org.soa4d.forge.osgi.xml.sax.over.pull.bri dge.osgi [22] org.xquark.serialize; version=1.1.1 - org.soa4d.forge.osgi.xml.xquare.serializi ng [23] # - inspect package c 22 org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] exports packages: - org.xml.sax.ext; version=2.0.2 org.xml.sax.helpers; version=2.0.2 - inspect package r 22 org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] imports packages: - org.xmlpull.v1; version=1.1.2 - org.soa4d.forge.osgi.xml.kxml.pullparser.osgi [15] org.xml.sax; version=2.0.2 - org.soa4d.forge.osgi.xml.sax2.api.osgi [21] Kind regards, Charbel. Date: Tue, 1 Jun 2010 14:54:41 +0200 From: le...@apache.org Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org On 01/06/2010 1.58, charbel el_kaed wrote: Hi Stefano, Thanks for your reply. I can't actually touch those bundles. Is there another way to do so ? Have you checked if the hypothesis regarding the import/export headers of bundle 20 and 22 are correct? If they aren't then the source of the problem is somewhere else. If the hypothesis are correct then you can change the import-package header of the UPnP Base Driver in order to force the loading of the classes from the bundle 0 by means of the bundle-symbolic-name parameter of import-package header (see OSGi Service Platform Release 4 Version 4.2 page 52). Kind Regards, Charbel
Re: Error with UPnP Base driver
Dear Charbel, Sorry for the late answer, I really believe that is a problem related from the wiring. Actually, the problem is not caused by bundle 20 and 22 but to others bundle on your configuration. If you want to find the source of the problem you should inspect the import/export tree for the packages org.xml.sax and org.xml.sax Nevertheless, I believe that easier for you to force the wiring of the org.w3c.dom and org.xml.sax packages of the UPnP Base Driver to the framework bundle. If you want to try this solution, you have to: 1 - download the UPnP bundle sources 2 - modify the pom.xml by replacing the content of the Import-Package tag org.osgi.*, javax.xml.parsers;bundle-symbolic-name=org.apache.felix.framework, org.w3c.dom;bundle-symbolic-name=org.apache.felix.framework, org.xml.sax;bundle-symbolic-name=org.apache.felix.framework 3 - package the bundle with maven, by executing mvn install 4 - replace the UPnP Base Driver bundle with the one just created, that is located inside target folder As additional note, you should be aware that inspect command shows only the actual wiring of the bundle which may be different from the content of the Import/Export-Pacakge headers of the bundle you are inspecting ( Richard would you mind to correct me if I'm wrong?) Ciao, Stefano Kismet Lenzi On 02/06/2010 11.18, charbel el_kaed wrote: Hi Stefano, I inspected the packages and this is what I found. (The inspection result are below) Bundle 20 ONLY imports org.w3c.dom and org.xml.sax while Bundle 22 imports and exports org.xml.sax In your previous reply you mentioned the correct configuration as: I think that the correct configuration of bundle 20 and 22 are: - bundle 20 and 22 import and export the packages: org.w3c.dom and org.xml.sax - bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax So I am not sure if it is correct. I am really new to this. I am looking at the OSGi Service Platform Release 4 core, Version 4.2 page 52 - inspect package c 20 org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] exports packages: -- org.jdom; version=0.0.0 org.jdom.adapters; version=0.0.0 org.jdom.filter; version=0.0.0 org.jdom.output; version=0.0.0 org.jdom.output.sax; version=0.0.0 org.jdom.output.stax; version=0.0.0 org.jdom.input.stax; version=0.0.0 - inspect package r 20 org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] imports packages: -- javax.xml.stream; version=1.6.0 - org.apache.felix.framework [0] org.xml.sax.ext; version=1.6.0 - org.apache.felix.framework [0] org.w3c.dom; version=2.0.0 - org.soa4d.forge.osgi.xml.dom.l2.core.api.osgi [19] org.xml.sax; version=2.0.2 - org.soa4d.forge.osgi.xml.sax2.api.osgi [21] org.xml.sax.helpers; version=2.0.2 - org.soa4d.forge.osgi.xml.sax.over.pull.bri dge.osgi [22] org.xquark.serialize; version=1.1.1 - org.soa4d.forge.osgi.xml.xquare.serializi ng [23] # - inspect package c 22 org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] exports packages: - org.xml.sax.ext; version=2.0.2 org.xml.sax.helpers; version=2.0.2 - inspect package r 22 org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] imports packages: - org.xmlpull.v1; version=1.1.2 - org.soa4d.forge.osgi.xml.kxml.pullparser.osgi [15] org.xml.sax; version=2.0.2 - org.soa4d.forge.osgi.xml.sax2.api.osgi [21] Kind regards, Charbel. Date: Tue, 1 Jun 2010 14:54:41 +0200 From: le...@apache.org Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org On 01/06/2010 1.58, charbel el_kaed wrote: Hi Stefano, Thanks for your reply. I can't actually touch those bundles. Is there another way to do so ? Have you checked if the hypothesis regarding the import/export headers of bundle 20 and 22 are correct? If they aren't then the source of the problem is somewhere else. If the hypothesis are correct then you can change the import-package header of the UPnP Base Driver in order to force the loading of the classes from the bundle 0 by means of the bundle-symbolic-name parameter of import-package header (see OSGi Service Platform Release 4 Version 4.2 page 52). Kind Regards, Charbel.
RE: Error with UPnP Base driver
Hi Stefano, I inspected the packages and this is what I found. (The inspection result are below) Bundle 20 ONLY imports org.w3c.dom and org.xml.sax while Bundle 22 imports and exports org.xml.sax In your previous reply you mentioned the correct configuration as: I think that the correct configuration of bundle 20 and 22 are: - bundle 20 and 22 import and export the packages: org.w3c.dom and org.xml.sax - bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax So I am not sure if it is correct. I am really new to this. I am looking at the OSGi Service Platform Release 4 core, Version 4.2 page 52 - inspect package c 20 org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] exports packages: -- org.jdom; version=0.0.0 org.jdom.adapters; version=0.0.0 org.jdom.filter; version=0.0.0 org.jdom.output; version=0.0.0 org.jdom.output.sax; version=0.0.0 org.jdom.output.stax; version=0.0.0 org.jdom.input.stax; version=0.0.0 - inspect package r 20 org.soa4d.forge.osgi.xml.jdom.over.stax.sax.xquark.osgi [20] imports packages: -- javax.xml.stream; version=1.6.0 - org.apache.felix.framework [0] org.xml.sax.ext; version=1.6.0 - org.apache.felix.framework [0] org.w3c.dom; version=2.0.0 - org.soa4d.forge.osgi.xml.dom.l2.core.api.osgi [19] org.xml.sax; version=2.0.2 - org.soa4d.forge.osgi.xml.sax2.api.osgi [21] org.xml.sax.helpers; version=2.0.2 - org.soa4d.forge.osgi.xml.sax.over.pull.bri dge.osgi [22] org.xquark.serialize; version=1.1.1 - org.soa4d.forge.osgi.xml.xquare.serializi ng [23] # - inspect package c 22 org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] exports packages: - org.xml.sax.ext; version=2.0.2 org.xml.sax.helpers; version=2.0.2 - inspect package r 22 org.soa4d.forge.osgi.xml.sax.over.pull.bridge.osgi [22] imports packages: - org.xmlpull.v1; version=1.1.2 - org.soa4d.forge.osgi.xml.kxml.pullparser.osgi [15] org.xml.sax; version=2.0.2 - org.soa4d.forge.osgi.xml.sax2.api.osgi [21] Kind regards, Charbel. Date: Tue, 1 Jun 2010 14:54:41 +0200 From: le...@apache.org Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org On 01/06/2010 1.58, charbel el_kaed wrote: Hi Stefano, Thanks for your reply. I can't actually touch those bundles. Is there another way to do so ? Have you checked if the hypothesis regarding the import/export headers of bundle 20 and 22 are correct? If they aren't then the source of the problem is somewhere else. If the hypothesis are correct then you can change the import-package header of the UPnP Base Driver in order to force the loading of the classes from the bundle 0 by means of the bundle-symbolic-name parameter of import-package header (see OSGi Service Platform Release 4 Version 4.2 page 52). Kind Regards, Charbel. _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969
Re: Error with UPnP Base driver
On 01/06/2010 1.58, charbel el_kaed wrote: Hi Stefano, Thanks for your reply. I can't actually touch those bundles. Is there another way to do so ? Have you checked if the hypothesis regarding the import/export headers of bundle 20 and 22 are correct? If they aren't then the source of the problem is somewhere else. If the hypothesis are correct then you can change the import-package header of the UPnP Base Driver in order to force the loading of the classes from the bundle 0 by means of the bundle-symbolic-name parameter of import-package header (see OSGi Service Platform Release 4 Version 4.2 page 52). Kind Regards, Charbel.
RE: Error with UPnP Base driver
Hi Stefano, Thanks for your reply. I can't actually touch those bundles. Is there another way to do so ? Kind Regards, Charbel. _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969
Re: Error with UPnP Base driver
On 27/05/2010 14.47, charbel el_kaed wrote: Hi Stefano, This is the wiring I had: === start 4 ... DEBUG: WIRE: 4.0 - javax.xml.parsers - 0 DEBUG: WIRE: 4.0 - org.w3c.dom - 20.0 DEBUG: WIRE: 4.0 - org.xml.sax - 22.0 I believe that the problem is caused by the wiring above. In fact, considering that you are using Java 6 you should have all the above wiring should pointing at bundle 0. Felix fails to resolve the wiring to bundle 0 because the Import-Package and Export-Package headers of bundle 20 and 22 may be not correct. I think that the correct configuration of bundle 20 and 22 are: - bundle 20 and 22 import and export the packages: org.w3c.dom and org.xml.sax - bundle 20 and 22 ONLY import the packages: org.w3c.dom and org.xml.sax I hope it can help...
RE: Error with UPnP Base driver
Hi Stephano, During the step: 3 - stop Felix with the command stop 0 (if you stop it with ^C or by killing java the next steps will fail) Ok Then starting felix with java -jar bin\felix.jar -Dfelix.log.level=5 The upnp base driver is already installed actually, so step 6 is not necessary Maybe I am missing something ? Or you mean I should change the log.level=5 in the config file? Thanks and Regards. charbel. From: le...@apache.org Date: Wed, 26 May 2010 19:46:50 +0200 Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org CC: charbel_el_k...@hotmail.com It looks like that you are facing a classloading issue The problem is related to your OSGi configuration , in fact I have just tried to execute the UPnP Base Driver 0.8.0 on Felix 2.0.5 and it runs perfectly. By looking at your configuration I don't think that the problem is related to the org.osgi.framework.system.packages.extra properties but it may be related to the export package defined by the bundles you have installed. If you want to identify the source of the problem a I need more debug information. In particular, I need the wiring message for trace how the UPnP Base Driver is loading the xml parser. In case that you don't know of to provide me the wiring, here are the steps to execute: 1 - start Felix 2 - stop the UPnP Base Driver bundle 3 - stop Felix with the command stop 0 (if you stop it with ^C or by killing java the next steps will fail) 4 - start Felix with felix.log.level=5 5 - execute the PS command from felix shell 6 - start the UPnP Base Driver bundle 7 - kill Felix (by pressing ^C) 8 - send me the output of the ps command along with the messages printed after the point 6 (in particular you should get some messages like DEBUG: DYNAMIC WIRE: 1.0 - org.apache.felix.shell - 2.0 DEBUG: WIRE: 3.0 - org.apache.felix.shell - 2.0 ) Best regards, Stefano Kismet Lenzi On Wed, May 26, 2010 at 16:42, charbel el_kaed charbel_el_k...@hotmail.comwrote: I added your email too Kind Regards, charbel _ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969
Re: Error with UPnP Base driver
On 27/05/2010 9.47, charbel el_kaed wrote: Hi Stephano, During the step: 3 - stop Felix with the command stop 0 (if you stop it with ^C or by killing java the next steps will fail) Ok Then starting felix with java -jar bin\felix.jar -Dfelix.log.level=5 If you start felix with java -jar bin\felix.jar -Dfelix.log.level=5 the log level would not be changed you have to modify config.properties file The upnp base driver is already installed actually, so step 6 is not necessary Maybe I am missing something ? Probably I was not clear, let me explain the goal and how to achieve it. The goal is to debug the classloader wiring produced by Felix for UPnP Base Driver which is failing. The procedure that I gave you should achieve the goal, in fact Felix print out the wiring when it resolve them, which it happens when a bundle is active. So to get the wiring printed we have to start the UPnP Base Driver (installing it is not enough), but on the other hand we want to minimize the printing to easy read the wiring. The step 6 of the procedure is used for starting the UPnP Base Driver after all the other bundles so that only his wiring will be printed out. In fact, if you noticed the output of step 5 the status of UPnP Base Driver should either installed or resolved. In case that, the status of UPnP Base Driver is active it means that you missed something either during step 2 or step 3 Or you mean I should change the log.level=5 in the config file? Yes, you have to change it. See my comment above Thanks and Regards. charbel. From: le...@apache.org Date: Wed, 26 May 2010 19:46:50 +0200 Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org CC: charbel_el_k...@hotmail.com It looks like that you are facing a classloading issue The problem is related to your OSGi configuration , in fact I have just tried to execute the UPnP Base Driver 0.8.0 on Felix 2.0.5 and it runs perfectly. By looking at your configuration I don't think that the problem is related to the org.osgi.framework.system.packages.extra properties but it may be related to the export package defined by the bundles you have installed. If you want to identify the source of the problem a I need more debug information. In particular, I need the wiring message for trace how the UPnP Base Driver is loading the xml parser. In case that you don't know of to provide me the wiring, here are the steps to execute: 1 - start Felix 2 - stop the UPnP Base Driver bundle 3 - stop Felix with the command stop 0 (if you stop it with ^C or by killing java the next steps will fail) 4 - start Felix with felix.log.level=5 5 - execute the PS command from felix shell 6 - start the UPnP Base Driver bundle 7 - kill Felix (by pressing ^C) 8 - send me the output of the ps command along with the messages printed after the point 6 (in particular you should get some messages like DEBUG: DYNAMIC WIRE: 1.0 - org.apache.felix.shell - 2.0 DEBUG: WIRE: 3.0 - org.apache.felix.shell - 2.0 ) Best regards, Stefano Kismet Lenzi On Wed, May 26, 2010 at 16:42, charbel el_kaed charbel_el_k...@hotmail.comwrote: I added your email too Kind Regards, charbel
RE: Error with UPnP Base driver
Hi Stephano, I attached the configuration file of the OSGi framework. I am using the Java version 1.6.0_20. and Felix version 2.0.5 Thanks and Regards, Charbel Date: Tue, 25 May 2010 16:57:57 +0200 From: le...@apache.org Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org Dear Charbel, Actually I have never had such problem, at the moment the only things that I can think of is some issue with bootdelagation of classes, but I need further information to come up with a solution. Would you mind to send us: - The OSGi version that you are using - Java version used for executing OSGi - The loading parameter of the OSGi enviroment Best regards, Stefano Kismet Lenzi On 25/05/2010 14.08, charbel el_kaed wrote: Hi, I am having the following exceptions: 14:02:32.845 EVENT Started HttpContext[/9ceebf86-8a60-3ba4-f066-446732608f68/pr esentation] 14:02:32.845 EVENT Started HttpContext[/lightService/wsdl] Exception in thread Cyber.SSDPSearchResponseSocket/0.0.0.0/0.0.0.0:2957:2957 j ava.lang.LinkageError: loader constraint violation: loader (instance ofbootloa der) previously initiated loading for a different type with name org/xml/sax/I nputSource at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown So urce) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk nown Source) at org.cybergarage.xml.parser.JaxpParser.parse(JaxpParser.java:112) at org.cybergarage.xml.Parser.parse(Parser.java:66) at org.cybergarage.upnp.ControlPoint.addDevice(ControlPoint.java:266) at org.cybergarage.upnp.ControlPoint.searchResponseReceived(ControlPoint .java:529) at org.cybergarage.upnp.ssdp.SSDPSearchResponseSocket.run(SSDPSearchResp onseSocket.java:79) at java.lang.Thread.run(Unknown Source) Exception in thread Cyber.SSDPNotifySocket/10.194.3.221:1900 - 239.255.255.250 :1900 java.lang.LinkageError: org/xml/sax/InputSource at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk nown Source) at org.cybergarage.xml.parser.JaxpParser.parse(JaxpParser.java:112) at org.cybergarage.xml.Parser.parse(Parser.java:66) at org.cybergarage.upnp.ControlPoint.addDevice(ControlPoint.java:266) at org.cybergarage.upnp.ControlPoint.notifyReceived(ControlPoint.java:51 8) at org.cybergarage.upnp.ssdp.SSDPNotifySocket.run(SSDPNotifySocket.java: 124) at java.lang.Thread.run(Unknown Source) Anybody else is having the same errors ? and have an idea about it ? Thanks and Regards, Charbel _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969 No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2894 - Release Date: 05/24/10 20:26:00 _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969
Re: Error with UPnP Base driver
On 26/05/2010 10.53, charbel el_kaed wrote: Hi Stephano, I attached the configuration file of the OSGi framework. I couldn't see any file attached to your email, can you try to send it again? Thanks and Regards, Charbel Stefano Kismet Lenzi
RE: Error with UPnP Base driver
I added your email too Kind Regards, charbel Date: Wed, 26 May 2010 15:59:50 +0200 From: le...@apache.org Subject: Re: Error with UPnP Base driver To: dev@felix.apache.org On 26/05/2010 10.53, charbel el_kaed wrote: Hi Stephano, I attached the configuration file of the OSGi framework. I couldn't see any file attached to your email, can you try to send it again? Thanks and Regards, Charbel Stefano Kismet Lenzi _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969
Re: Error with UPnP Base driver
On 5/26/10 9:59, Stefano Lenzi wrote: On 26/05/2010 10.53, charbel el_kaed wrote: Hi Stephano, I attached the configuration file of the OSGi framework. I couldn't see any file attached to your email, can you try to send it again? It is likely getting stripped by the mailing list...it isn't a good idea to send attachments to the mailing list. Either open a JIRA issue and attach it there or send it directly to the interested party...the former is the preferred approach. - richard Thanks and Regards, Charbel Stefano Kismet Lenzi
Re: Error with UPnP Base driver
It looks like that you are facing a classloading issue The problem is related to your OSGi configuration , in fact I have just tried to execute the UPnP Base Driver 0.8.0 on Felix 2.0.5 and it runs perfectly. By looking at your configuration I don't think that the problem is related to the org.osgi.framework.system.packages.extra properties but it may be related to the export package defined by the bundles you have installed. If you want to identify the source of the problem a I need more debug information. In particular, I need the wiring message for trace how the UPnP Base Driver is loading the xml parser. In case that you don't know of to provide me the wiring, here are the steps to execute: 1 - start Felix 2 - stop the UPnP Base Driver bundle 3 - stop Felix with the command stop 0 (if you stop it with ^C or by killing java the next steps will fail) 4 - start Felix with felix.log.level=5 5 - execute the PS command from felix shell 6 - start the UPnP Base Driver bundle 7 - kill Felix (by pressing ^C) 8 - send me the output of the ps command along with the messages printed after the point 6 (in particular you should get some messages like DEBUG: DYNAMIC WIRE: 1.0 - org.apache.felix.shell - 2.0 DEBUG: WIRE: 3.0 - org.apache.felix.shell - 2.0 ) Best regards, Stefano Kismet Lenzi On Wed, May 26, 2010 at 16:42, charbel el_kaed charbel_el_k...@hotmail.comwrote: I added your email too Kind Regards, charbel
Re: Error with UPnP Base driver
Dear Charbel, Actually I have never had such problem, at the moment the only things that I can think of is some issue with bootdelagation of classes, but I need further information to come up with a solution. Would you mind to send us: - The OSGi version that you are using - Java version used for executing OSGi - The loading parameter of the OSGi enviroment Best regards, Stefano Kismet Lenzi On 25/05/2010 14.08, charbel el_kaed wrote: Hi, I am having the following exceptions: 14:02:32.845 EVENT Started HttpContext[/9ceebf86-8a60-3ba4-f066-446732608f68/pr esentation] 14:02:32.845 EVENT Started HttpContext[/lightService/wsdl] Exception in thread Cyber.SSDPSearchResponseSocket/0.0.0.0/0.0.0.0:2957:2957 j ava.lang.LinkageError: loader constraint violation: loader (instance ofbootloa der) previously initiated loading for a different type with name org/xml/sax/I nputSource at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown So urce) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk nown Source) at org.cybergarage.xml.parser.JaxpParser.parse(JaxpParser.java:112) at org.cybergarage.xml.Parser.parse(Parser.java:66) at org.cybergarage.upnp.ControlPoint.addDevice(ControlPoint.java:266) at org.cybergarage.upnp.ControlPoint.searchResponseReceived(ControlPoint .java:529) at org.cybergarage.upnp.ssdp.SSDPSearchResponseSocket.run(SSDPSearchResp onseSocket.java:79) at java.lang.Thread.run(Unknown Source) Exception in thread Cyber.SSDPNotifySocket/10.194.3.221:1900 - 239.255.255.250 :1900 java.lang.LinkageError: org/xml/sax/InputSource at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unk nown Source) at org.cybergarage.xml.parser.JaxpParser.parse(JaxpParser.java:112) at org.cybergarage.xml.Parser.parse(Parser.java:66) at org.cybergarage.upnp.ControlPoint.addDevice(ControlPoint.java:266) at org.cybergarage.upnp.ControlPoint.notifyReceived(ControlPoint.java:51 8) at org.cybergarage.upnp.ssdp.SSDPNotifySocket.run(SSDPNotifySocket.java: 124) at java.lang.Thread.run(Unknown Source) Anybody else is having the same errors ? and have an idea about it ? Thanks and Regards, Charbel _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969 No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2894 - Release Date: 05/24/10 20:26:00
