Skip to main content
A
Anonymous
March 18, 2009
Question

Upgrading Multiple Instances of CF8 to CF8.01

  • March 18, 2009
  • 2 replies
  • 2173 views
I am running CF8 on a Windows 2003 server. I have 13 instances on this server. I need to get all of them to CF8.01 but I don't know how. I ran the coldfusion8-win-updater and selected Mulit-server configuration. When I look at the instance where the install was pointed for CFIDE, that instance is at 8.01. The others are still at 8.0. I then stopped everything again and ran the install and selected Multi-server configuration again. I then pointed the installation to another one of my instances CFIDE . When I try to open that instance I get an error message. That is included at the end of this post. Can SOMEONE tell me how to upgrade all of these instances to 8.01? And, can someone tell me what the fix is for my error?

ROOT CAUSE:
java.lang.NoSuchMethodError: coldfusion.tagext.GenericTag.doFinally()V
at cfApplication2ecfm1253482620._factor7(E:\cf8_updates\cfusion\wwwroot\CFIDE\administrator\Application.cfm:4)
at cfApplication2ecfm1253482620.runPage(E:\cf8_updates\cfusion\wwwroot\CFIDE\administrator\Application.cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
at coldfusion.filter.CfincludeFilter.include(CfincludeFilter.java:33)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:214)
at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)
at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)
at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:74)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.CfmServlet.service(CfmServlet.java:175)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)



