Error in Tomcat

Hi,

When we started Tomcat and then using IE when we try to access the default login page, we get the below error in Tomcat console:

INFO: Jk running ID=0 time=15/531 config=C:\worksitemp4\mpwebcomponents\tomcat4.1.30\bin\..\conf\jk2.properties
log4j:WARN No appenders could be found for logger (com.imanage.workteam.viewSets.ConnectorSet).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN No appenders could be found for logger (com.imanage.cms.fc.sysproperties.SystemProperty).
log4j:WARN Please initialize the log4j system properly.

Anybody could throw some light as to what it is...

Thanks and Regards
Selva.

Find more posts tagged with

Comments

Nicholas

Don't worry, this will not affect anything. It's a warning not error Well its not finding log4j.properties at correct place.

Thanks Nicholas

tup_selva

Thanks Nicolas for the information.

Could you pls. let me know what should be done to avoid such warning.

Thanks
Selva.

JTNeville

Configure your log4j.

Start here:

http://logging.apache.org/log4j/docs/manual.html

Aryan

But in spite of this error I see that the logs get created properly. Just check the Log Viewer and you would be able to see all the logs.

Aryan

In you still have doubts check the log4j.properties file in the following path, if you have chosen "WebComponents with Tomcat" option while installation:

<Worksite install dir>\mpwebcomponents\tomcat4.1.30\webapps\workroute\WEB-INF\config

Migrateduser

From the developer (you cannot get a more honest answer):

It is the result of the classic chicken&egg issue, during initializaiton of the log4j subsystem. MP Webapp uses a somewhat dynamic log4j configuration mechanism. It updates the default log4j config template (WEB-INF/config/logger.xml) with some parameters taken from the main web app config file (parameters like log file location, logging level etc) and then starts the log4j with a new runtime config file (logger-runtime.xml).
For this extra processing to be fault tolerant we have to start a few other subsystems (like Config subsystem and FaultManager Subsystem) beforehand. These subssystems produce some log entries which in turn cause those WARN messages (remember log4j is not initlialized yet). We could not completely hide these logs because Config and FaultManager subsystems are re-entry enabled and they are used during the normal running of the webapp after the log4j init.

With that much said, the init code can be a bit more intelligent and dynamically detect the log4j state before issuing the log messages. We did not take this path as this might introduce some minor unnecessary overhead after the init stage.

There is nothing a customer/partner can do here to hide those messages. We will try to see if this can be fixed in the next major release.

-bijoy