[
https://issues.apache.org/jira/browse/DIRMINA-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
martin krivosik reopened DIRMINA-539:
-------------------------------------
thx very much for quick fix,
unfortunately it takes me more time to go back to this problem and verify why
it does not work correctly.
in the DefaultDatagramSessionConfig
are variables
GET_TRAFFIC_CLASS_AVAILABLE
SET_TRAFFIC_CLASS_AVAILABLE
both of them are false, but only the GET_XXXX is setup according the current
conditions.
the SET_XXX is never touched and therefore is not possible to set the traffic
mask
in setTrafficClass() method in NioDatagramSessionConfig class since it is
always false..
Since I do not understand completely the aim if your design and architecture of
the lib,
I will ask you kindly to look on it and provide some fix...
> 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: Trustin Lee
> Fix For: 2.0.0-M2
>
> Original Estimate: 0.33h
> Remaining Estimate: 0.33h
>
> 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:
> NioDatagramAcceptor acceptor = new NioDatagramAcceptor();
> DatagramSessionConfig dcfg =
> ((NioDatagramAcceptor)acceptor).getSessionConfig();
> dcfg.setTrafficClass(tosByte);
> InetSocketAddress bindAddrPort = new InetSocketAddress(originatingIP,
> port);
> acceptor.bind(bindAddrPort);
> -> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
