Hi Trygve,
When I hear symptoms such as this I think "memory leak" as a first thought.
Have you tried monitoring resources on the server in question - does it
lose memory over time after repeated requests? Can you isolate this to
which part of your code is leaking (e.g. is the MySQL call leaking, is the
MySQL database leaking? Is IIS leaking? Check and compare in the process
table to see what is growing and growing and growing). Is the thread pool
exhausted?
Just some thoughts
Dan Rogers
Microsoft Corporation
--------------------
From: "Trygve Lorentzen" <trygveloAThaldenDOTnet>
Subject: Get "System.InvalidOperationException: Request format is
unrecognized" after running a while
Date: Mon, 8 Nov 2004 18:39:46 +0100
Lines: 26
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Message-ID: <ec**************@TK2MSFTNGP11.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: c5100a786.sdsl.catch.no 81.0.167.134
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP11
.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:7299
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
Hi,
my webservice is running on Win2000 SP4, IIS 5.0 fully patched, connecting
to a MySQL database and mainly returning Typed DataSet's from webmethods.
After running for a while, generally a few days, the webservice stops
responding and the .NET windows app client fails with no informative error
message. When I try to run any webmethod from the webservice locally in the
browser I first get a "This page cannot be display IE error message", but
when I hit reload I get a familiar .NET webservice error page stating:
"System.InvalidOperationException: Request format is unrecognized".
Anyone have the slightest ideas what this could be. It runs fine for several
days and suddenly this happens. I got 2 other webservices on the same box
that doesn't seem to be affected, but the number of requests to those are
much smaller, so I might not have hit the "fail-treshold" number of requests
yet.
If you don't have any idea what this might be I'd also like suggestions on
how I should go forward with debugging this issue...!
Any help will be greatly appreciated, I'm getting desperate.
Cheers,
Trygve