none
FSIS IMS Flow federation over ESP is failing when one ESP returns 0 hits. RRS feed

  • Question

  • Hello!!

    I am working with an IMS Flow that sends a simple query to 2 different Collections in one ESP server (it will change to a different ESP Servers for production) 

    The search was executed correctly according with esp querylogs.  The same query goes directly to both instances and the first one returns several documents but the second does not have any hit.

    Here is the stacktrace of the exception:

    2011-01-14 04:17:25.978Z  Info    [44] Microsoft.Ceres.ContentEngine.Component.ContentIntegrationComponent - Evaluation Warning: Failing cause Microsoft.Ceres.Evaluation.DataModel.EvaluationException: Evaluation failed in operator SearchResultMixer of type SearchResultMixer ---> System.ArgumentNullException: Value cannot be null.
    Parameter name: key
       at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
       at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
       at System.Collections.Generic.Dictionary`2.ContainsKey(TKey key)
       at Microsoft.Ceres.InteractionEngine.Operators.BuiltIn.SearchResultMixerOperator.MixResultsRelevancy(ContextModifierList`1 mixedResults, IList`1 resultsList, String relevancyField, IDictionary`2 multipliersDictionary)
       at Microsoft.Ceres.InteractionEngine.Operators.BuiltIn.SearchResultMixerOperator.MixResults(ImsSearchResultsGroup resultGroup, MixerConfiguration mixerConfiguration)
       at Microsoft.Ceres.InteractionEngine.Operators.BuiltIn.SearchResultMixerOperator.TransformContext(Context context)
       at Microsoft.Ceres.InteractionEngine.Processing.BuiltIn.ContextTransformationEvaluator`1.ContextTransformationProducer.ProcessRecord(IRecord record)
       at Microsoft.Ceres.Evaluation.Processing.Producers.ProducerRecordSetSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Engine.ErrorHandling.HandleExceptionRecordSetSink.Put(IRecord record)
       --- End of inner exception stack trace ---
       at Microsoft.Ceres.Evaluation.Engine.ErrorHandling.HandleExceptionRecordSetSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Processing.AbstractSequenceIdJoinEvaluator`1.RecordComplete(IRecord lastInput, Int32 lastInputSource)
       at Microsoft.Ceres.Evaluation.Processing.AbstractSequenceIdJoinEvaluator`1.RecordArrived(IRecord record, Int32 source)
       at Microsoft.Ceres.Evaluation.Processing.AbstractSequenceIdJoinEvaluator`1.MergeSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Engine.ErrorHandling.HandleExceptionRecordSetSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Processing.Producers.ProducerRecordSetSink.PushToOutput()
       at Microsoft.Ceres.Evaluation.Engine.ErrorHandling.HandleExceptionRecordSetSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Processing.Producers.ProducerRecordSetSink.PushToOutput()
       at Microsoft.Ceres.Evaluation.Engine.ErrorHandling.HandleExceptionRecordSetSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Processing.Producers.ProducerRecordSetSink.PushToOutput()
       at Microsoft.Ceres.Evaluation.Engine.ErrorHandling.HandleExceptionRecordSetSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Processing.Producers.ProducerRecordSetSink.PushToOutput()
       at Microsoft.Ceres.Evaluation.Engine.ErrorHandling.HandleExceptionRecordSetSink.Put(IRecord record)
       at Microsoft.Ceres.Evaluation.Engine.PushPull.PushPullThread.DoRunPushPull()
       at Microsoft.Ceres.Common.Utils.Concurrent.PoolTaskWrapper.Run()

     

    This workflow is working fine when both searches return at least 1 hit, but if one of them returns an emptyresultset, the flow throws the previous exception.

    Am I missing a simple configuration parameter to just ignore empty result sets from ESP? 

     

    Thanks,

    Iriana Arguedas.

    Friday, January 14, 2011 5:05 AM

All replies

  • This exception happens with Relevancy MixerType.  Using RoundRobin MixerType works fine.
    Friday, January 14, 2011 6:12 PM
  • Hi Iriana,

     

    We have verified that this is a product issue, and we've reported the problem to our development team.

     

    Thanks,

     

    Patrick Schneider

    Support Escalation Engineer

     

    Wednesday, February 2, 2011 1:32 PM
  • Hi Patrick,

    Do we have any update or bug number to define this error ?

    Regards

    Thursday, December 27, 2012 3:08 PM
  • Hello,

    This issue was resolved well over a year ago with patch02.

    Thanks,

    Patrick Schneider


    Patrick Schneider | Microsoft | Enterprise Search Group | Support Escalation Engineer | http://www.microsoft.com/enterprisesearch

    Friday, December 28, 2012 8:54 AM