Unable to connect to the remote server error

[R. Tan]

Hi guys,

I'm getting an exception while in the middle of a batch indexing job. Can anybody help me figure this out?

Error: Only one usage of each socket address (protocol/network address/port) is normally permitted 127.0.0.1:8080

Solr is 1.4 on Tomcat.

Big thanks.

Rihaed

[steinar]

I was just about to post regarding the exact same(?) problem.

Whats happening is that i get the error message (in VS):
"A first chance exception of type
'SolrNet.Exceptions.SolrConnectionException' occurred in SolrNet.DLL"
And the web browser (which i use to start the feed says:
"System.Data.SqlClient.SqlException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
not responding."

At the time of writing my index contains 15k docs, and "lacks" ~700k
docs that the incremental feed should take care of adding to the
index.
The error message appears between 3k docs are added, and before 4k
docs are added.
I'm committing each 1%1000==0.
In addittion autocommit is set to:
<autoCommit>
<maxDocs>10000</maxDocs>
</autoCommit>

More info:
From schema.xml:
<field name="id" type="text" indexed="true" stored="true"
required="true" />
<field name="name" type="string" indexed="true" stored="true"
required="false" />
I'm fetching data from a (remote) Sql 2008 Server, using sqljdbc4.jar.
And Solr is running on a local Tomcat-installation.
SolrNet version: 0.2.3.0
Solr Specification Version: 1.3.0.2009.08.29.08.05.39

Rihaed, did you figure out anything to solve this problem?
Any suggestions on how to fix this would be much apreceiated.


Regards, Steinar

[Mauricio Scheffer]

These problems seem to be unrelated.
Rihaed's error looks like a IP/port binding issue with Tomcat.
Your exception is a SQL timeout, probably due to a long query, try
increasing the timeout limit.

[steinar]

Hi Mauricio.
Thanks for your swift response.
Indeed you are right in that my problem is database(connection)
related.
I tried to run the app localy on the db-server instead of on a given
port on the db-server, and the problem seems to be gone (sadly
replaced with another one tho).

But as I learned yday, the index that are giving me problems seems to
be redundant, so I'm all ok anyway.

Thanks,
Steinar

On 28 Sep, 17:07, Mauricio Scheffer <mauricioschef...@gmail.com>
wrote: