On Oct 23, 2013, at 8:37 AM, Pampolini Matteo <[email protected]> wrote:
> Hi Dan, > > did you find some time to look at this issue? Just fixed, I think. Can you give the next snapshots a try? Dan > > Thanks, Matteo > > > -------- Original Message -------- > Subject: Re: WS-Discovery does not work with a WCF discovery proxy > (should be fixed in CXF Jira) > Date: Wed, 16 Oct 2013 11:21:38 +0200 > From: Pampolini Matteo <[email protected]> > To: [email protected] <[email protected]> > CC: Daniel Kulp <[email protected]> > > Hi Dan, > > many thanks for your quick reply. Please find attached both exceptions > traces (I had to enable them in WSDiscoveryClient code) and Wireshark > captures. The address from which I start WS-Discovery is 172.19.121.75 > while the proxy is hosted at 172.19.121.69. You can note that the proxy > replies with SOAP fault messages, but after that all ONVIF devices on > the network reply by themselves, then I expected my client to receive > and process the replies anyway. > > I also tried directly with the proxy without success. > > Regards, Matteo > > On 15/10/2013 18:58, Daniel Kulp wrote: > > On Oct 15, 2013, at 12:04 PM, Pampolini Matteo > > <[email protected]> wrote: > > > >> Hello there, > >> > >> I'm using CXF WS-Discovery to find ONVIF devices on my network. > >> > >> After a patch from Dan, included from version 2.7.5, that allows to set > >> discovery version to 1.0 everything > >> was fine, but now I'm facing a new issue if a discovery proxy developed > >> with .NET WCF is in the same network, > >> I get some exceptions (I recompiled CXF with some custom debug prints) and > >> no device is found. Shutting down > >> the proxy everything works as expected. > > I'd likely need to at least see what the exceptions are. Ideally, could > > you wireshark the probe and responses and see what is coming back. > > > > One thought is that the proxy is sending back a Hello and thus the client > > is flipping to managed mode (to use the proxy), but the proxy isn't then > > sending any information back or CXF isn't waiting for it and it's getting > > lost. What happens if you do a second probe with the same client? In > > that case, the probe should ONLY go to the proxy. > > > > What happens if you force the client to use the proxy right up front via > > the constructor that takes the address? Use an address like > > "soap.udp://proxy.hostname:3702". In that case, the probe should just go > > to the proxy immediately. Does the proxy return the right information? > > > > Not sure what else to suggest at this point. Would really need to the > > packets and stack traces. > > > > Dan > > > > > > > >> It seems a similar, not to say equal, issue was opened on CXF Jira with > >> number 4955 that should be fixed now, > >> but this is not my case. Since in issue description the WS-Discover > >> version mentioned is 1.1, could it be that > >> the issue is still present when setting version 1.0, as requested by ONVIF > >> specs? > >> > >> Any help is very appreciated, thanks in advance, > >> > >> Matteo > >> > >> > >> This email and any attachments are confidential to the intended recipient > >> and may also be privileged. If you are not the intended recipient please > >> delete it from your system and notify the sender. You should not copy it > >> or use it for any purpose nor disclose or distribute its contents to any > >> other person. > >> Questa e-mail e tutti i suoi allegati sono da intendersi inviati in via > >> riservata all'effettivo destinatario e possono essere soggetti a > >> restrizioni legali. Se non siete l'effettivo destinatario o avete ricevuto > >> il messaggio per errore siete pregati di cancellarlo dal vostro sistema e > >> di avvisare il mittente. E' vietata la duplicazione, l'uso a qualsiasi > >> titolo, la divulgazione o la distribuzione dei contenuti di questa e-mail > >> a qualunque altro soggetto. > >> > >> Prima di stampare questa comunicazione consideratene, per favore, > >> l'impatto ambientale > >> Please consider the environment before printing this email > > > > > This email and any attachments are confidential to the intended recipient and > may also be privileged. If you are not the intended recipient please delete > it from your system and notify the sender. You should not copy it or use it > for any purpose nor disclose or distribute its contents to any other person. > Questa e-mail e tutti i suoi allegati sono da intendersi inviati in via > riservata all'effettivo destinatario e possono essere soggetti a restrizioni > legali. Se non siete l'effettivo destinatario o avete ricevuto il messaggio > per errore siete pregati di cancellarlo dal vostro sistema e di avvisare il > mittente. E' vietata la duplicazione, l'uso a qualsiasi titolo, la > divulgazione o la distribuzione dei contenuti di questa e-mail a qualunque > altro soggetto. > > Prima di stampare questa comunicazione consideratene, per favore, l'impatto > ambientale > Please consider the environment before printing this email > <discovery.zip> -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
