RE: Error: Key "LogFile" not found in configuration

Hi,

I had these problems before, typically when editing configuration files in a OS and then deploying in another OS.

The way I solved was to change the line end characters in the destiny OS.

In linux open configuration files with ‘vi’ and execute the command ‘:set ff=unix’.

In windows open in editor like Scite and change the line end characters.

Hope this is useful.

Regards,

Luis Carvalho

Hi,

There is some JNDI reference problem during leafKeys() method execution!

Newer EAF releases are reading application parameters and resources from JNDI context.

The goal was unified way of reading conf/xml defined properties and resources initialized by the servlet container.  So, now you have property reader (configurable ConfigFileReader – conf/xml) that loads properties from configuration file into application JNDI context at application startup and JNDI adaptor that loads (during leafKeys() method) properties (from JNDI  context) into application “Config” object.

Logger initialization is coming first and if EAF is not able to find “LogClassName” property (as a result of empty Config object) it is assuming   that you are using standard logger implementation (default property value) which requires  “LogFile” property to be defined (explanation of the log message you’re getting).

So, this is only manifestation of different problem - configuration corruption which results with incomplete application “Config”!

Usually, this is result of some “null” resource references in you configuration (e.g. not properly configured Data Source and/or Transaction Manager JNDI reference).

The strange behavior is that you have functional configuration on Linux and problems on Windows!

Please, check configuration of the environment resources (definition and reference configuration) one more time (drivers, url’s …)!

If the problem persists, you can send me you configuration file(s) and I can take another look.

Regards,

    Slobodan

--
Cordialmente

Luis Alfonso Cañas T.