.net - WCF Proxy Submit Crash - Kills Process -


i have simple wcf service accept data (wshttpbiding) , returns result. on client side dll containing proxy wrapper loaded , used build/submit request service.

this works in majority of cases, few users, submit call client proxy results in immediate crash of application (no errors, warnings, etc - process dies instantly)

the issue appears related users windows account: different users logged same machine not experience issue.

looking thoughts on might start looking culprit. ideas out there?

edit:

  1. i'm trying version trace statements , error logging in out affected machines @ moment. there no try/catch around .submit call, shouldn't exceptions propogate through call stack (the client/proxy dll being loaded directly primary app domain other exceptions such timeouts handed host application expected)
  2. web.config on server side below
  3. the users in same domain other users, default credentials being used. in house app, server on same network.

service web.config:

<system.servicemodel>     <behaviors>         <servicebehaviors>             <behavior name="services.eventsbehavior">                 <servicemetadata httpgetenabled="true" />                 <servicedebug includeexceptiondetailinfaults="true" />                 <servicethrottling maxconcurrentsessions="100" />             </behavior>             <behavior name="services.layoutsbehavior">                 <servicemetadata httpgetenabled="true" />                 <servicedebug includeexceptiondetailinfaults="true" />             </behavior>         </servicebehaviors>     </behaviors>     <services>         <service behaviorconfiguration="services.eventsbehavior" name="services.events">             <endpoint address="" binding="wshttpbinding" contract="services.ievents">                 <identity>                     <dns value="localhost" />                 </identity>             </endpoint>             <endpoint address="mex" binding="mexhttpbinding" contract="imetadataexchange" />             <host>                 <timeouts opentimeout="00:00:45" />             </host>         </service>         <service behaviorconfiguration="services.layoutsbehavior" name="services.layouts">             <endpoint address="" binding="wshttpbinding" bindingconfiguration="largerequestmsg" contract="services.ilayouts">             <identity>                 <dns value="localhost" />             </identity>             </endpoint>             <endpoint address="mex" binding="mexhttpbinding" contract="imetadataexchange" />         </service>     </services>     <bindings>         <wshttpbinding>             <binding name="largerequestmsg" maxreceivedmessagesize="5000000"></binding>         </wshttpbinding>     </bindings> </system.servicemodel> 

update: (2011/03/18) i've been able little testing (finally) , unfortunatly can't reproduce issue using test harness on client machine.

this leads me believe there funky going on in calling client dll (via com) causing issue.

any thoughts?

to more info, try turning on wcf trace, , using trace viwer utility read teh error messages, in case source wcf operation. here's link on how this, it`s not complicated. please note trace file can large. dont keep trace on more time need collcet data. (a dev machine ideal here, if possible)

one more thing, immediate crash no warning, because error happends on thread other gui`s main thread. (so wcf call indeed place start looking).


Comments

Popular posts from this blog

javascript - Enclosure Memory Copies -

php - Replacing tags in braces, even nested tags, with regex -