none
WCF LOB Adapter SDK IInboundHandler System.ArgumentNullException Value cannot be null RRS feed

  • Question

  •  

    This is happening with my WCF LOB Adapter existing within a BizTalk 2006 R2 receive location. 

    The interaction between TryReceive, WaitForMessage still isn't clear to me.

    Any ideas on what's causing, and how to fix, error below?

     

    System.ArgumentNullException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

     

    Value cannot be null.
    Parameter name: message

     

    System.ServiceModel.Dispatcher.EndpointAddressMessageFilter.Match(Message message)
    System.ServiceModel.Dispatcher.EndpointDispatcherTable.LookupInCache(Message message, Boolean& addressMatched)
    System.ServiceModel.Dispatcher.EndpointDispatcherTable.Lookup(Message message, Boolean& addressMatched)
    System.ServiceModel.Dispatcher.ChannelHandler.GetSessionChannel(Message message, EndpointDispatcher& endpoint, Boolean& addressMatched)
    System.ServiceModel.Dispatcher.ChannelHandler.EnsureChannelAndEndpoint(RequestContext request)
    System.ServiceModel.Dispatcher.ChannelHandler.TryRetrievingInstanceContext(RequestContext request)
    System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(RequestContext request, OperationContext currentOperationContext)
    System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
    System.ServiceModel.Dispatcher.ChannelHandler.OnAsyncReceiveComplete(IAsyncResult result)
    System.ServiceModel.Diagnostics.Utility.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
    Microsoft.ServiceModel.Channels.Common.Design.AdapterAsyncResult.SignalFinished(Object finishedResult, Exception finishedException)
    Microsoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel.TryReceiveAsyncCall(Object obj)
    System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
    System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

    Thursday, March 20, 2008 10:02 PM

Answers

  • hi

    regarding the null reference exception, have you verified that whenever tryreceive returns true, you have set the out message parameter to a valid message?

    regarding waitformessage: if you set supportstransactedinbound=true, then, WCF will first call waitformessage, and when it returns true, it will then start a transaction, and within that scope call tryreceive.
    Friday, March 21, 2008 4:15 PM