We are aware of this problem (not only codebehind). I think there's
already a bug report for it.
Is this problem being actively chased? We cannot use XSP or mod_mono for
any serious work because it hangs after 10 or so requests (it varies).
This is often not even enough to load a whole page. Do
El lun, 15-03-2004 a las 15:47, David Mitchell escribió:
We are aware of this problem (not only codebehind). I think there's
already a bug report for it.
Is this problem being actively chased? We cannot use XSP or mod_mono for
any serious work because it hangs after 10 or so requests
I don't know if this will have anything to do with it, but all the
machines we are running here use RedHat 9.
--
David Mitchell
Software Engineer
Telogis
NOTICE:
This message (including any attachments) contains CONFIDENTIAL
INFORMATION intended for a specific individual and purpose, and
is
Juraj Skripsky wrote:
Hi David,
What version of glibc do you have? Try updating to the latest version
(2.3.2-27.9.7).
I've had similar problems with mono on several machines which were all
running freshly installed RH9. XSP was hanging sometimes.
The same application ran perfectly on two other
I have been trying to understand the problem with XSP stopping responding.
I don't believe it's an XSP problem, I think it's a mono problem.
All the managed threads stop running. (I added a monitor thread to
XSP). Thus it seems like a deadlock somewhere in mono could be the problem.
Another
I'm running an ASP.Net application through XSP on the CVS version of
mono. XSP has a habit of simply stopping after a few pages have been
requested from it. I can still close it with Ctrl-C. Basically it just
serves a few pages and then all managed code stops executing. Has anyone
else
More on this, after running this under different environments (Windows
w/ .Net) and trying various apps I've discovered this only happens when
running on mono and running a codebehind page. Even the codebehind test
page in the xsp package has this freezing problem. This fails on
mod_mono too.
I've discovered this only happens when
running on mono and running a codebehind page.
Ok, I'm wrong. This isn't limited to codebehind and this happens on any
of the xsp tests. Try opening any of the xsp tests in your browser
(through xsp of course). Say server-side-object.aspx, but it doesn't
El dom, 14-03-2004 a las 21:35, David Mitchell escribió:
More on this, after running this under different environments (Windows
w/ .Net) and trying various apps I've discovered this only happens when
running on mono and running a codebehind page. Even the codebehind test
page in the xsp
