Skip to main content
B
bmelendy
Known Participant
January 21, 2011
Question

ColdFusion 9 CFSTAT Won't Stay Checked??

  • January 21, 2011
  • 3 replies
  • 1891 views

Hi Folks, trying to enable CFStat.  I can't get the CFSTAT or Enable Performance Monitoring check boxes to keep their settings?  I check them, restart ColdFusion and when I log back into the CF Administrator, they are not checked?!  I've read a lot of posts on this problem and tried multiple things (like manually editing the neo-metric.xml file) but nothing works.  I've got multiple 9.01 Enterprise servers and it is the same on all of them.

Is there any fix for this?  It works great on my CF 8 Enterprise servers, just CF 9 fails??   Thanks in advance.

...Brad

    This topic has been closed for replies.

    3 replies

    C
    carl type3
    Legend
    January 23, 2011

    hi Brad,

    Just bit of a sanity check - CF9.0.1 with CFSTAT OK:

    Not sure what to suggest. Was  the CF9 install fresh or upgrade of existing CF8?

    Keep your chin up, Carl.

    B
    bmelendyAuthor
    Known Participant
    January 26, 2011

    Thanks for everyone's comments.  I never got anything to work, however, I uninstalled CF and reinstalled, in so doing, I moved up to the 64bit version of CF rather than the 32bit version (which I had been using) and CFStat now works!  I'll never be able to prove what was wrong before but at this point and with all the time I've spend trouble shooting, I don't care anymore.  Thanks again for everyone's help!

    ...Brad

    C
    carl type3
    Legend
    January 28, 2011

    I wondered about cfstat being checked by default and wondered if maybe that had been stored in the registry someplace?  It couldn't have been from the previously installed directory because I had renamed it prior to installing the 64bit version. 

    The cfstat counts look fine so it all appears to be working now.  Thanks again.


    CFSTAT check box; I went back and “visited” some of the Win 64bit CF9 64bit installs I did recently and notice CFSTAT box is ticked.

    C
    carl type3
    Legend
    January 21, 2011

    Hi Brad,

    check neo-metric.xml file:

    Does it say:
    <var name='cfstat'><number>1.0</number></var>

    Then change it to:
    <var name='cfstat'><string>true</string></var>


    And or this:

    <var name='cfstatport'><number>1.0</number></var> to

    <var name='cfstatport'><string>7999</string></var>

    After XML file change restart CF and try enable CFSTAT.

    HTH, Carl.

    B
    bmelendyAuthor
    Known Participant
    January 21, 2011

    Thanks Carl, I've got the following values:

    <var name='cfstat'>

    <string>true</string>

    </var>

    <var name='cfstatport'>

    <string>7997</string>

    </var>

    I've tried running cfstat with the -port option and passing it a value of 7997 but that never does anything except generate the same error that tells me it can't connect.  Thanks again.

    ...Brad

    D
    Community Expert
    Dave WattsCommunity Expert
    Community Expert
    January 21, 2011

    Can you try running CF as an application, to see (a) whether you still have the same problem, and (b) if so, what gets dumped to STDOUT?

    Can you see if the neo-*.xml files are locked using a Windows tool like Process Explorer?

    Dave Watts, CTO, Fig Leaf Software

    http://www.figleaf.com/

    http://training.figleaf.com/

    Dave Watts, Eidolon LLC
    B
    bmelendyAuthor
    Known Participant
    January 21, 2011

    Thanks Dave, I'm not sure what you mean by running CF as an application.  I have standalone installations running under both Windows and Linux (no J2EE or Clustering or anything fancy like that).  I don't have process explorer handy but I can inspect the file permissions on neo.xml files and the system account has full control of them. 

    D
    Community Expert
    Dave WattsCommunity Expert
    Community Expert
    January 22, 2011

    I mean, starting CF from a command prompt rather than running it as a service, using cfstart.bat for a standalone install I think.

    As for the Process Explorer bit, I was more interested in whether the files were locked than who owned them. But I think the correct Sysinternals tool is File Monitor actually, not Process Explorer.

    Dave Watts, CTO, Fig Leaf Software

    http://www.figleaf.com/

    http://training.figleaf.com/

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