Speech Application Logging Issue after upgrading OD from 8.1 to 8.1.2.1201

[neman]

Hello
We are in the process of migrating from 8.1 to 10.2. Not sure that is good info or not but thought I should mention it.
I have installed OD 8.1.2.1201 locally.
Setup 2 new windows application servers running Apache 9.0.104 and OpenJDK 11 from Temurin to be compatible with 10.2.
I imported all my applications into the new OD 8.1.2.1201, they are all converted with no errors.
I export the speech applications as usual choosing my Platform = Experience Portal, Servlet container = Apache Tomcat 9.x
Under Tracing I DESELECT "Reset tracing in the deployed application to the default (disabled) settings option.
Installed all my speech application war files
Executed the http://localhost:8080/runtimeconfig on both application servers.
Went into Application Configuration
Added all my applications
I normally go into Applicaiton Information and I redirect all apps on all servers to F:\ExtAppLogs\{application_name}
That has been completed.

Call into it the flows and they work great.

Now the issue, under F:\ExtAppLogs\ I see it created the typical folder for the application, however there are zero trace files in there. It is writing the log entries to the tomcat\webapps\{application name} folder as if I didn't run runtimeconfig.

I noticed each application now has a ddlog4j2.xml file which did not exist in 8.1
and they all start with this

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
<Properties>
<Property name="log-path"> ${log4j:configParentLocation}/log</Property>
</Properties>

no clue where configParentLocation is defined but I assume this is the problem.

One more item, I am testing this by calling into an 8.1 EP system and sending the calls to my new application servers, not sure if that makes a difference. The 10.2 EP's are not ready yet.

[wilsonyu]

The ${log4j:configParentLocation}/log directory is the Tomcat_Home/webapps/<app>/data/log.
The trace.log file will reside in this directory as stipulated by the ddlog4j2.xml configuration. The runtimeconfig is no longer relevant in this log4 v2 upgrade.
Also, for logs to be produced, make sure you have the properties in the EPM app configuration set as before.
You certainly change directory path in the ddlog4j2.xml. You can use UNC path ie c:\\xxx\xx as permitted by log4j.

[neman]

Thanks Wilson

ok so there is no longer a GUI like runtimeconfig to set these remote logging directories, you have to manually edit each file before exporting them to the application servers, am I understanding that correctly?

This is what I see now
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
<Properties>
<Property name="log-path"> ${log4j:configParentLocation}/log</Property>
</Properties>

Can you possibly share with me how that entry would look?
I want to log locally to the F:\ExtAppLogs\App1 or F:\ExtAppLogs\App2 or F:\ExtAppLogs\App3, depending on the application that is being used.

[neman]

Update: I tried to change one of my apps called Australia by making the following entry and restarted apache.

<Configuration status="WARN">
<Properties>
<Property name="log-path">F:/ExtAppLogs/Australia/data/log</Property>
</Properties>

I placed a call to the app, went thru it and then checked the server on my F:\ExtAppLogs it did create Australia\data\log but there are no trace.log files.
I always have tracing on the url that runs the speech app in EP, this is the new 8.1.2.2 by the way.
http://my1ava1sql01:8080/Australia/Start?ddtrace=true

[wilsonyu]

The path seems to be fine. The fact that there is no file (even an empty) is no good.
If you dig into the app's WEB-INF/lib directory, do you see a library file named "log4j-web-2.17.1.jar"?
Another thing is I am not sure if the parameter "ddtrace" still works. It has never been the official way to enable logs for apps running on EP
The official way is setting the parameters in the Application Configuration screen in EPM as shown in the attached graphic

[neman]

That's good to know I've literally never used that screen. All of mine are set to No in my 8.1 world and all of them do proper tracing.
I figured out the format that works. It was also failing because that bug you and I worked in the other thread about the <!--<!---<appender-ref ref="console-log"/> -->--> that keep stacking up . I had to remove those again and make the "" backslashes, "/" forward slashes and now it is logging.

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
<Properties>
<Property name="log-path">F:/ExtAppLogs/Australia/data/log</Property>
</Properties>
<Appenders>

<!-- console appender -->
<Console name="console-log" target="SYSTEM_OUT">
<PatternLayout pattern="%d{dd/MM/yyyy HH:mm:ss:SSS} %5p - %m%n"/>
</Console>

<!-- file appender -->
<RollingFile name="trace" fileName="${log-path}/trace.log"
filePattern="${log-path}/trace-%d{yyyy-MM-dd}.log">
<!-- log pattern -->
<PatternLayout>
<pattern>%d{dd/MM/yyyy HH:mm:ss:SSS} %5p - %m%n</pattern>
</PatternLayout>

<!-- set file size policy -->
<Policies>
<!--TimeBasedTriggeringPolicy interval="1" modulate="true"/-->
<SizeBasedTriggeringPolicy size="10 MB" />
</Policies>
<DefaultRolloverStrategy max="20"/>
</RollingFile>
<RollingFile name="report" fileName="${log-path}/report.log"
filePattern="${log-path}/report-%d{yyyy-MM-dd}.log">
<PatternLayout>
<pattern>%d{dd/MM/yyyy HH:mm:ss:SSS} %5p - %m%n</pattern>
</PatternLayout>
<Policies>
<TimeBasedTriggeringPolicy interval="1" modulate="true"/>
</Policies>
</RollingFile>
</Appenders>

<Loggers>
<Logger name="Dialog.Designer.TraceWriter" level="debug" additivity="false">
<appender-ref ref="trace"/>
<appender-ref ref="console-log"/>
</Logger>
<Logger name="Dialog.Designer.ReportWriter" level="debug" additivity="false">
<appender-ref ref="report"/>
<appender-ref ref="console-log"/>
</Logger>
<Root level="debug" additivity="false">
<AppenderRef ref="console-log"/>
</Root>
</Loggers>
</Configuration>

thanks for working with me on these last 3 issues, go live is next Wednesday so this really helped move testing along.