Skip to Main Content

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Integrator Bulk Add to domain problem - All settings seem correct but Getting error: "SEVERE: Couldn

NickelausJan 14 2015 — edited Jan 20 2015

While trying to Bulk Add/Replace records I'm getting an error back which says:

"

com.endeca.BulkLoad.BulkIngester logError

SEVERE: Couldn't connect to ourservername:15150

"

We're using Endeca Integrator  3.1.1 and Endeca Server Server 7.6. Endeca Server is running on Oracle Linux 64-bit. Local Integrator client on Windows 7. Running Endeca server on a cluster of 3. I believe this Oracle is in Production mode.

I've made sure the EndecaServer.properties file only has the short name (not fully qualified) and that the /etc/hosts is listing the actual server name first in the list as recommended here:

I can get the Reset Data Domain to execute successfully.

The message in context is this:

------------------------------------------ Error details -------------------------------------------

  Component [Bulk Add/Replace Records:BULK_ADD_REPLACE_RECORDS] finished with status ERROR.

   Component pre-execute initialization failed.

    Failed with the following IntegratorException:

    com.endeca.clover.adapters.exception.IntegratorException: Exception creating the BulkIngester:

    java.io.IOException: Couldn't connect to uspsicvslx1055:15151

   Failed with the following IntegratorException:

    com.endeca.clover.adapters.exception.IntegratorException: Exception creating the BulkIngester:

    java.io.IOException: Couldn't connect to uspsicvslx1055:15151

----------------------------------------------------------------------------------------------------

The /etc/hosts file now looks like this:

10.2.276.28     myhostname.oursite.com myhostname

127.0.0.1       localhost

What could be causing this error beyond what I've already addressed?  Is there somewhere I should check. It seems weird that I should not use the fully-qualified name in the EndecaServer.properties file - but this is what version 7.6 requires, correct?

Any ideas or other areas I should check?

This post has been answered by Branchbird - Pat on Jan 18 2015
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 17 2015
Added on Jan 14 2015
10 comments
2,492 views