My Oracle Support Banner

UnknownHostException when starting component on EAC client server (Doc ID 1042336.1)

Last updated on MAY 01, 2018

Applies to:

Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 5.1.0 and later
Information in this document applies to any platform.

Symptoms

When you attempt to start a dgraph or logserver on an EAC client, the dgraph or logserver process fails to start and is shut down by the EAC after a timeout expires. On UNIX, the ps utility reports the dgraph or logserver process as being in a <defunct> state. 

An error similar to this appears in the Deployment Template application log, [app_dir]/log/app.0.0.log: 

Feb 11, 2008 1:10:19 AM com.endeca.soleng.eac.toolkit.Controller execute 
SEVERE: Caught an exception while invoking method 'run' on object 'BaselineUpdate'. Releasing locks. 
java.lang.reflect.InvocationTargetException 
... 
Caused by: com.endeca.soleng.eac.toolkit.exception.AppControlException: Error executing valid BeanShell script. 
... 
Caused by: com.endeca.soleng.eac.toolkit.exception.AppControlException: Error executing valid BeanShell script. 
... 
Caused by: com.endeca.soleng.eac.toolkit.exception.EacComponentControlException: Server component 'Dgraph1' failed to start. Refer to component logs in [app_dir]/./logs/dgraphs/Dgraph1 on host MDEXHost3. 
... 


An error similar to the following appears in the [ENDECA_CONF]/logs/process.0.log file: 

INFO: Starting dgraph 'Dgraph1' 
Feb 11, 2008 2:37:40 PM com.endeca.esf.delegate.procctrl.ProcessControlImpl startProcess 
INFO: Starting process for TaskId(COMPONENT,prod1,Dgraph1): /usr/local/endeca/5.1.2/i86pc-linux/bin/dgraph "--port" "8000" 
Feb 11, 2008 2:37:41 PM com.endeca.esf.delegate.task.ProcessHandlePollingTask startProcess 
INFO: Started process 8335 for dgraph 'Dgraph1' 
Feb 11, 2008 2:39:42 PM com.endeca.esf.delegate.task.ServerTask setFailedStatus 
SEVERE: dgraph 'Dgraph1' has finished with status Failed - Startup of dgraph 'Dgraph1' lasted longer than timeout and was shutdown. 


An error similar to the following appears in the [ENDECA_CONF]/logs/invoke.0.log file: 

Feb 11, 2008 2:58:01 PM ScriptControlPortSOAPBindingImpl 
SEVERE: 'Get script status' request encountered an error for script 'WeeklyHtmlReports' in application 'prod1' 
com.endeca.esf.shared.EsfException: Error connecting to http://localhost:8888/eac-agent/IDelegateServer: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Couldn't send message. 
... 
Caused by: org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Couldn't send message. 
... 
Caused by: org.codehaus.xfire.fault.XFireFault: Couldn't send message. 
... 
Caused by: org.codehaus.xfire.XFireException: Couldn't send message. 
... 
Caused by: java.net.UnknownHostException: localhost 
... 


An error similar to the following appears in the [ENDECA_CONF]/logs/main.0.log file: 

Feb 11, 2008 2:58:01 PM ScriptControlPortSOAPBindingImpl 
SEVERE: 'Get script status' request encountered an error for script 'BaselineUpdate' in application '<APPNAME>' 
com.endeca.esf.shared.EsfException: Error connecting to http://localhost:8888/eac-agent/IDelegateServer: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Couldn't send message. 
... 
Caused by: org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Couldn't send message. 
... 
Caused by: org.codehaus.xfire.fault.XFireFault: Couldn't send message. 
... 
Caused by: org.codehaus.xfire.XFireException: Couldn't send message. 
... 
Caused by: java.net.UnknownHostException: localhost 
... 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.