I too, am impressed very favorably with not only the follow-up, but the reassurance that those of us that were experiencing problems and took quite a bit of flack from other users of this list for complaining about it, were not imagining the problems.
It is also very re-assuring that the identification and resolution has become a priority of MM, and I am really going to enjoy becoming a member of the happy campers again. I now have a slick and solid running Win2003/CFMX server running and am in the process of adding the free hosting of another user group, the first of which are very interested in a CFMX web site. I think it will be a showpiece when uploaded and goes live within the next few days. ====================================== Stop spam on your domain, use our gateway! For hosting solutions http://www.clickdoug.com ISP rated: http://www.forta.com/cf/isp/isp.cfm?isp_id=772 ====================================== If you are not satisfied with my service, my job isn't done! ----- Original Message ----- From: "Mike Kear" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Wednesday, June 11, 2003 9:54 PM Subject: RE: Update on the Installer "Freeze" & Failure to Auto-Start on W indows Issues... | This is excellent follow-up. I'm pleased they're working on it like | terriers and aren't going to let it go till it's resolved. | | What Damon says would explain how come some people experience the problem | and others don't, and also how come the problem went away when some people | forced CFMX to load earlier in the boot-up cycle. | | | Cheers, | Michael Kear | Windsor, NSW, Australia | AFP Webworks. | | | | | -----Original Message----- | From: Damon Cooper [mailto:[EMAIL PROTECTED] | Sent: Thursday, 12 June 2003 11:42 AM | To: CF-Talk | Subject: RE: Update on the Installer "Freeze" & Failure to Auto-Start on W | indows Issues... | | One more update: | | We believe we at least somewhat understand the "CFMX doesn't startup on | reboot" issue as recreated on the machines in house here. | | To summarize (and I'm sure I'm whitewashing some of this): | | 1) The CFMX App Server is an native Windows executable wrapper that is the | main "ColdFusion MX Application Server" service. | 2) It controls, starts, stops, and monitors the main "jrun.exe" executable | that CFMX is runs on. | 3) The wrapper executable has separate timeout values for both starting and | stopping the main "jrun.exe" executable. Both timeout values are currently | hardwired to 20 seconds. | 4) On machines with a lot going on during startup, or complex services | dependencies, or slow machines, the "jrun.exe" executable can exceed the 20 | second timeout in successfully starting. When this timeout is exceeded, the | Service wrapper executable "gives up", returns a failure code and CFMX is | not started. | 5) If, when CFMX is told to shutdown (via the Services Control Panel, or via | command, or when an Updater installer tells it to shutdown), the "jrun.exe" | exceeds the Service wrapper's shutdown timeout (20 sec), the wrapper returns | a failure code and gives up. | | When we extend the startup timeout of the Service wrapper executable (we | give it some patience), "jrun.exe" and CFMX eventually startup fine, but it | may take some extra time. Same for shutdown in most cases. | | So............... | | We're testing a fix to the wrapper that a) raises the default timeout for | both operations, and making these values configurable via a setting | (registry, XML file, whatever). It seems to work in all cases so far, and we | hope to get it to Mike's hoster guy to try shortly (he may already have it | now). | | Finally, as extra shutdown insurance, we may optionally allow the shutdown | code of the Service wrapper to do a forced shutdown of the "jrun.exe" if the | (now extended, configurable) timeout expires. As soon as we have a good | hotfix, we'll try to make it generally available ASAP. | | | | Sorry about all this, and thanks for hanging with us... | | Damon | | | | | -----Original Message----- | From: Damon Cooper | Sent: Tuesday, June 10, 2003 7:16 AM | To: 'CF-Talk '; '[EMAIL PROTECTED]' | Subject: RE: Update on the Installer "Freeze" & Failure to Auto-Start on | Windows Issues... | | | Quick update: | | Switching JVM's didn't have any affect on our test machine exhibiting the | problem. We do get "Error Number 2" errors in the System Event Log, however, | which indicate "The system cannot find the file specified." This could be | due to the fact that a socket open failed (TCP sockets are OS "files") due | to the OS network layer not being ready for us, or we were impatient with a | short timeout, and may need to sleep & retry the open and/or use a longer | timeout. | | We continue to actively work this today. More to come... | | | | | -----Original Message----- | From: Damon Cooper | Sent: Sunday, June 08, 2003 10:42 AM | To: 'CF-Talk ' | Subject: Update on the Installer "Freeze" & Failure to Auto-Start on Windows | Issues... | | | I've not had the cycles to keep up with the feeding frenzy this has turned | into, but I thought I'd update everyone on where we are regarding the 2 | issues reported and discussed here at the one machine at Mike's hosting | site: | | 1) ZeroG Java-based Updater installer hang. | | It took us a little while to track this down (we had to find a machine with | less-than 8-bit color display capability...harder than you'd think these | days). | | Here's the scoop: | | a) For the GUI-based installer, a minimum of 8-bit color depth (256 colors) | is required to run InstallAnywhere-based installers. Additionally, | installers require a minimum 640 X 480 screen resolution. | | b) The Updater installer can be invoked in "silent" mode on Windows, if you | have a machine that doesn't meet (a) above for the GUI install, or (b) you | have a need to apply the Updater to many machines via batch scripts, etc, | etc. Follow the instructions here for a "silent" install: | | http://www.macromedia.com/support/coldfusion/releasenotes/mx/releasenotes_mx | _updater03.html#silentinstall | | | 2) CF not automatically starting reliably on Windows after system reboot: | | We had 3 engineers working this all day Friday, and we believe we have a | reproducible case, and have started debugging the process to see what's | happening. | | One of the things we're about to try is to simply switch Java VM's to see if | this is the result of a Java VM bug (we've had several in the | interacting-with-Windows-as-a-Service area before, so we're not ruling that | out, and it's a quick thing to try. Recall that the CFMX Gold bits shipped | out of the box with the Sun 1.3.1_03 VM. Trying the 1.3.1_08 VM, the | 1.4.1_03 VM and the 1.4.2 Beta VM will determine whether it's something | that's fixed in the VM. If anyone on this list is experiencing the issue, | and wants to try these VM's and report back, that would be a big help, and | you can participate in helping to move this issue forward. | | More to come, when we know more (likely Monday EOD sometime)... | | Thanks for your patience. | | Damon | | | | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
