Error: Key "LogFile" not found in configuration

[Petr Stehlik]

Hi,

I am trying to deploy a WAR on a fresh Windows installation of TAS 7.2
by visiting http://localhost:8080/manager/ , selecting a file in "War
file to deploy" and clicking on Deploy.

This works on Linux perfectly. However, on Windows I get the following
error in the wrapper.log file:

Error occured in leafKeys() method
Error: Initialization of logger failed
com.lutris.util.ConfigException: Key "LogFile" not found in configuration.

Any idea why it happens and how to fix that, please?

Petr



--
You receive this message as a subscriber of the enhydra@... mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

[Petr Stehlik]

Petr Stehlik wrote:
> This works on Linux perfectly. However, on Windows I get the following
> error in the wrapper.log file:
>
> Error occured in leafKeys() method
> Error: Initialization of logger failed
> com.lutris.util.ConfigException: Key "LogFile" not found in configuration.
>
> Any idea why it happens and how to fix that, please?

Well, after adding "LogFile" and "DefaultUrl" to web.xml it seems to
almost works (throws a different error now).

I am still wondering why on Linux host it deploys correctly (probably
using a different config than web.xml) while on Windows it fails this way.

Petr




--
You receive this message as a subscriber of the enhydra@... mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

[luis.alfonso.canas]

I have the same problem, but I have not been able to solve.

If you could share what I solved the solution

The truth is that all attempts and fails to reach a solution.


Thank you.

Luis Alfonso Cañas

 

2007/11/29, Petr Stehlik <pstehlik@...>:

Petr Stehlik wrote:
> This works on Linux perfectly. However, on Windows I get the following
> error in the wrapper.log file:
>
> Error occured in leafKeys() method
> Error: Initialization of logger failed
> com.lutris.util.ConfigException: Key "LogFile" not found in configuration.
>
> Any idea why it happens and how to fix that, please?

Well, after adding "LogFile" and "DefaultUrl" to web.xml it seems to
almost works (throws a different error now).

I am still wondering why on Linux host it deploys correctly (probably
using a different config than web.xml) while on Windows it fails this way.

Petr




--
You receive this message as a subscriber of the enhydra@... mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@... ?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Cordialmente

Luis Alfonso Cañas T.

--
You receive this message as a subscriber of the enhydra@... mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

[Slobodan Vujasinovic-2]

Some parts of this message have been removed. Learn more about Nabble's security policy.

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

 

From: luis alfonso cañas triana [mailto:luis.alfonso.canas@...]
Sent: Thursday, 29 November, 2007 20:37
To: enhydra@...
Subject: Re: [enhydra] Error: Key "LogFile" not found in configuration

 

I have the same problem, but I have not been able to solve.

If you could share what I solved the solution

The truth is that all attempts and fails to reach a solution.


Thank you.

Luis Alfonso Cañas

 

2007/11/29, Petr Stehlik <pstehlik@...>:

Petr Stehlik wrote:
> This works on Linux perfectly. However, on Windows I get the following
> error in the wrapper.log file:
>
> Error occured in leafKeys() method
> Error: Initialization of logger failed
> com.lutris.util.ConfigException: Key "LogFile" not found in configuration.
>
> Any idea why it happens and how to fix that, please?

Well, after adding "LogFile" and "DefaultUrl" to web.xml it seems to
almost works (throws a different error now).

I am still wondering why on Linux host it deploys correctly (probably
using a different config than web.xml) while on Windows it fails this way.

Petr




--
You receive this message as a subscriber of the enhydra@...mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@... ?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Cordialmente

Luis Alfonso Cañas T.

--
You receive this message as a subscriber of the enhydra@... mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

[Luis Carvalho-2]

Some parts of this message have been removed. Learn more about Nabble's security policy.

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

 

 

From: Slobodan Vujasinovic [mailto:slobodan.vujasinovic@...]
Sent: sexta-feira, 30 de Novembro de 2007 11:06
To: enhydra@...
Subject: RE: [enhydra] Error: Key "LogFile" not found in configuration

 

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

 

From: luis alfonso cañas triana [mailto:luis.alfonso.canas@...]
Sent: Thursday, 29 November, 2007 20:37
To: enhydra@...
Subject: Re: [enhydra] Error: Key "LogFile" not found in configuration

 

I have the same problem, but I have not been able to solve.

If you could share what I solved the solution

The truth is that all attempts and fails to reach a solution.


Thank you.

Luis Alfonso Cañas

 

2007/11/29, Petr Stehlik <pstehlik@...>:

Petr Stehlik wrote:
> This works on Linux perfectly. However, on Windows I get the following
> error in the wrapper.log file:
>
> Error occured in leafKeys() method
> Error: Initialization of logger failed
> com.lutris.util.ConfigException: Key "LogFile" not found in configuration.
>
> Any idea why it happens and how to fix that, please?

Well, after adding "LogFile" and "DefaultUrl" to web.xml it seems to
almost works (throws a different error now).

I am still wondering why on Linux host it deploys correctly (probably
using a different config than web.xml) while on Windows it fails this way.

Petr




--
You receive this message as a subscriber of the enhydra@...mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@... ?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Cordialmente

Luis Alfonso Cañas T.

--
You receive this message as a subscriber of the enhydra@... mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

[Petr Stehlik]

Luis Carvalho wrote:
> I had these problems before, typically when editing configuration files
> in a OS and then deploying in another OS.

we develop on linux and when deploy on linux it works while this error
appeared when we tried to deploy under windows.

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

oh no. It's 2007. Does it still need the Carriage Return typewriter-ish
character? Java shouldn't need that.

> Hope this is useful.

thanks for the hint, we'll give it a try but if it helps then I'll be
really unhappy from the MS-DOS CRLF.

Petr




--
You receive this message as a subscriber of the enhydra@... mailing list.
To unsubscribe: mailto:enhydra-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws