[sctp-dev] SCTP_EXPLICIT_COMPLETE

[Michal Lefler]

Amir Eliaz <amir.eliaz at traffixsystems.com> wrote:

Hello Chris,
   We tried testing on two different kernels:
--  5.el6 
2.6.32-131.0.15.el6.x86_64 #1 SMP Sat May 21 10:27:57 CDT 2011 x86_64 x86_64 x86_64 GNU/Linux
Lksctp-tools version 1.0.10
-- 3.el5
2.6.18-194.el5 #1 SMP Fri Apr 2 14:58:14 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
lksctp-tools version 1.0.6

In both we get the exception "Protocol not available" when trying to access the socket option SCTP_EXPLICIT_COMPLETE from the Java API.

Regards,
--Amir

-----Original Message-----
From: Chris Hegarty [mailto:chris.hegarty at oracle.com] 
Sent: Wednesday, February 29, 2012 12:14 PM
To: Michal Lefler
Cc: sctp-dev at openjdk.java.net; Gil Shafran; Amir Eliaz
Subject: Re: [sctp-dev] (no subject)

Hi Michal,

What version of lksctp are you using? Also, what kernel?

-Chris

On 29/02/2012 09:15, Michal Lefler wrote:
> Hi all.
> We ran into the following problem.
> Whenever we try to send sctp messages which are longer than 1024b the 
> messages are automatically splitted into two smaller messages.
> The problem is that both messages are marked as "COMPLETED".
> For that reason, the receiving side sees each long message as two 
> messages.
> The first message is incomplete, while the second one is malformed.
> We first suspected the MTU, but setting the MTU to a small value 
> resulted with a nice split (first message with an unset "COMPLETED", 
> and the second one is marked as "COMPLETED", as expected).
> We tried to handle the "COMPLETED" flag manually, but trying to set 
> "SctpStandardSocketOption.SCTP_EXPLICIT_COMPLETE" to true caused a 
> "Protocol not supported" exception.
> Any idea what the problem can be and how we can solve it?
> We are using Java 1.6 u23, with the SCTP to Java 6 patch.
> Thanks,
> Michal.
>

--