While certainly not as well characterized we are noticing a similar
problem, associated with frequent development restarts causing issues with
ports being in use.
At 12:17 PM 1/16/2001 +0000, you wrote:
>Hi,
> This is probably one for JRun's Dev Team, I've been having seemingly
>random problems with JRun 3.0 running as a service causing a Dr Watson on
>the javaw.exe.
>
>Problems seem to appear when the following happens:
>
>Changing a class, recompiling and changing a jsp page and restarting the
>server (via admin tool or services control panel it doesn't matter) and then
>a Dr Watson occures upon recompilaion of the jsp
>
>To fix you need to kill the javaw.exe process via a taskmgr.exe started with
>system privileges - being a serveice started with system account.
>
>That is to say, it appears that Jrun detects a fault and starts another
>javaw.exe, but the crashed one seems to hang around causing problems like,
>when you request a page in this state the request just hangs at the browser
>and is not handled by the new javaw.exe.
>
>Also if you have a look at the port status via netstat -a -n you can see a
>lot of connector ports in a TIME_WAIT state from memory, so the problem may
>be something to do with networking.
>
>Only when the process is killed does the port status return to normal.
>
>Sometimes this can occur several times in a row and then on say the sixth or
>seventh attempt it will work and no more problems will occur until you next
>change a jsp page and java class together. And even then sometimes those
>changes work.
>
>If anyone can work out what is causing this, we'd be most grateful... or
>even suggest a clean install route that won't cause these problems, such as
>using the default-server and app or something.... Either way this is very
>annoying - conceptually we're impressed with JRun, but if these problems
>continue we will move our dev servers over to apache running tomcat, and
>recommend this platform to clients.
>
>thank you - below is an overview of installs we've tried JRun 3.0 on:
>
>o Win 2000 Advanced Sever
> Clean install, to be a live server, Jrun Connector used, JDK 1.2.2
> **No problems - although no alteration were made to
> the jsps after their initial compilation
>
>
>
>
>o Win NT 4 Server SP6
> Machine used as workstation for 2.5 years without re-install, JDK 1.2.1
> used as dev server, installed alongside Jrun 2.3.3
> JRun Connector Used
> **No problems - pages changed frequently
>
>
>
>o Win NT 4 Server SP6 <-most studied problem machine
> Machine used as workstation for 1 year without re-install, JDK 1.2.2
>then
> JDK 1.2.1 (which helped) used as dev server - Jrun 2.3.3 uninstalled
> JRun Connector Used
> **Problems - pages changed frequently
>
> JRun Connector Not Used
> **Less Problems - pages changed frequently
>
>
>o Win NT 4 Server SP6
> Machine used as server for 3 months without re-install, JDK 1.2.2
> used as dev server
> JRun Connector Used
> **Problems - pages changed frequently
>
>
>
>o Win NT 4 Server SP6
> Machine used as server for >1 year without re-install, JDK 1.2.2
> used as live server, installed alongside Jrun 2.3.3
> JRun Connector Used
> **No Problems - pages infrequently
>
>
>if any more information is required just ask.
>
>thanks,
>
>/c
>
>
>
>/c>Person -e [EMAIL PROTECTED] -t 01932 237686 -m 07970 255651
>/c/..>People -e [EMAIL PROTECTED] -t 01932 237685 -f 08701 266512
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
