[ 
https://issues.apache.org/jira/browse/CXF-6795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nick Birnie updated CXF-6795:
-----------------------------
    Description: 
The current WS-Discovery implementation could use support for discovering 
services which are provided on localhost. This is currently not the case, due 
to an obscure detail of multicast communications where, when a multicast packet 
is sent, by default it is not echoed back to the host that sent it.

For more info, see: http://www.tldp.org/HOWTO/Multicast-HOWTO-6.html

This should be an easy fix by setting the appropriate options on the 
MulticastSocket used by WSDiscoveryClient (which I believe is implemented by 
UDPConduit in UDPTransport).

  was:
The current WS-Discovery implementation could use support for discovering 
services which are provided on localhost. This is currently not the case, due 
to an obscure detail of multicast communications where, when a multicast packet 
is sent, by default it is not echoed back to the host that sent it.

See: http://www.tldp.org/HOWTO/Multicast-HOWTO-6.html

This should be an easy fix by setting the appropriate options on the 
MulticastSocket used by WSDiscoveryClient (which I believe is implemented by 
UDPConduit in UDPTransport).


> WS-Discovery add support for discovery on localhost
> ---------------------------------------------------
>
>                 Key: CXF-6795
>                 URL: https://issues.apache.org/jira/browse/CXF-6795
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 3.1.5
>            Reporter: Nick Birnie
>
> The current WS-Discovery implementation could use support for discovering 
> services which are provided on localhost. This is currently not the case, due 
> to an obscure detail of multicast communications where, when a multicast 
> packet is sent, by default it is not echoed back to the host that sent it.
> For more info, see: http://www.tldp.org/HOWTO/Multicast-HOWTO-6.html
> This should be an easy fix by setting the appropriate options on the 
> MulticastSocket used by WSDiscoveryClient (which I believe is implemented by 
> UDPConduit in UDPTransport).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to