javax.servlet.ServletException: ROOT CAUSE:
java.lang.NoSuchMethodError: coldfusion.tagext.GenericTag.doFinally()V
at cfApplication2ecfm1253482620._factor7(E:\cf8_updates\cfusion\wwwroot\CFIDE\administrator\Application.cfm:4)
at cfApplication2ecfm1253482620.runPage(E:\cf8_updates\cfusion\wwwroot\CFIDE\administrator\Application.cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:192)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:366)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
at coldfusion.filter.CfincludeFilter.include(CfincludeFilter.java:33)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:214)
at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)
at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)
at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:74)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.CfmServlet.service(CfmServlet.java:175)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:70)
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

    This topic has been closed for replies.

    2 replies

    K
    kensdw
    Inspiring
    May 12, 2009

    Sorry to hear you went through hoops with the updater. I can sympathize with your frustrations, we have had many or out own with all sorts of issues administratively as well as in development.

    I think I found the cause of the problem you reported. I just applied the 8.0 to 8.0.1 UPDATER to a MULTI-INSTANCE server with 7 INSTANCES without incident. The update took all of approximately 10 minutes.

    I couldn't agree with you more; you are so correct that ADOBE provides very little in the way of clearly defined instructions for the updater (and for that matter not very much on most other CF related topics). We found that there is nothing posted in the form or a step-by-step instruction as it regards instructions and in particular be careful as it regards the PATHS of a multiserver installation as it regards doing an upgrade.

    To keep it as short as possible, there are several prompts that come up during the UPDATER, two of which fill in with a PATH during the update:

    • The first is the PATH to the folder containing all the instances - in my case this was filled in with the MULTI-INSTANCE INSTALL location I selected on an early screen of the updater where I pointed it to "DRIVE LETTER:/JRUN4".
    • The second PATH is where the CORE Cold Fusion CFIDE  location is. HERE IS THE PROBLEM - when UPDATER is run, it fills in a PATH by DEFAULT  (I say DEFAULT CAUTIOUSLY because this is MAY NOT be where you want to target the update). In my case UPDATER filled in the PATH of the FIRST configured INSTANCE in the JRUN4\SERVERS folder - THAT'S BAD, this IS NOT were the CORE CFIDE LIVES.....  It is important to understand the UPDATER PROMPT text instruction box that does appear when filling in this CFIDE location. THAT IS, it does advise that this CFIDE PATH is typically the CF ROOT - "CFIDE" location. You need to be sure to point to that root folder or the rest of the updater will continue on and seem perfectly normal except...  the end result will not be what you expect.

    HERE'S WHY - Typically when CF 8 was installed on a server most users will take the defaults for the install and in doing so, the PATH is  C:\Inetpub\wwwroot\CFIDE unless it was overidden to some other drive location. This is where the gotcha is during the updater process. If you don't change this path to the location of the CF ROOT CFIDE the only INSTANCE that will get updated to 8.0.1 will be the first INSTANCE that is in "Drive Letter\JRUN4\SERVERS\xxxxxxx". I believe this may explain why only the instance you targeted was updated and when you ran it again and picked another instance the next one updated, etc. After that, attempts to copy other CFIDE around to try to force it to work got it further twisted up until you resorted to the fix method you tried.

    HERE'S MY GUESS ON WHY or HOW UPDATER BLOWS THE CONFIGS OUT OF THE WATER - I don't know the TECHNICAL specifics that the Adobe Wizards came up for the UPDATER behind the covers but it seems to me that the UPDATER needs to FIRST UPDATE the CF ROOT "CORE CFIDE" and as the process continues to run it then COPIES the UPDATED CORE CF ROOT CFIDE into each INSTANCE.

    Hopefully my posting will help some poor unsuspecting CF ADMIN to an easy 8.0 - 8.0.1 UPDATE.

    Good Luck

    ilssac
    ilssac
    Inspiring
    May 12, 2009

    kensdw wrote:

    HERE'S MY GUESS ON WHY or HOW UPDATER BLOWS THE CONFIGS OUT OF THE WATER -I don't know the TECHNICAL specifics that the Adobe Wizards came up for the UPDATER behind the covers but it seems to me that the UPDATER needs to FIRST UPDATE the CF ROOT "CORE CFIDE" and as the process continues to run it then COPIES the UPDATED CORE CF ROOT CFIDE into each INSTANCE.

    Sounds like somebody had a very unpleasnt upgrade process.  I just wanted to say that is is a very plosible theory.  I do know that when one creates a new instance that the CFIDE of the new instance is a copy of the base instances CFIDE folder thus inheriting any configureations of the base instance at that time.

    S
    Sebastian83
    Participant
    March 20, 2009
    Hi jalehman,

    I had this problem, too. A simple restart of the ColdFusion service should solve that problem.

    Greetings

    Sebastian
    A
    Anonymous
    March 20, 2009
    I wish that was all it took. Heaven knows I have restarted the ColdFusion service numerous times.

    The upgrade to the multiserver configuration SHOULD upgrade all of the instances. I can see where some files in each instance were changed but when I open the CF Admin for one of those instances they are still showing me CF8.0. Figleaf told me that all I had to do was copy over the CFIDE from an upgraded instance to an instance that wasn't upgraded and it should work. It doesn't. I get the same error message that I get when I run the install and point it to a different instance.

    I did find if I copied over the CFIDE and the WEB-INF then the instance showed the upgrade. That may be my only way to get them work. Since all of my instances are almost identical it shouldn't be much work. The only thing I will have to go back and fix is their line debugging port, which I have documented.

    I do wish Adobe had a little more information about upgrading multiple instance when the install of a multiserver configuration doesn't work. I would even take a little more documentation on multiple instances period!
    A
    Anonymous
    March 21, 2009
    OK, I have all of my instances upgraded. First let me give you a little history. When I created my first instances I based them off of J2EE archives. I named those archives to differeniate between archives. When the instances were created they named the .ear and .war of that instance the same name as the archive. I didn't think it made any difference. The latter instances were just setup based on the very first install, hence those .ear and .war folders were named cfusion.

    I found that those instances did upgrade which concluded, in my mind, that the upgrade will only upgrade cfusion-ear and cfusion-war.

    Now what I did for my other 11 instances was this: 1) made a CAR archive of each of those instances, 2) discovered all of the files that changed in the upgrade, 3) copied those files from an upgraded instance to another folder, 4) copied those files from that folder to each of the instances that did not upgrade, 5) restored the CAR archive to each instance.

    This took quite a while to do but it is done.

    Since the CFIDE folder was copied in total, I found that the Enterprise Manager was now showing up on all instances but was erroring out. I went into all, but 1, instances and deleted the cfide\administrator\entman folder. That fixed it.

    I also updated each instance with HotFix 2.

    I must say, I am hoping before there is another upgrade that we move to new servers and set up these instances again. I don't want to have to do this in the future.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices