Hi Stefano,
This is the wiring I had:
=======================================
start 4
DEBUG: WIRE: 4.0 -> org.osgi.service.log -> 2.0
DEBUG: WIRE: 4.0 -> org.osgi.service.upnp -> 8.0
DEBUG: WIRE: 4.0 -> org.osgi.framework -> 0
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
-> Exception in thread "Cyber.SSDPNotifySocket/10.194.3.221:1900 -> 239.255.255.
250:1900" java.lang.LinkageError: loader constraint violation: loader (instance
of <bootloader>) previously initiated loading for a different type with name "or
g/xml/sax/InputSource"
-> Exception in thread "Cyber.SSDPNotifySocket/10.194.3.221:1900 -> 239.255.255.
250:1900" java.lang.LinkageError: loader constraint violation: loader (instance
of <bootloader>) previously initiated loading for a different type with name "or
g/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(Unknown
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:518)
at
org.cybergarage.upnp.ssdp.SSDPNotifySocket.run(SSDPNotifySocket.java:124)
at java.lang.Thread.run(Unknown Source)
Exception in thread "Cyber.SSDPSearchResponseSocket/0.0.0.0/0.0.0.0:3493:3493"
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(Unknown
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(SSDPSearchResponseSocket.java:79)
at java.lang.Thread.run(Unknown Source)
ShellTUI: No standard input...exiting.
-----> SetLevelCommand deactivated
-----> GetStatusCommand deactivated
-----> GetLevelCommand deactivated
-----> SwitchCommand deactivated
-----> LightsClient deactivated
-----> Light device left
Deactivating Light device ...
14:42:54.223 EVENT Stopped HttpContext[/lightService/wsdl]
14:42:54.223 EVENT Stopped
HttpContext[/9ceebf86-8a60-3ba4-f066-446732608f68/presentation]
14:42:54.458 EVENT Stopping Acceptor
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
WARNING! Bundle #25 called closed LogRef object
debug 20100527 14:42:54 bid#25 -
org.soda.dpws.transport.udp.AbstractSoapUdpScheduler: Sending message -> To
address : 239.255.255.250 To port : 3702
WARNING! Bundle #25 called closed LogRef object
debug 20100527 14:42:54 bid#25 -
org.soda.dpws.transport.udp.AbstractSoapUdpScheduler: Sending message -> data :
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery"
xmlns:wsa="http://schemas.xmlsoa
p.org/ws/2004/08/addressing"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:2005:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discove
ry/Bye</wsa:Action><wsa:MessageID>urn:uuid:47d9cbdf-b9d0-197f-fa36-8d6020d0150a</wsa:MessageID><wsd:AppSequence
InstanceId="92"
MessageNumber="4"/></soap:Header><soap:Body><wsd:Bye><wsa:EndpointReference><wsa:Address>urn:uuid:9ceebf86-8a60-3ba4-f066-446732608f68</wsa:Address></wsa:EndpointReference></wsd:Bye></soap:Body></soap:Envelope>
WARNING! Bundle #25 called closed LogRef object
debug 20100527 14:42:54 bid#25 - org.soda.dpws.transport.udp.AbstractSo
apUdpScheduler: Sending message -> To address : 239.255.255.250 To port : 3702
WARNING! Bundle #25 called closed LogRef object
debug 20100527 14:42:54 bid#25 - org.soda.dpws.transport.udp.AbstractSo
apUdpScheduler: Sending message -> data : <?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:wsd="h
ttp://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:wsa="http://schemas.xmlsoa
p.org/ws/2004/08/addressing"><soap:Header><wsa:To>urn:schemas-xmlsoap-org:ws:200
5:04:discovery</wsa:To><wsa:Action>http://schemas.xmlsoap.org/ws/2005/04/discove
ry/Bye</wsa:Action><wsa:MessageID>urn:uuid:47d9cbdf-b9d0-197f-fa36-8d6020d0150a<
/wsa:MessageID><wsd:AppSequence InstanceId="92" MessageNumber="4"/></soap:Header
><soap:Body><wsd:Bye><wsa:EndpointReference><wsa:Address>urn:uuid:9ceebf86-8a60-
3ba4-f066-446732608f68</wsa:Address></wsa:EndpointReference></wsd:Bye></soap:Bod
y></soap:Envelope>
14:42:55.380 EVENT Stopped SocketListener on 0.0.0.0:8080
14:42:55.380 EVENT Stopped ServletHttpContext[/]
14:42:55.380 EVENT Stopped org.mortbay.http.httpser...@1dff3a2
==============================================================
I can send the framework and the bundles if you want.
Regards,
Charbel
> Date: Thu, 27 May 2010 11:33:28 +0200
> From: le...@apache.org
> Subject: Re: Error with UPnP Base driver
> To: dev@felix.apache.org
>
> 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.com>wrote:
> >>
> >>>
> >>> I added your email too
> >>>
> >>>
> >>> Kind Regards,
> >>>
> >>> charbel
> >>>
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
https://signup.live.com/signup.aspx?id=60969