incubator-etch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holger Grandy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ETCH-80) Windows 7 / .NET 3.5 SP1 runtime setsockopt error
Date Wed, 15 Sep 2010 09:11:36 GMT

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

Holger Grandy updated ETCH-80:
------------------------------

    Fix Version/s: 1.1
                       (was: 1.2)

> Windows 7 / .NET 3.5 SP1 runtime setsockopt error
> -------------------------------------------------
>
>                 Key: ETCH-80
>                 URL: https://issues.apache.org/jira/browse/ETCH-80
>             Project: Etch
>          Issue Type: Bug
>          Components: csharp-binding
>    Affects Versions: 1.0.2
>         Environment: Windows 7, Visual Studio 2008 SP1
>            Reporter: James E. King, III
>            Assignee: Holger Grandy
>            Priority: Critical
>             Fix For: 1.1
>
>   Original Estimate: 0.03h
>  Remaining Estimate: 0.03h
>
> When starting a client or server in this environment an exception is thrown and the socket
closes with the following stack - this stops everything:
> System.Net.Sockets.SocketException: An unknown, invalid, or unsupported option or level
was specified in a getsockopt or setsockopt call
>       at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName
optionName, Int32 optionValue, Boolean silent)
>       at System.Net.Sockets.Socket.SetSocketOption(SocketOptionLevel optionLevel, SocketOptionName
optionName, Int32 optionValue)
>       at Etch.Util.TcpTransport.SetUpSocket() in c:\BambooAgent\xml-data\build-dir\ETCH-RELEASE\binding-csharp\runtime\src\main\csharp\Etch\Util\TcpTransport.cs:line
193
>       at Etch.Util.Connection`1.Run0(Boolean first) in c:\BambooAgent\xml-data\build-dir\ETCH-RELEASE\binding-csharp\runtime\src\main\csharp\Etch\Util\Connection.cs:line
116
> Fix:
> In TcpTransport, a call is made to SetSocketOption with SocketOptionLevel.Tcp set.  The
correct SocketOptionLevel is .Socket, and this will fix the issue.  By setting it to .Tcp,
the socket sends a SO_BROADCAST which is invalid for TCP.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message