[
https://issues.apache.org/jira/browse/LUCENENET-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TJ Kolev updated LUCENENET-168:
-------------------------------
Attachment: TestRemoteSearchable.cs.patch
A patch is attached:
- Calls HttpChannel(0) constructor to get and bind to an available port
allocated by the system, rather than picking a port at rendom.
- Uses [TestFixtureSetUp] and [TestFixtureTearDown] to setup one server for
all tests in the fixture.
- A static variable for the remote type name, rather than a literal string.
tjk :)
> Sporadic failures in TestRemoteSearchable.cs
> --------------------------------------------
>
> Key: LUCENENET-168
> URL: https://issues.apache.org/jira/browse/LUCENENET-168
> Project: Lucene.Net
> Issue Type: Bug
> Environment: Windows Server 2003, .Net 3.5
> Reporter: TJ Kolev
> Priority: Trivial
> Attachments: TestRemoteSearchable.cs.patch
>
>
> NUnit test TestRemoteSearchable.cs fails with SocketException.
> Lucene.Net.Search.TestRemoteSearchable.TestPhraseQuery:
> System.Net.Sockets.SocketException : Only one usage of each socket address
> (protocol/network address/port) is normally permitted
> at
> System.Runtime.Remoting.Channels.Http.HttpServerChannel.StartListening(Object
> data)
> at System.Runtime.Remoting.Channels.Http.HttpServerChannel.SetupChannel()
> at System.Runtime.Remoting.Channels.Http.HttpServerChannel..ctor(Int32 port)
> at System.Runtime.Remoting.Channels.Http.HttpChannel..ctor(Int32 port)
> at Lucene.Net.Search.TestRemoteSearchable.SetUp() in
> D:\svn_lucene\src\Test\Search\TestRemoteSearchable.cs:line 47
> tjk :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
