[ 
https://issues.apache.org/jira/browse/CAMEL-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713694#comment-13713694
 ] 

Sam Patel edited comment on CAMEL-6563 at 7/19/13 2:19 PM:
-----------------------------------------------------------

Pull request:
https://github.com/apache/camel/pull/31

Pull request developer discussion topic:
http://camel.465427.n5.nabble.com/camel-pull-request-CAMEL-6563-Added-networkInterface-option-and-added-logi-td5735874.html
                
      was (Author: samel):
    Pull request:

https://github.com/apache/camel/pull/31

Pull request developer discussion topic:

http://camel.465427.n5.nabble.com/camel-pull-request-CAMEL-6563-Added-networkInterface-option-and-added-logi-td5735874.html
                  
> camel-netty - unable to consume on UDP multicast addresses
> ----------------------------------------------------------
>
>                 Key: CAMEL-6563
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6563
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 2.11.0
>         Environment: Karaf 2.3.1
> Java 7 
> Ubuntu 12.04 (64 bit)
>            Reporter: Sam Patel
>            Priority: Minor
>
> When using a route to listen to UDP multicast address , no messages seem to 
> get consumed. No exceptions are observed. 
> Multicast address is defined as addresses in the range of 224.0.0.0 through 
> 239.255.255.255 (http://en.wikipedia.org/wiki/Multicast_address)
> Input was simple string (e.g. "Test String")
> Example Route:
> <route>
>      <from 
> uri="netty:udp://225.1.1.1:8001?allowDefaultCodec=false&sync=false&broadcast=true"/>
> </route>
> Found an old topic in the user discussion forum that seems related.  Did not 
> find any unit tests in the Camel source code exercising this behavior.  
> (http://camel.465427.n5.nabble.com/camel-netty-and-multicast-tt4638622.html)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to