[
https://issues.apache.org/jira/browse/DIRMINA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRMINA-539.
---------------------------------------
Resolution: Won't Fix
Too complex to implement in 2.0.
To be discussed in 3.0
> NioDatagramConnector doesn't takes the TrafficClass value set to his
> DatagramSessionConfig
> -------------------------------------------------------------------------------------------
>
> Key: DIRMINA-539
> URL: https://issues.apache.org/jira/browse/DIRMINA-539
> Project: MINA
> Issue Type: Bug
> Affects Versions: 2.0.0-M1
> Environment: WinXP, RHEL5 (probably not important)
> Reporter: martin krivosik
> Assignee: Emmanuel Lecharny
> Fix For: 2.0.8
>
> Original Estimate: 20m
> Remaining Estimate: 20m
>
> client sending datagrams without taking care to the trafficClas set in the
> config, so the ToS byte is not set in the packet sent from client.
> client code:
> {code}
> NioDatagramAcceptor acceptor = new NioDatagramAcceptor();
> DatagramSessionConfig dcfg =
> ((NioDatagramAcceptor)acceptor).getSessionConfig();
> dcfg.setTrafficClass(tosByte);
> InetSocketAddress bindAddrPort = new InetSocketAddress(originatingIP,
> port);
> acceptor.bind(bindAddrPort);
> {code}
> -> connecting to another computer with NioDatagramConnector.
> for me it looks like in the newHandle method of NioDatagramConnector is not
> cared about TrafficClass (like it is done in NioDatagramAcceptor.open())
> The server part with the accceptor is OK and the correct ToS byte is set in
> the packet.
> (the same problem may be in the socket, i have to check it)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
