nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding custom log configuration to customer tk

Bill Klish

TeamSite 6.5 SP1
Windows 2003

I have added my own log4j log configuration file for some Java code I have added to the customer toolkit. The log4j configuration file contains:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"
debug="false">


<appender name="CUSTOMER_DEBUG" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="${log100.iwlogs}/iwui/customer_debug.log"/>
<param name="MaxFileSize" value="1MB"/>
<param name="MaxBackupIndex" value="2"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c (%x) - %m%n"/>
</layout>
</appender>
<appender name="CUSTOMER_DEFAULT" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="${log100.iwlogs}/iwui/customer.log"/>
<param name="MaxFileSize" value="1MB"/>
<param name="MaxBackupIndex" value="2"/>
<param name="Threshold" value="WARN"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c (%x) - %m%n"/>
</layout>
</appender>



<root>
<level value="debug"/>
<appender-ref ref="CUSTOMER_DEFAULT"/>
</root>
</log4j:configuration>

When I issue make_toolkit after adding this file to customer_src/etc/conf, the following messages appear multiple times in the servletd_out.log file:

log4j:ERROR Parsing error on line 5 and column 36
log4j:ERROR Document root element "log4j:configuration", must match DOCTYPE root "null".

I have checked and this file gets properly copied into the same location within the httpd/webapps/content_center/WEB-INF/conf/customer directory that it does for other sections, i.e. ccpro, etc.

What appears to be happening is that the DTD is not being located properly. We have had a support case open for 3 months now to solve this issue without much progress or success. This behavior has been duplicated on 6.1, Solaris and Linux.

Anyone have any ideas on what to try?

Find more posts tagged with

Comments

Migrateduser

Hi,

Try the log4j.xml without the root element. It doesn't validate during make_toolkits.ipl.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"
debug="false">


<appender name="CUSTOMER_DEBUG" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="${log100.iwlogs}/iwui/customer_debug.log"/>
<param name="MaxFileSize" value="1MB"/>
<param name="MaxBackupIndex" value="2"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c (%x) - %m%n"/>
</layout>
</appender>
<appender name="CUSTOMER_DEFAULT" class="org.apache.log4j.RollingFileAppender">
<param name="File" value="${log100.iwlogs}/iwui/customer.log"/>
<param name="MaxFileSize" value="1MB"/>
<param name="MaxBackupIndex" value="2"/>
<param name="Threshold" value="WARN"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d %-5p %c (%x) - %m%n"/>
</layout>
</appender>



</log4j:configuration>

Drop the log4j.dtd into the local\config\lib\content_center\customer_src\etc\conf\customer directory. That enables the toolkit to be built. During execution of make_toolkit.ipl, the log4j.xml is placed in the httpd\webapps\content_center\WEB-INF\conf\customer. Before restarting iwservletd, copy the log4j.dtd into the same directory from the httpd\webapps\content_center\WEB-INF\conf directory.

That should work!

Bill Klish

Sorry it took so long to actually try this out.

Your suggestion didn't work.

I am still getting this:

log4j:ERROR Parsing error on line 5 and column 35
log4j:ERROR Document root element "log4j:configuration", must match DOCTYPE root "null".
log4j:ERROR Parsing error on line 5 and column 35
log4j:ERROR Document is invalid: no grammar found.

This time I tried this on a TeamSite 6.1 SP2, Windows 2003 EE server.

I copied the log4j.dtd into the proper location underneath httpd\webapps.....

Does this work for you?

Migrateduser

I am running with Teamsite 6.5. This works for me.

Couple of questions:

Did you remove the root element from the xml? Also, do you get the error in the servletd log when the make_toolkits.ipl is executed or during servletd startup?

Amish

Bill Klish

Just to be clear, by root element you mean: <?xml version="1.0" encoding="UTF-8"?> ?

I tried that, tried removing the log4j:configuation element, but got a SAX parse exception (which makes sense).

This is showing up in servletd_out.log after executing make_toolkit.ipl

Migrateduser

No, remove or comment this portion from the log4j.xml

<root>
<level value="debug"/>
<appender-ref ref="CUSTOMER_DEFAULT"/>
</root>

After executing make_toolkit.ipl, did you restart the servlerd service?

thanks
Amish

Bill Klish

Yes, I took that section out as well.

I did an iwreset -a after running make_toolkit but those error lines still show up. Do I need to restart the service individually? Will I need to repeat this every time we make a change to the customer toolkit?

The weird thing is, despite those errors appearing in servletd_out.log, the logging works correctly (and always has). This is more of an annoyance then anything.

As mentioned in my first post, Interwoven Support has been working on this for months and we have gotten absolutely nowhere.

soka

Hi,

did you managed to solve this issue?

Regards
Akos

Bill Klish

Nope. We opened a support case and that hasn't gone anywhere either. Not sure what is not being setup correctly, but it is sure annoying. It has fallen to the back burner but I will see if the support case was ever solved and post back.

Bill Klish

This is what I found out from my colleague who worked with support on this issue. We were told that they couldn't reproduce the issue in house. I have seen the issue with 6.1 SP1, 6.5 SP1 and 6.5 SP2 on both windows and solaris.

The solution we were given was to manually copy the log4j.xml file into the target directory underneath iw-home/httpd/webapps/content_center

There has to be a better way....