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

2010-03-20 Thread Atsushi Eno
gt; Matt. > > > >> -Original Message- >> From: Atsushi Eno [mailto:atsushi...@veritas-vos-liberabit.com] >> Sent: 12 March 2010 3:25 AM >> To: Matt Dargavel >> Cc: mono-devel-list@lists.ximian.com >> Subject: Re: [Mono-dev] WCF: ObjectDisp

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

2010-03-19 Thread Matt Dargavel
mit the patches? Regards, Matt. > -Original Message- > From: Atsushi Eno [mailto:atsushi...@veritas-vos-liberabit.com] > Sent: 12 March 2010 3:25 AM > To: Matt Dargavel > Cc: mono-devel-list@lists.ximian.com > Subject: Re: [Mono-dev

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

2010-03-15 Thread Matt Dargavel
- > From: Matt Dargavel > Sent: 15 March 2010 3:58 PM > To: 'Atsushi Eno' > Cc: mono-devel-list@lists.ximian.com > Subject: RE: [Mono-dev] WCF: ObjectDisposedException in > System.ServiceModel.Channels > > I've tried the trunk version and it's stil

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

2010-03-15 Thread Matt Dargavel
0 3:25 AM > To: Matt Dargavel > Cc: mono-devel-list@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

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

2010-03-11 Thread Atsushi Eno
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 wonde

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

2010-03-11 Thread Matt Dargavel
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 firin