[Mono-dev] bug 352210
Hi, Does anyone know, or have a good estimation, when this bug regarding DateTime parsing is going to be checked in? Regards, Roei Erez ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Wapi handle leaks problems
Hi, Threads WAPI handle leaks has always caused problems with ASP.NET and MONO. In the past, there has been many bugs related to this problem... Now, we use mono to power our intranet (more than 4000 users...). I'm monitoring the number of wapi handles using mono --wapi=hps | wc -l During the day, the number of WAPI handles keeps stable. It seems that the GC collect them correctly... but during the night when our intranet is inactive the number of WAPI handles grows... and sometimes reach the limit of 4096... And crashes the mod-mono-server's... Two question : - why the number of WAPI handles grows... when there's no activity on the site (if the ASP.NET application has been very busy during the day... it will grows faster during the night) ? - don't you thing that a 4096 limit for WAPI handles is too small for big production servers? (on windows the number of handles is often 6000)? Thanks for helping me fixing this issue Hubert FONGARNAND I've a workaround: I use my monitoring system to send a request (that do a GC.Collect()) on each ASP.NET apps every 5 minutes Some graphs (without the 5 minutes ping) attachment: chart.php.png___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.9.0 Preview 2 is out!!
Hi! There seems to be a problem handling anonymous methods returning multidimensional arrays. I have submitted a bug report #363218 Best regards, Michał Ziemski Thomas Wiest pisze: Hey Everyone, We've just released Mono 1.9.0 Preview 2 today! This preview has Windows and Mac OS X installers. Please help us out by giving it a try with your applications. As always, you can get the preview releases here: http://mono.ximian.com/monobuild/preview/download-preview/ Please report any bugs that you may find using our Bugs page, AND reply to this thread with the bug numbers so we can track them! http://www.mono-project.com/Bugs The earlier you file the bugs and reply to this message, the more likely your bugs will get fixed. Special attention is given to regressions, so if you can tell us a version of Mono where the bug worked and you tag the summary of the bug with [Regression], then it is much more likely your bug will get fixed. Please help the Mono team to make 1.9.0 the best release of Mono ever. Thanks again! Mono QA ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] mono 1.9
Hi! Try http://www.mono-project.com/Class_Status Best regards, Michał Ziemski Scott Fluto pisze: I was wondering if anyone knows what percentage of support 1.9 has with regards to .net 3.0 and 3.5 , is there a place to see the percentage of method coverage it has or will have? thanks scott ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] fix for bug #358987 in 1.9?
Could someone make sure that the proposed patch gets applied to 1.9?
https://bugzilla.novell.com/show_bug.cgi?id=358987
Since applying it to our server (1.2.6), we've seen uptime for 12
days compared to less than 24 hrs before.
The fix is merely to put a try...catch around the statement that
closes the sockets even when shutdown fails (which it does when only
1 side of the socket is closed as in an abandoned connection).
Failing to close the socket causes a leak and eventually kills the
process as it runs out of file handles.
Index: HttpConnection.cs
===
--- HttpConnection.cs (revision 94904)
+++ HttpConnection.cs (working copy)
@@ -313,7 +313,11 @@
Socket s = sock;
sock = null;
- s.Shutdown (SocketShutdown.Both);
+ try {
+ s.Shutdown (SocketShutdown.Both);
+ } catch(Exception e) {
+ // log here?
+ }
s.Close ();
if (context_bound)
epl.UnbindContext (context);
The pushback has been that this problem should be solved upstream,
but this is a SAFE fix. Regardless of the implementation of Shutdown
(), Close() MUST be called to release resources associated with the
socket.
PLEASE add this fix to 1.9. Thanks.
- Steve
-
Steve G. Bjorg
MindTouch
555 W. Beech St.
Suite 501
San Diego, CA 92101
619.795.8459x1106 office
619.795.3948 fax
425.891.5913 mobile
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] mono 1.9
I'm pretty sure the support is 0%. Although we have implemented some of the 3.0 and 3.5 base class libraries, they are not shipped yet in our releases. These are done in our Olive module: http://www.mono-project.com/Olive. Oh, 1.9 will ship with nearly complete support for C# 3, but none of the base class libraries. Jonathan Scott Fluto wrote: I was wondering if anyone knows what percentage of support 1.9 has with regards to .net 3.0 and 3.5 , is there a place to see the percentage of method coverage it has or will have? thanks scott ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Performance improvement for System.Web.UI.Page.RegisterRequiresPostBack
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 18 Feb 2008 09:15:23 -0800 Vladimir Krasnov [EMAIL PROTECTED] wrote: Hello, Hello Vladimir, Please review and approve attached patch that improves Page.RegisterRequiresPostBack method, it will give up to 5% for controls that calls this method. Please commit, thanks! marek -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHvE4eq3909GIf5uoRAhcEAJkBz48splbR3OCRRttE1UwgIPISNgCfbVNq kul/En2iHfSeEm0FS40GmLk= =/8Lw -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] xsp issu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 20 Feb 2008 09:58:06 +0530 Sharique uddin Ahmed Farooqui [EMAIL PROTECTED] wrote: HI, Hi, I run with xsp2, it get this error. Server Error in '/' Application -- *Cannot cast from source type to destination type.* *Description: *Error processing request. *Error Message: *HTTP 500. System.InvalidCastException: Cannot cast from source type to destination type. *Stack Trace: * System.InvalidCastException: Cannot cast from source type to destination type. at System.DateTime.System.IConvertible.ToInt32 (IFormatProvider provider) [0x0] at System.Convert.ToInt32 (System.Object value, IFormatProvider provider) [0x0] at System.Convert.ToInt32 (System.Object value) [0x0] at System.Data.Common.AbstractDataContainer+Int32DataContainer.set_Item (Int32 index, System.Object value) [0x0] at System.Data.DataColumn.set_Item (Int32 index, System.Object value) [0x0] It's impossible to say what the issue is without the application source, but the problem in this case might be either in the data you feed System.Data with, or in System.Data itself. best regards, marek -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHvE6Wq3909GIf5uoRAjB1AJ0fWqjxa80U/Ugn4y1daO8WZZOrmACeMAp5 NZRRqEvmnbTmbeRnjVJSwZg= =1eQh -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] fix for bug #358987 in 1.9?
2008/2/20 Steve Bjorg [EMAIL PROTECTED]:
- s.Shutdown (SocketShutdown.Both);
+ try {
+ s.Shutdown (SocketShutdown.Both);
+ } catch(Exception e) {
+ // log here?
+ }
s.Close ();
Why call Shutdown() at all? The shutdown syscall is only useful if
you need to keep the fd around longer (eg. if someone else is still
holding onto it and you don't want it to be reused). In the above
code, close() shuts down the socket anyway.
...unless mono's socket code is doing something different than
standard C sockets, that is.
Have fun,
Avery
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] StackT performance
Hi, Attached is a small patch that gives a large performance improvement in the scenario where the stack is popped until empty. Notice that before the patch, whenever the stack reaches zero size it reallocates the array, even if the array is not null or 'zero length array'. Please review. Regards, Roei Erez stack_preformance.patch Description: stack_preformance.patch ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] fix for bug #358987 in 1.9?
Avery Pennarun wrote:
2008/2/20 Steve Bjorg [EMAIL PROTECTED]:
- s.Shutdown (SocketShutdown.Both);
+ try {
+ s.Shutdown (SocketShutdown.Both);
+ } catch(Exception e) {
+ // log here?
+ }
s.Close ();
Why call Shutdown() at all? The shutdown syscall is only useful if
you need to keep the fd around longer (eg. if someone else is still
holding onto it and you don't want it to be reused). In the above
code, close() shuts down the socket anyway.
Close(2) will fail with EINTR if there are still pending receptions
and/or sendings. That's why usually shutdown(2) is called, followed by
a loop until close(2) does not return EINTR anymore, because shutdown
does not kill current recvs/sends.
I don't know how mono is handling this internally but the patch
above looks OK to me. Even MSDN clearly states that Shutdown
must be called unless linger is turned on.
Robert
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] mono 1.9
On Wed, 2008-02-20 at 09:11 -0600, Jonathan Pobst wrote: I'm pretty sure the support is 0%. Although we have implemented some of the 3.0 and 3.5 base class libraries, they are not shipped yet in our releases. These are done in our Olive module: http://www.mono-project.com/Olive. Oh, 1.9 will ship with nearly complete support for C# 3, but none of the base class libraries. System.Core.dll should be in 1.9, which is required for such C# 3 features as extension methods and LINQ. - Jon ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] mono 1.9
hmm, so what I can gather then is that it will be pretty much 3.0 complete but just partially 3.5 complete given 3.5 has a lot of base class library enchantments? scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Pryor Sent: February-20-08 10:33 AM To: Jonathan Pobst Cc: Scott Fluto; mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] mono 1.9 On Wed, 2008-02-20 at 09:11 -0600, Jonathan Pobst wrote: I'm pretty sure the support is 0%. Although we have implemented some of the 3.0 and 3.5 base class libraries, they are not shipped yet in our releases. These are done in our Olive module: http://www.mono-project.com/Olive. Oh, 1.9 will ship with nearly complete support for C# 3, but none of the base class libraries. System.Core.dll should be in 1.9, which is required for such C# 3 features as extension methods and LINQ. - Jon ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] mono 1.9
so 1.9 will be c#3.0 and the .net 3.0/3.5(wpf,wcf...) will be coming from the olive project and they are on their own timeline then? is there a roadmap for the olive branch?? scott -Original Message- From: Jonathan Pobst [mailto:[EMAIL PROTECTED] Sent: February-20-08 11:36 AM To: Scott Fluto Cc: mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] mono 1.9 No, it will be pretty much 0% complete for 3.0 and 3.5. The ONLY post-2.0 piece that will be available is the C# compiler which will support the new C# 3 language features (such as extensions and partial LINQ support) and the one base class library needed to support this. It will not support any of the 3.0 base class libraries (WCF, WF, WPF) or any of the new 3.5 base class libraries (other than parts of System.Core.dll). I know its complicated, the thing to remember is C# 3 is not .Net 3.0 or .Net 3.5. It's just an enhancement to the language which shipped (ironically enough) in .Net 3.5. :) Hope this helps! Jonathan Scott Fluto wrote: hmm, so what I can gather then is that it will be pretty much 3.0 complete but just partially 3.5 complete given 3.5 has a lot of base class library enchantments? scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Pryor Sent: February-20-08 10:33 AM To: Jonathan Pobst Cc: Scott Fluto; mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] mono 1.9 On Wed, 2008-02-20 at 09:11 -0600, Jonathan Pobst wrote: I'm pretty sure the support is 0%. Although we have implemented some of the 3.0 and 3.5 base class libraries, they are not shipped yet in our releases. These are done in our Olive module: http://www.mono-project.com/Olive. Oh, 1.9 will ship with nearly complete support for C# 3, but none of the base class libraries. System.Core.dll should be in 1.9, which is required for such C# 3 features as extension methods and LINQ. - Jon ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] mono 1.9
No, it will be pretty much 0% complete for 3.0 and 3.5. The ONLY post-2.0 piece that will be available is the C# compiler which will support the new C# 3 language features (such as extensions and partial LINQ support) and the one base class library needed to support this. It will not support any of the 3.0 base class libraries (WCF, WF, WPF) or any of the new 3.5 base class libraries (other than parts of System.Core.dll). I know its complicated, the thing to remember is C# 3 is not .Net 3.0 or .Net 3.5. It's just an enhancement to the language which shipped (ironically enough) in .Net 3.5. :) Hope this helps! Jonathan Scott Fluto wrote: hmm, so what I can gather then is that it will be pretty much 3.0 complete but just partially 3.5 complete given 3.5 has a lot of base class library enchantments? scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Pryor Sent: February-20-08 10:33 AM To: Jonathan Pobst Cc: Scott Fluto; mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] mono 1.9 On Wed, 2008-02-20 at 09:11 -0600, Jonathan Pobst wrote: I'm pretty sure the support is 0%. Although we have implemented some of the 3.0 and 3.5 base class libraries, they are not shipped yet in our releases. These are done in our Olive module: http://www.mono-project.com/Olive. Oh, 1.9 will ship with nearly complete support for C# 3, but none of the base class libraries. System.Core.dll should be in 1.9, which is required for such C# 3 features as extension methods and LINQ. - Jon ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] mono 1.9
There isn't. Atsushi Eno Scott Fluto wrote: so 1.9 will be c#3.0 and the .net 3.0/3.5(wpf,wcf...) will be coming from the olive project and they are on their own timeline then? is there a roadmap for the olive branch?? scott -Original Message- From: Jonathan Pobst [mailto:[EMAIL PROTECTED] Sent: February-20-08 11:36 AM To: Scott Fluto Cc: mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] mono 1.9 No, it will be pretty much 0% complete for 3.0 and 3.5. The ONLY post-2.0 piece that will be available is the C# compiler which will support the new C# 3 language features (such as extensions and partial LINQ support) and the one base class library needed to support this. It will not support any of the 3.0 base class libraries (WCF, WF, WPF) or any of the new 3.5 base class libraries (other than parts of System.Core.dll). I know its complicated, the thing to remember is C# 3 is not .Net 3.0 or .Net 3.5. It's just an enhancement to the language which shipped (ironically enough) in .Net 3.5. :) Hope this helps! Jonathan Scott Fluto wrote: hmm, so what I can gather then is that it will be pretty much 3.0 complete but just partially 3.5 complete given 3.5 has a lot of base class library enchantments? scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Pryor Sent: February-20-08 10:33 AM To: Jonathan Pobst Cc: Scott Fluto; mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] mono 1.9 On Wed, 2008-02-20 at 09:11 -0600, Jonathan Pobst wrote: I'm pretty sure the support is 0%. Although we have implemented some of the 3.0 and 3.5 base class libraries, they are not shipped yet in our releases. These are done in our Olive module: http://www.mono-project.com/Olive. Oh, 1.9 will ship with nearly complete support for C# 3, but none of the base class libraries. System.Core.dll should be in 1.9, which is required for such C# 3 features as extension methods and LINQ. - Jon ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Wapi handle leaks problems
On Wed, 2008-02-20 at 09:51 +0100, Hubert FONGARNAND wrote: - don't you thing that a 4096 limit for WAPI handles is too small for big production servers? (on windows the number of handles is often 6000)? The shared memory part of io-layer is currently being rewritten to avoid the hard-coded limit (amongst other issues.) There is no timetable yet for its completion. - Dick signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono 1.9.0 Preview 2 is out!!
Hi, If possible this bug should be fixed in 1.9.0: [Date header should not be added by HttpResponse] https://bugzilla.novell.com/show_bug.cgi?id=363404 Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] WebServiceBindingAttribute bug in r72089?
When I upgrade mono from 1.2.6 to SVN HEAD, I get the following error making a webservice call: Unhandled Exception: System.InvalidOperationException: WebServiceBindingAttribute is required on proxy class 'Microsoft.TeamFoundation.Client.Authenticator' The class in question begins thusly: [System.Web.Services.WebServiceBindingAttribute(Name=ServerStatusSoap, Namespace=http://schemas.microsoft.com/TeamFoundation/2005/06/Services/ServerStatus/03;)] [System.Diagnostics.DebuggerStepThroughAttribute()] [System.ComponentModel.DesignerCategoryAttribute(code)] internal class Authenticator : System.Web.Services.Protocols.SoapHttpClientProtocol To get the class to work on SVN HEAD I had to make the following change: http://repo.or.cz/w/tfs.git?a=blobdiff;f=class/Microsoft.TeamFoundation.Client/Authenticator.cs;fp=class/Microsoft.TeamFoundation.Client/Authenticator.cs;h=49415b99a6e67c4c8ac8769787bf3e837dea14f2;hp=54fbe57736d23fa018840f0ebbf278c13acd35aa;hb=bec93a9ee5151193e6f1b41de8fe1667aadc0ba1;hpb=31e713085a865708a46ca82d7d2625b550332326 Basically, changing ServerStatusSoap to AuthenticatorSoap. I think the changeset which introduced this new behavior is r72089. http://lists.ximian.com/pipermail/mono-patches/2007-February/086979.html I'm a bit surprised that apparently now the attribute name must match the class name. That doesn't appear to be a requirement on this code sample at msdn2: http://msdn2.microsoft.com/en-us/library/system.web.services.webservicebindingattribute.aspx jr -- Joel Reed Manager, Leadership Software Engineering Development Dimensions International, Inc. (DDI) 1225 Washington Pike Bridgeville, PA 15017 412.257.3881 [EMAIL PROTECTED] ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono-devel-list Digest, Vol 34, Issue 38
As far as I know you in Mono can get column by index (int) not by name (string). Getting by name works in .NET but not in Mono. Looks like your supplying string and compiler is trying to cast it to int. Just a guess... Date: Wed, 20 Feb 2008 17:00:22 +0100 From: Marek Habersack [EMAIL PROTECTED] Subject: Re: [Mono-dev] xsp issu To: Sharique uddin Ahmed Farooqui [EMAIL PROTECTED] Cc: Zoltan Varga [EMAIL PROTECTED], mono-devel mono-devel-list@lists.ximian.com Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 20 Feb 2008 09:58:06 +0530 Sharique uddin Ahmed Farooqui [EMAIL PROTECTED] wrote: HI, Hi, I run with xsp2, it get this error. Server Error in '/' Application -- *Cannot cast from source type to destination type.* *Description: *Error processing request. *Error Message: *HTTP 500. System.InvalidCastException: Cannot cast from source type to destination type. *Stack Trace: * System.InvalidCastException: Cannot cast from source type to destination type. at System.DateTime.System.IConvertible.ToInt32 (IFormatProvider provider) [0x0] at System.Convert.ToInt32 (System.Object value, IFormatProvider provider) [0x0] at System.Convert.ToInt32 (System.Object value) [0x0] at System.Data.Common.AbstractDataContainer+Int32DataContainer.set_Item (Int32 index, System.Object value) [0x0] at System.Data.DataColumn.set_Item (Int32 index, System.Object value) [0x0] It's impossible to say what the issue is without the application source, but the problem in this case might be either in the data you feed System.Data with, or in System.Data itself. best regards, marek ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] WebServiceBindingAttribute bug in r72089?
joel reed wrote: When I upgrade mono from 1.2.6 to SVN HEAD, I get the following error making a webservice call: Unhandled Exception: System.InvalidOperationException: WebServiceBindingAttribute is required on proxy class 'Microsoft.TeamFoundation.Client.Authenticator' The class in question begins thusly: [System.Web.Services.WebServiceBindingAttribute(Name=ServerStatusSoap, Namespace=http://schemas.microsoft.com/TeamFoundation/2005/06/Services/ServerStatus/03;)] [System.Diagnostics.DebuggerStepThroughAttribute()] [System.ComponentModel.DesignerCategoryAttribute(code)] internal class Authenticator : System.Web.Services.Protocols.SoapHttpClientProtocol To get the class to work on SVN HEAD I had to make the following change: http://repo.or.cz/w/tfs.git?a=blobdiff;f=class/Microsoft.TeamFoundation.Client/Authenticator.cs;fp=class/Microsoft.TeamFoundation.Client/Authenticator.cs;h=49415b99a6e67c4c8ac8769787bf3e837dea14f2;hp=54fbe57736d23fa018840f0ebbf278c13acd35aa;hb=bec93a9ee5151193e6f1b41de8fe1667aadc0ba1;hpb=31e713085a865708a46ca82d7d2625b550332326 Basically, changing ServerStatusSoap to AuthenticatorSoap. I think the changeset which introduced this new behavior is r72089. http://lists.ximian.com/pipermail/mono-patches/2007-February/086979.html I'm a bit surprised that apparently now the attribute name must match the class name. That doesn't appear to be a requirement on this code sample at msdn2: http://msdn2.microsoft.com/en-us/library/system.web.services.webservicebindingattribute.aspx This is must likely this bug: https://bugzilla.novell.com/show_bug.cgi?id=360421 Robert ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] WebServiceBindingAttribute bug in r72089?
If Vladimir does not fix his regression, I'll revert r91075 tomorrow. Atsushi Eno Robert Jordan wrote: joel reed wrote: When I upgrade mono from 1.2.6 to SVN HEAD, I get the following error making a webservice call: Unhandled Exception: System.InvalidOperationException: WebServiceBindingAttribute is required on proxy class 'Microsoft.TeamFoundation.Client.Authenticator' The class in question begins thusly: [System.Web.Services.WebServiceBindingAttribute(Name=ServerStatusSoap, Namespace=http://schemas.microsoft.com/TeamFoundation/2005/06/Services/ServerStatus/03;)] [System.Diagnostics.DebuggerStepThroughAttribute()] [System.ComponentModel.DesignerCategoryAttribute(code)] internal class Authenticator : System.Web.Services.Protocols.SoapHttpClientProtocol To get the class to work on SVN HEAD I had to make the following change: http://repo.or.cz/w/tfs.git?a=blobdiff;f=class/Microsoft.TeamFoundation.Client/Authenticator.cs;fp=class/Microsoft.TeamFoundation.Client/Authenticator.cs;h=49415b99a6e67c4c8ac8769787bf3e837dea14f2;hp=54fbe57736d23fa018840f0ebbf278c13acd35aa;hb=bec93a9ee5151193e6f1b41de8fe1667aadc0ba1;hpb=31e713085a865708a46ca82d7d2625b550332326 Basically, changing ServerStatusSoap to AuthenticatorSoap. I think the changeset which introduced this new behavior is r72089. http://lists.ximian.com/pipermail/mono-patches/2007-February/086979.html I'm a bit surprised that apparently now the attribute name must match the class name. That doesn't appear to be a requirement on this code sample at msdn2: http://msdn2.microsoft.com/en-us/library/system.web.services.webservicebindingattribute.aspx This is must likely this bug: https://bugzilla.novell.com/show_bug.cgi?id=360421 Robert ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Wapi handle leaks problems
Le mercredi 20 février 2008 à 20:43 +, Dick Porter a écrit : On Wed, 2008-02-20 at 09:51 +0100, Hubert FONGARNAND wrote: - don't you thing that a 4096 limit for WAPI handles is too small for big production servers? (on windows the number of handles is often 6000)? The shared memory part of io-layer is currently being rewritten to avoid the hard-coded limit (amongst other issues.) There is no timetable yet for its completion. This is a great news... But for now our servers crashes each night... It could be good to track why the number of Handles grows on ASP.NET when there's no activity - Dick ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
