[Mono-dev] WCF: ObjectDisposedException in System.ServiceModel.Channels

[Atsushi Eno]

Hello,

That sounds like a cool set of fixes :)

Either this list or bugzilla is okay for me.

Atsushi Eno

On 2010/03/20 2:55, Matt Dargavel wrote:
> I've found the problem and I have a few patches to submit.  The patches
> cover the following:
>
> * Some fixes for the issue I was seeing below (some multithreaded timing
> issues).
> * A change to make the check against ?wsdl case insensitive for the root
> wsdl page, after that you should follow the include links anyway.  This
> appears to be more consistent with the way .NET works.
> * A change to the property handling of
> TransactionChannelListener<TChannel>  and ChannelListenerBase to fix a
> problem with the MetadataPublishingInfo property.  This patch probably
> requires some extra explanation / discussion.
> * A change to ServiceHostBase so that ApplyDescription can add base
> addresses (a problem I noticed when using config files).
>
> I've made the changes against tip, although I've also tried the
> resulting dll with 2.6 (.1) and it seems to work fine.
>
> Do you have a preference as to how I submit the patches?
>
> 	Regards,
>
> 		Matt.
>
>
>    
>> -----Original Message-----
>> From: Atsushi Eno [mailto:atsushieno at veritas-vos-liberabit.com]
>> Sent: 12 March 2010 3:25 AM
>> To: Matt Dargavel
>> Cc: mono-devel-list at lists.ximian.com
>> Subject: Re: [Mono-dev] WCF: ObjectDisposedException in
>> System.ServiceModel.Channels
>>
>> Hello,
>>
>> There are few things I can say from your input, but 1) I have never
>> heard of this kind of problem
>> and 2) trunk is way better than 2.6.
>>
>> Atsushi Eno
>>
>> On 2010/03/12 1:09, Matt Dargavel wrote:
>>      
>>> Hi there,
>>>
>>> I've found an issue in Mono 2.6.0 using a self hosted WCF service
>>>        
> and
>    
>>> was wondering if anyone had seen this before (Mono trace below).
>>>
>>> It appears to be caused by firing in a request to the Service that
>>> takes a long time and while that request is still running firing in
>>> another one. I've tried with both a Singleton service instance with
>>> ConcurrencyMode.Single and a service host with a type and
>>> ConcurrencyMode.Multiple but both seem to have the same problem.
>>>
>>> I'm just trying the latest svn and will try to pinpoint the issue,
>>>        
> but
>    
>>> any help / pointers would be appreciated!
>>>
>>> Regards,
>>>
>>> Matt.
>>>
>>> Trace:
>>>
>>>        
>
>
>