TDI 6.1.1 logging issue

[udayab...@gmail.com]

Hi,

I have an issue with TDI 6.1.1 logs. I have two TDI configs. One
runs always and other runs for a period of time. And both are using
same Solution properties. I dont see any logging activities for the
second config (which runs periodically) and sometimes whenever it
logs, other config (which runs always) hangs. But there are no errors
or exceptions thrown in logs.

Did anyone faced this issue? And also can someone please advise
about using SAME Solution properties for different config.

Thanks in Advance.

[Eddie Hartman]

How have you configured logging for your ALs? Or have
you set Config-wide Log Appenders?

-Eddie

[udayab...@gmail.com]

> > Thanks in Advance.- Hide quoted text -
>
> - Show quoted text -

Hi Eddie,

Thanks for your quick reply. I am logging using DailyRolling File
appenders for ALs. And at the rootCategory I am using the default
DailyRollingFile Appender.

log4j.rootCategory=INFO, Default
log4j.appender.Default=org.apache.log4j.DailyRollingFileAppender

log4j.appender.EmailLog=org.apache.log4j.DailyRollingFileAppender
log4j.appender.EmailLog.file=/var/log/idi/Email.log
log4j.appender.EmailLog.layout=org.apache.log4j.PatternLayout
log4j.appender.EmailLog.layout.ConversionPattern=%d{ISO8601} [%c] - %m
%n
log4j.appender.EmailLog.append=true

Please let me know if my logging strategy is OK or need to be changed.

Thanks

[kolev.kg]

Hi,

Do you face this issue when you do not use any of the log appenders at
all?

To verify this you could add a single ScriptComponent for each of the
ALs with the following content:
Packages.java.lang.System.err.println("AL1: " + new
Packages.java.util.Date());

This will get written to the TDI Server's console so you know when any
of the ALs stop.

If the issue is still present then the problem is deeper than we
think.

Best Regards,
Kaloyan Kolev.