Skip to main content
T
tribule
Legend
August 31, 2013
Question

Configuring logging in ColdFusion 10

  • August 31, 2013
  • 1 reply
  • 4415 views

Hi,

Can someone please tell me how to configure the logging options in ColdFusion 10? In particular, we have a lot of WARN and INFO errors in our coldfusion-error.log and coldfusion-out.log files. These errors are not fixable, and we would rather not log them as they are not critical. The issue is that the logs grow massively and are not wanted.

How can we control the level of logging in ColdFusion 10? There is no information anywhere on this subject, either on the web generally or on Adobe's own website.

Advice appreciated.

Thanks,

Mark

    This topic has been closed for replies.

    1 reply

    A
    Adam Cameron.
    Inspiring
    August 31, 2013

    As far as I know you can't. IMO CF's logging is not very well thought out or implemented.


    That said what is causing these INFO and WARNING entries to be logged in the first place?

    --

    Adam

    T
    tribuleAuthor
    Legend
    August 31, 2013

    Hi Adam,

    Thanks for the reply. That is surprising, since one would think this is a basic requirement.

    The errors are vague. We use a third-party ecommerce system (legacy) and we see:

    [Fatal Error] :-1:-1: Premature end of file.

    and:

    WARN  org.xml.sax.SAXParseException; Premature end of file.

    org.xml.sax.SAXParseException; Premature end of file.

    errors in our logs. It does not affect our website, but the logs are enormous.

    There is some mention of the subject of the SAX errors on the net, but not in context to our system.

    Does anyone know how to stop these SAX errors? We have a saxpath.jar in use (dates from 2007).

    Regards,

    Mark

    A
    Adam Cameron.
    Inspiring
    August 31, 2013

    I had a shufti around, and I found this config file: [instance]/lib/neo-logging.xml, and within that there is a setting value: <var name='priority'><string>information</string></var>. This does not have any equiv on the log-management UI in CFAdmin.  Maybe mess around with that and see if it helps... it might be a minimum log level to log? That's a guess.

    --

    Adam

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