i tried to run the base driver with a Media server already running and i get this error:
at gnu.java.net.VMPlainSocketImpl.bind(Native Method) at gnu.java.net.VMPlainSocketImpl.bind(VMPlainSocketImpl.java:302) at gnu.java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:125) at java.net.DatagramSocket.bind(DatagramSocket.java:700) at java.net.MulticastSocket.<init>(MulticastSocket.java:112) at java.net.MulticastSocket.<init>(MulticastSocket.java:93) at org.cybergarage.upnp.ssdp.HTTPMUSocket.open(HTTPMUSocket.java:133) at org.cybergarage.upnp.ssdp.HTTPMUSocket.open(HTTPMUSocket.java:147) at org.cybergarage.upnp.ssdp.SSDPNotifySocket.<init>(SSDPNotifySocket.java:52) at org.cybergarage.upnp.ssdp.SSDPNotifySocketList.open(SSDPNotifySocketList.java:89) at org.cybergarage.upnp.ControlPoint.start(ControlPoint.java:852) at org.cybergarage.upnp.ControlPoint.start(ControlPoint.java:905) at org.apache.felix.upnp.basedriver.Activator.doInitImporter(Activator.java:239) at org.apache.felix.upnp.basedriver.Activator.start(Activator.java:87) at org.knopflerfish.framework.BundleImpl.start0(BundleImpl.java:373) at org.knopflerfish.framework.PermissionOps.callStart0(PermissionOps.java:212) at org.knopflerfish.framework.BundleImpl.start(BundleImpl.java:320) at org.knopflerfish.framework.StartLevelImpl.increaseStartLevel(StartLevelImpl.java:278) at org.knopflerfish.framework.StartLevelImpl$1.run(StartLevelImpl.java:210) at org.knopflerfish.framework.StartLevelImpl.run(StartLevelImpl.java:171) at java.lang.Thread.run(Thread.java:743) [stdout] ## DEBUG: errors - FrameworkErrorEvent bundle #751 [stdout] ## DEBUG: errors - FrameworkErrorEvent throwable: org.osgi.framework.BundleException: BundleActivator start failed at org.knopflerfish.framework.BundleImpl.start0(BundleImpl.java:418) at org.knopflerfish.framework.PermissionOps.callStart0(PermissionOps.java:212) at org.knopflerfish.framework.BundleImpl.start(BundleImpl.java:320) at org.knopflerfish.framework.StartLevelImpl.increaseStartLevel(StartLevelImpl.java:278) at org.knopflerfish.framework.StartLevelImpl$1.run(StartLevelImpl.java:210) at org.knopflerfish.framework.StartLevelImpl.run(StartLevelImpl.java:171) at java.lang.Thread.run(Thread.java:743) Caused by: java.lang.NullPointerException at org.cybergarage.upnp.ssdp.HTTPMUSocket.getLocalPort(HTTPMUSocket.java:95) at org.cybergarage.upnp.ssdp.SSDPNotifySocket.start(SSDPNotifySocket.java:122) at org.cybergarage.upnp.ssdp.SSDPNotifySocketList.start(SSDPNotifySocketList.java:115) at org.cybergarage.upnp.ControlPoint.start(ControlPoint.java:855) at org.cybergarage.upnp.ControlPoint.start(ControlPoint.java:905) at org.apache.felix.upnp.basedriver.Activator.doInitImporter(Activator.java:239) at org.apache.felix.upnp.basedriver.Activator.start(Activator.java:87) at org.knopflerfish.framework.BundleImpl.start0(BundleImpl.java:373) ...6 more [stdout] Nested bundle exception: java.lang.NullPointerException at org.cybergarage.upnp.ssdp.HTTPMUSocket.getLocalPort(HTTPMUSocket.java:95) at org.cybergarage.upnp.ssdp.SSDPNotifySocket.start(SSDPNotifySocket.java:122) at org.cybergarage.upnp.ssdp.SSDPNotifySocketList.start(SSDPNotifySocketList.java:115) at org.cybergarage.upnp.ControlPoint.start(ControlPoint.java:855) at org.cybergarage.upnp.ControlPoint.start(ControlPoint.java:905) at org.apache.felix.upnp.basedriver.Activator.doInitImporter(Activator.java:239) at org.apache.felix.upnp.basedriver.Activator.start(Activator.java:87) at org.knopflerfish.framework.BundleImpl.start0(BundleImpl.java:373) at org.knopflerfish.framework.PermissionOps.callStart0(PermissionOps.java:212) at org.knopflerfish.framework.BundleImpl.start(BundleImpl.java:320) at org.knopflerfish.framework.StartLevelImpl.increaseStartLevel(StartLevelImpl.java:278) at org.knopflerfish.framework.StartLevelImpl$1.run(StartLevelImpl.java:210) at org.knopflerfish.framework.StartLevelImpl.run(StartLevelImpl.java:171) at java.lang.Thread.run(Thread.java:743) how can you explain that Sana, 2009/5/19 chihi asma <[email protected]> > ok thanks a lot. > > Asma > > --- En date de : Mar 19.5.09, Francesco Furfari < > [email protected]> a écrit : > > De: Francesco Furfari <[email protected]> > Objet: Re: UPnP Port > À: [email protected] > Date: Mardi 19 Mai 2009, 16h44 > > Yes, I looked at the code, and I can confirm that we use the first > available port. The original code from from Cyberlink used a fixed port. > We changed this behavior to run multiple instances of the OSGi framework. > > If you want to change it you can modify the code @ line 113 of the > org.cybergarage.upnp.ControlPoint: > > private final static int DEFAULT_SSDP_PORT = 0; > > > By inspecting the pom you get the domoware repository > > http://domoware.isti.cnr.it/maven2/it/cnr/isti/domoware/cyberdomo/upnp-stack/1.8.0/ > > francesco > > > > chihi asma wrote: > > Thanks. but I have an other question. I see that the basedriver import in > its code the org.cybergarage and I dont know from where the basedriver get > this library? I don't have it? > > thanks in advance > > > > > > --- En date de : Mar 19.5.09, Francesco Furfari < > [email protected]> a écrit : > > > > De: Francesco Furfari <[email protected]> > > Objet: Re: UPnP Port > > À: [email protected] > > Date: Mardi 19 Mai 2009, 16h14 > > > > the right way to reply is by getting the source address of the received > > M-Search message , I guess the basedriver uses the first available port > > to send the request, I don't remember now. > > > > francesco > > > > > > chihi asma wrote: > >> thanks Francesco I understand this, but I know that to respond to > control point M-Search, devices should send an unicast ssdp message. I want > to know to which port? > >> Does the basedrievr specify any port? > >> --- En date de : Mar 19.5.09, Francesco Furfari < > [email protected]> a écrit : > >> > >> De: Francesco Furfari <[email protected]> > >> Objet: Re: UPnP Port > >> À: [email protected] > >> Date: Mardi 19 Mai 2009, 15h46 > >> > >> Hi Asma, > >> > >> if your question is: > >> Can UPnP devices coexist on the same host machine? one developed by > using Felix Base driver and another one (the mentioned Mediaserver) > developed by third party? > >> > >> The answer is yes, the port is not a problem. > >> It is a port used by all the devices belonging to the same multicast > group. You don't need to change the port for the devices running on the OSGi > Platform. > >> > >> ------ > >> > >> If you have experienced a conflict then there is a bug. > >> > >> > >> francesco > >> > >> > >> > >> > >> > >> chihi asma wrote: > >>> I understand that the 1900 port is a standard port on which listens > UPnP devices and control points, but on which source port sends the > basedriver the ssdp requests? I can't find it in the source code of the > basedriver. Please help me > >>> > >>> Asma > >>> > >>> --- En date de : Mar 19.5.09, Stefano Lenzi <[email protected]> a > écrit : > >>> > >>> De: Stefano Lenzi <[email protected]> > >>> Objet: Re: UPnP Port > >>> À: [email protected] > >>> Date: Mardi 19 Mai 2009, 14h43 > >>> > >>> chihi asma wrote: > >>>> Hi, > >>>> > >>>> I'm runing the UPnP basedriver in an embedded device to detect UPnP > services on the network and as it is shown in the upnp.properties file the > default ssdp port is 1900 but I'm also runing a media server which listens > on the same port. So I get a conflict. May I change the basedriver port > without having any problem? > >>> If change the listing port you are creating UPnP network that can't > discover each other, unless you want to "join" the network on the OSGi > platform. Is it clear? > >>> > >>>> Thanks in advance > >>>> > >>>> > >>>> > >>>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> > >>> > >>> > >>> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > >> > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > >
