Skip to main content
A
Anonymous
August 17, 2010
Question

Cannot find component.cfc after Solaris upgrade to 9.0.1

  • August 17, 2010
  • 1 reply
  • 665 views

  As subject says.  Path is correct, permissions and file length are the same as a working 9.0.1 install.

  Solaris 10 SPARC 64b

    This topic has been closed for replies.

    1 reply

    A
    Adam Cameron.
    Inspiring
    August 17, 2010

    Is it like a createObject() call or <cfinvoke> or some thing that cannot find it?  Are you using a full-dotted path to it or just "component" (have you really got a CFC called component.cfc?).

    Have you lost some mappings or custom tag paths during the upgrade?

    Can you browse directly to the file?  If so, what dotted path does it suggest it's on?  Is it the same as what you're using?

    Did you clear out any saved classes you might have in your cfclasses dir as part of the upgrade?  It shouldn't matter, but then again...

    --

    Adam

    A
    Anonymous
    August 17, 2010

      I can browse directly to the file.  CFIDE is in a custom location.  The path called in the cfserver log appears to be correct.  I'm just a sysadmin; not a CF developer.  All I did was run the 9.0.1 installer bin file, upgrade the l10 patch files and then start the server.  Did so earlier on another box and had problems.  Let me know what info I should be providing; appreciate the help.

    javax.servlet.ServletException: ROOT CAUSE:

    coldfusion.runtime.CfJspPage$NoSuchTemplateException: Could not find the ColdFusion component or interface /opt/coldfusion9/wwwroot/WEB-INF/cftags/component.cfc.

            at coldfusion.runtime.TemplateClassLoader.newInstance(TemplateClassLoader.java:565)

            at coldfusion.runtime.TemplateClassLoader.newInstance(TemplateClassLoader.java:541)

            at coldfusion.runtime.TemplateProxyFactory.getCFCInstance(TemplateProxyFactory.java:271)

            at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:174)

            at coldfusion.runtime.TemplateProxyFactory.resolveComponentHelper(TemplateProxyFactory.java:405)

            at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:224)

            at coldfusion.runtime.TemplateProxyFactory.resolveComponentHelper(TemplateProxyFactory.java:364)

            at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:224)

            at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:159)

            at coldfusion.runtime.TemplateProxyFactory.resolveName(TemplateProxyFactory.java:149)

            at coldfusion.cfc.ComponentProxyFactory.getProxy(ComponentProxyFactory.java:62)

            at coldfusion.runtime.CFPage.CreateObject(CFPage.java:4827)

            at coldfusion.runtime.CFPage.CreateObject(CFPage.java:4841)

            at cfApplication2ecfm829109979._factor0(E:\cf9_updates_rc\cfusion\wwwroot\CFIDE\administrator\Application.cfm:96)

            at cfApplication2ecfm829109979._factor3(E:\cf9_updates_rc\cfusion\wwwroot\CFIDE\administrator\Application.cfm:76

    -bash-3.00# lt  /opt/coldfusion9/wwwroot/WEB-INF/cftags/component.cfc

    -rwxrwxrwx   1 nobody   root           0 Aug 17 15:32 /opt/coldfusion9/wwwroot/WEB-INF/cftags/component.cfc

    A
    Adam Cameron.
    Inspiring
    August 17, 2010

    Ah.  Yikes.  That's one of CF's own files.

    I'm not great with Solaris installs... haven't touched on for about three years and even then was just a CF dev "helping" the Solaris sysadmin.  Um... if it was on Windows I'd be looking in the jrun-web.xml file to make sure the /WEB-INF mapping was a) there; b) pointing to the correct place.

    Did you back everything up before doing the upgrade?

    --

    Adam

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices