We have been seeing stability problems running non-Reactor apps on JRun... All I know is that our server administrators insist that we switch to IBM Websphere, but: I can't say we're having a memory leak problem, and I'm not certain the problems will go away on WAS ;-)
Wout On 5/23/06, Porter, Benjamin L. <[EMAIL PROTECTED]> wrote:
Our ATS guy just came to me yesterday with this exact issue. I did not stop to think it could be a reactor issue. So yes we are noticing it on a server under heavy load. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Kotek Sent: Tuesday, May 23, 2006 10:57 AM To: [email protected] Subject: Re: [Reactor For CF] Been out of touch, but trying to get back Doug, just wanted to let you know that I have not seen a memory leak in JRun yet. I'm using the latest from SVN. However, the apps aren't under heavy production use yet, so if it is something that comes up under load we wouldn't have seen it yet. Thanks, Brian On 5/23/06, Doug Hughes <[EMAIL PROTECTED]> wrote: Hey guys. This is just a quick update on what's been up with reactor lately and where I'm headed: I haven't had the time to keep up with the mailing list and I haven't been tracking bugs. I know this is bad. I'm working on resolving this. To help with this I will be moving the SVN repo to Simeon's servers (more on this soon). Simeon also provides Trac so we will have a public bug tracker. I'll be using the site to create an official roadmap so you're not blindsided by where the project's headed. This will tell us how we're going to get from here to beta to RC to 1.0. I need to build this out, but it'll happen soon. Also, Adobe donated RoboHelp to the cause. I'll be setting that up as a server eventually and proving access to some people to write documentation. About bug fixes…. Right now I'm working on two big ones. The biggest is a possible memory leak. Those who've tried to access my blog recently may have noticed it's been flakey. I've been battling a memory leak that takes down the instance that my blog is running in. Right now I don't know if the leak is in Reactor or elsewhere. But, I have a few sites that have similar problems and one unifying factor is Reactor. This is taking up all my time right now. I could really use help with this too. Has anyone else noticed their jrun server choking up with all it's ram being allocated? Does anyone have a feel as for where this might be? Have you NOT experienced this problem? The other big thing relates to OO queries. There are a few logical errors in the API. I'm not going to get into the details on this, but I need to address this in a big way. More on this later too. Thanks for understanding guys. More updates to follow over the next couple days. Doug -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. *************************************************************************** -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
-- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
