(TechNote) After your external web server has been configured, the JRun connector will establish a connection with the specified JRun server every time the web server is started. This TechNote describes what happens when the web server starts up and some changes that occurred after JRun 4 Updater 2.
(TechNote) ColdFusion MX and JRun are Java applications that depend on the Sun Java Virtual Machine (JVM) for their time information. The new US Daylight Savings Time changes for 2007 will affect ColdFusion MX and JRun because of this.
(Hot fix) JRun generates Java stderr and stdout logs as [server name]-err and [server name]-out when running as a Windows service, however, the files do not rotate. A hot fix has been created to solve this issue.
(Hot fix) JRun Remote transactions did not function properly with remote client.
(Hot fix) When browsing a cluster while an instance is starting, the server throws a “500 Server error Service Temporarily Unavailable” message in the browser window until the instance has fully started.
(Hot fix) JRun may lose query string parameters from the same URL under heavy load if request.setCharacterEncoding() is called before getting the parameters.
(Hot fix) JRun connector returns a blank page for a JSP request when the JRun server is stopped.
(TechNote) The JRun 4.5 beta program has officially ended. Adobe would like to express our gratitude for all customer participation and feedback during this cycle.
(TechNote) It is good practice to always code a return after a sendRedirect statement in any Servlet. It has been found that, without a return statement immediately following the sendRedirect, a request may fail due to the timing of how JRun manages its socket communication.
(Hot fix) JRun causes a memory leak when a client calls an EJB via the JMX service using a new thread.
