Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(2 Ratings)
facebook Twitter
Print Bookmark Alert me when this article is updated


ERROR: "Argument msgEnum cannot be null. Mirror Batcher: Unknown exception occurred" when Model Repository Service becomes unresponsive while accessing the object
Problem Description
While modifying or saving any object from MRS through Developer tool, Developer tool hangs and logs the following error stack into log.

MRS log:

SEVERE 17831 Async Mirror Thread MRS_0001] Argument 'msgEnum' cannot be null. "Mirror Batcher: Unknown exception occurred. " 


com.informatica.core.exception.IllegalArgumentException: [CORE_0001] Argument 'msgEnum' cannot be null. 

at com.informatica.core.exception.IllegalArgumentException.createNullArgumentException( 

at com.informatica.core.exception.ExceptionDelegate.<init>( 

at com.informatica.core.exception.UncheckedException.<init>( ​


The exception stacks seem to occur during index synchronization of MRS. If the index files are corrupted, it may report exceptions.

​​​MRS Stack Trace shows that it is performing index operation at the time of issue. 

"Thread-21" prio=10 tid=0x00007fbb68f79000 nid=0x6be2 waiting on condition [0x00007fbbd1f2b000]

   java.lang.Thread.State: TIMED_WAITING (parking)

at sun.misc.Unsafe.park(Native Method)

- parking to wait for  <0x00000000ccb81638> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)

at java.util.concurrent.locks.LockSupport.parkNanos(

at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(

at java.util.concurrent.ThreadPoolExecutor.awaitTermination(

at org.apache.solr.common.util.ExecutorUtil.shutdownNowAndAwaitTermination(

at org.apache.solr.update.UpdateLog.close(

- locked <0x00000000ccb81fc8> (a org.apache.solr.update.UpdateLog)

at org.apache.solr.update.UpdateLog.close(

at org.apache.solr.update.DirectUpdateHandler2.closeWriter(

at org.apache.solr.update.DefaultSolrCoreState.closeIndexWriter(

at org.apache.solr.update.DefaultSolrCoreState.close(

- locked <0x00000000ce1718f8> (a org.apache.solr.update.DefaultSolrCoreState)

at org.apache.solr.update.SolrCoreState.decrefSolrCoreState(

at org.apache.solr.core.SolrCore.close(

at org.apache.solr.core.CoreMaps.clearMaps(

at org.apache.solr.core.CoreContainer.shutdown(

at org.apache.solr.client.solrj.embedded.EmbeddedSolrServer.shutdown(

at com.informatica.searchservice.service.impl.SolrServerWrapper.shutdown(

at com.informatica.searchservice.service.impl.EmbeddedSolrServerWrapper.shutdown(

at com.informatica.searchservice.service.impl.EmbeddedSolrServerLocator.shutdown(

- locked <0x00000000cb663e68> (a com.informatica.searchservice.service.impl.EmbeddedSolrServerLocator)


- locked <0x00000000cad194e8> (a



​​​Clear the Search Index for MRS service from the server location.




1. Go to Informatica Administrator console. 

2. Stop/Disable the MRS service. 

3. MRS->Process Tab->SearchIndexRootDir-> "Path". Default value: ./target/repository/1524054085176/<MRS_NAME>/index

4. Go to Server location "Path" of SearchIndexDir.

5. Take a backup of "searchdata" directory into another directory. 

6. Delete the directory under index (that is, searchdata). 

7. Start the MRS service and verify if the messages are gone or still logging into MRS log. 

More Information
​​./target means <INFA_HOME>\tomcat\bin\target.
Applies To
Product: Data Quality
Problem Type:
User Type:
Project Phase:
Product Version:
Operating System:
Other Software:

Last Modified Date:1/9/2019 9:34 PMID:502274
People who viewed this also viewed


Did this KB document help you?

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