Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

ERROR: "Connection Closed." while starting the Elastic search server in MDM
Problem Description
In Master Data Management (MDM), during the server startup, elastic search server is unable to start due to which indices fail to get generated.

​14:57:27,681 INFO  [com.informatica.mdm.sss.ElasticSearchConfigListener] (pool-30-thread-2) ##########################################################
14:57:27,728 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241) [2019-03-20 14:57:27,728] [pool-24-thread-3] [WARN ] com.delos.cmx.server.interact.caller.InteractCleanseClient: Response did not return any content type

14:57:29,978 ERROR [com.informatica.search.ElasticSearchSchemaMap] (pool-30-thread-2) ++++ Get Index Exception
14:57:29,978 ERROR [com.informatica.search.ElasticSearchSchemaMap] (pool-30-thread-2) ++++ mapping Query Exception
14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241) [2019-03-20 14:57:29,978] [pool-30-thread-2] [ERROR] com.informatica.mdm.sss.searchEngine.es.SmartSearchESIndexProcessor: Error while uploading configsConnection closed

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241) com.informatica.http.ConnectionClosedException: Connection closed

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.nio.protocol.HttpAsyncRequestExecutor.endOfInput(HttpAsyncRequestExecutor.java:344)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:261)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at com.informatica.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241)  at java.lang.Thread.run(Unknown Source)

14:57:29,994 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-241) [2019-03-20 14:57:29,994] [pool-30-thread-2] [WARN ] com.siperian.common.ExternalMsgUtil: Could not find the following error code: SIP-52075

14:57:29,994 ERROR [com.informatica.mdm.sss.ElasticSearchConfigListener] (pool-30-thread-2) SIP-52075: Connection closed
Connection closed
Connection closed: com.siperian.common.SipException: SIP-52075: Connection closed
Connection closed
Connection closed
at com.informatica.mdm.sss.searchEngine.es.SmartSearchESSchemaProcessor.generateBusinessEntityESMappings(SmartSearchESSchemaProcessor.java:89) [siperian-server-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.mdm.sss.searchEngine.es.SmartSeachES.generateIndexSchema(SmartSeachES.java:49) [siperian-server-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.mdm.sss.ElasticSearchConfigListener.onRepositoryChange(ElasticSearchConfigListener.java:31) [siperian-server-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.mdm.util.RepositoryChangeMonitorThread$ListenerInvoker.call(RepositoryChangeMonitorThread.java:93) [siperian-server-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.mdm.util.RepositoryChangeMonitorThread$ListenerInvoker.call(RepositoryChangeMonitorThread.java:71) [siperian-server-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.8.0_201]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) [rt.jar:1.8.0_201]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [rt.jar:1.8.0_201]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_201]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_201]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_201]
Caused by: com.informatica.http.ConnectionClosedException: Connection closed
at com.informatica.http.nio.protocol.HttpAsyncRequestExecutor.endOfInput(HttpAsyncRequestExecutor.java:344) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:261) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
at com.informatica.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588) [search-elasticsearch-10.3.0-SNAPSHOT.jar:10.3.0.0.0.0.7448529]
... 1 more​
Cause
​​During the server startup, the MDM Hub made an attempt to connect to the Elastic search server through the URL defined in the Provisioning Tool.
and in the Provisioning tool, the ES URL must be in HTTPs and the port should be 9200 (It will not be HTTP).

This issue is caused when the ES URL is configured as HTTP.
Solution
To resolve this issue, change the URL to HTTPs in the provisioning tool, publish the changes and validate the Operational Reference Store (ORS).

Log in to Provisioning Tool -> Click Configuration > go to InfraStructure Setting > Choose the ESCluster > In the URL section, correct it.
More Information
Applies To
Product: MDM Multidomain
Problem Type: Configuration
User Type: Developer
Project Phase: Implement
Product Version:
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:6/18/2019 12:25 AMID:572765
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)