Running 6.1 developers edition on a desktop and getting the above error when I access the Java and JVM settings (java.cfm) and the Settings Summary (_jvmdata.cfm).
Any suggestions? Shawn McKee -----Original Message----- From: Robertson-Ravo, Neil (RX) [mailto:[EMAIL PROTECTED] Sent: Thursday, January 19, 2006 7:20 AM To: CF-Server Subject: RE: Server Stops Responding I am 99.9% certain that this is down to a JRun deadlock - it's no doubt down to the fact JRun is a server in limbo.. I reckon if you roll with Websphere or BEA (even Tomcat) the problems will go away! N -----Original Message----- From: Douglas Knudsen [mailto:[EMAIL PROTECTED] Sent: 19 January 2006 13:18 To: CF-Server Subject: Re: Server Stops Responding anything in the wsconfig logs? eg E:\JRun4\lib\wsconfig\1\LogFiles what about the jrun\logs? I'd rebuild the IIS connector with wsconfig and turn on the internal JRun server. If it happens again, try hitting the server via its internal server bypassing IIS, just to see. I have seen mucked up stuff with IIS that iisreset fixed up before too. Certainly back up your IIS metadirectory too. Once we had an issue with CFLDAP, it bomed its connection about 75% of the time. After hours of network checks, reseting IIS fixed it...wierd eh? DK On 1/19/06, Dave Hannum <[EMAIL PROTECTED]> wrote: > We're having a strange problem with one of our ColdFusion servers. We're > running on Win 2K3, IIS 6, CF 7.01 and Java 1.4.2_05. > > The web server will stop responding altogether. It will not serve up HTML > or CFM pages. Now, we've seen this before in the past, when the hook > between IIS and CF has been hosed up, but usually when used to see this, > JRun would go to 100% CPU and hang up. But with this problem, we're seeing > the opposite. JRun is running at almost 0% CPU when the web server stops > responding. There is no load on the box at all, during this time, and we're > getting a boat load of the following error: > java.net.SocketException: Connection reset by peer: socket write error > I know this can be cause by at least the following three reasons: > client's browser has been closed. > client's connection has been disconnected. > client presses the stop button. > > Now, short of rebooting the box, the system admins have tried disconnecting > and then reconnecting (via the Windows interface) the NIC. It seems to help > for a short time. During this time, you can still Remote Desktop in, so I > don't think it's a true NIC problem. It "feels" like a Windows/IIS issue > but we can't find anything in the logs to help us troubleshoot. I don't > think it's an actual NIC or NIC driver problem, because during this time, > you can still Remote Desktop in. If the box is completely re-booted, the > problem seems to go away for a couple of days, then it happens again. > > Has anyone seen anything like this before. Up to this point, this server > has been running quite well. Now this out of the blue. One thing I can > point to is that this problem "seemed" to start immediately after the latest > rounds of Windows updates - however the System Admins have rolled them back, > and it still persists - so I'm not sure if that was merely co-incidence or > not. > > Any input is appreciated. > > Kind Regards, > Dave Hannum > =============================== > David R. Hannum > Web Analyst/Programmer > Ohio University Computer Services > (740) 597-2524 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5815 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
