Interrupted logger writing Issue - Websphere

This is a discussion on Interrupted logger writing Issue - Websphere ; Hi I am facing a problem some time, logging stopped and again started at some point again.. Here is the Log4j.properties file content log4j.rootCategory=DEBUG, OrderLog log4j.appender.OrderLog=org.apache.log4j.RollingFi leAppender log4j.appender.OrderLog.File=C:/logs/OrderLog.txt log4j.appender.OrderLog.Append=true log4j.appender.OrderLog.MaxFileSize=100KB log4j.appender.OrderLog.MaxBackupIndex=5 log4j.appender.OrderLog.layout=org.apache.log4j.Pa tternLayout log4j.appender.OrderLog.layout.ConversionPattern= %d : %-5p %F : %L ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: Interrupted logger writing Issue

  1. Interrupted logger writing Issue

    Hi

    I am facing a problem some time, logging stopped and again started at some point again..



    Here is the Log4j.properties file content



    log4j.rootCategory=DEBUG, OrderLog

    log4j.appender.OrderLog=org.apache.log4j.RollingFi leAppender

    log4j.appender.OrderLog.File=C:/logs/OrderLog.txt

    log4j.appender.OrderLog.Append=true

    log4j.appender.OrderLog.MaxFileSize=100KB

    log4j.appender.OrderLog.MaxBackupIndex=5

    log4j.appender.OrderLog.layout=org.apache.log4j.Pa tternLayout

    log4j.appender.OrderLog.layout.ConversionPattern= %d : %-5p %F : %L: - %m%n

    log4j.logger.com.bowstreet.solutions.OrderLog=DEBU G, OrderLog



    I guess after maxbackupindex reached, it might have giving problem..

    How to resolve this.. any idea..

    It is working fine in Windows os.. It is giving problem in AIX box. env..

  2. Re: Interrupted logger writing Issue

    rameshmessages@gmail.com wrote:
    > Hi

    > I am facing a problem some time, logging stopped and again started at some point again..

    >

    > Here is the Log4j.properties file content

    >

    > log4j.rootCategory=DEBUG, OrderLog

    > log4j.appender.OrderLog=org.apache.log4j.RollingFi leAppender

    > log4j.appender.OrderLog.File=C:/logs/OrderLog.txt

    > log4j.appender.OrderLog.Append=true

    > log4j.appender.OrderLog.MaxFileSize=100KB

    > log4j.appender.OrderLog.MaxBackupIndex=5

    > log4j.appender.OrderLog.layout=org.apache.log4j.Pa tternLayout

    > log4j.appender.OrderLog.layout.ConversionPattern= %d : %-5p %F : %L: - %m%n

    > log4j.logger.com.bowstreet.solutions.OrderLog=DEBU G, OrderLog

    >

    > I guess after maxbackupindex reached, it might have giving problem..

    > How to resolve this.. any idea..

    > It is working fine in Windows os.. It is giving problem in AIX box. env..
    >

    I cannot imagine how "C:/logs/OrderLog.txt" could possibly work in AIX.

    Ken

  3. Re: Interrupted logger writing Issue

    rameshmessages@gmail.com wrote:
    > Hi

    > I am facing a problem some time, logging stopped and again started at some point again..

    >

    > Here is the Log4j.properties file content

    >

    > log4j.rootCategory=DEBUG, OrderLog

    > log4j.appender.OrderLog=org.apache.log4j.RollingFi leAppender

    > log4j.appender.OrderLog.File=C:/logs/OrderLog.txt

    > log4j.appender.OrderLog.Append=true

    > log4j.appender.OrderLog.MaxFileSize=100KB

    > log4j.appender.OrderLog.MaxBackupIndex=5

    > log4j.appender.OrderLog.layout=org.apache.log4j.Pa tternLayout

    > log4j.appender.OrderLog.layout.ConversionPattern= %d : %-5p %F : %L: - %m%n

    > log4j.logger.com.bowstreet.solutions.OrderLog=DEBU G, OrderLog

    >

    > I guess after maxbackupindex reached, it might have giving problem..

    > How to resolve this.. any idea..

    > It is working fine in Windows os.. It is giving problem in AIX box. env..


    Is it possible that you have multiple processes, multiple WARs, or multiple
    EARs writing to the same file? If so, this is not safe for log4j rolling
    appenders. It seems that if one writer is rolling while another is writing,
    logging may cease or may continue trying to write to the old file instead of
    to the new one.

    That may not be your issue, but it's worth checking.
    --
    Doug

  4. Re: Interrupted logger writing Issue

    for Windows OS



    log4j.rootCategory=DEBUG, OrderLog

    log4j.appender.OrderLog=org.apache.log4j.RollingFi leAppender

    log4j.appender.OrderLog.File=C:/logs/OrderLog.txt

    log4j.appender.OrderLog.Append=true

    log4j.appender.OrderLog.MaxFileSize=100KB

    log4j.appender.OrderLog.MaxBackupIndex=5

    log4j.appender.OrderLog.layout=org.apache.log4j.Pa tternLayout

    log4j.appender.OrderLog.layout.ConversionPattern= %d : %-5p %F : %L: - %m%n

    log4j.logger.com.bowstreet.solutions.OrderLog=DEBU G, OrderLog



    for AIX OS



    log4j.rootCategory=DEBUG, OrderLog

    log4j.appender.OrderLog=org.apache.log4j.RollingFi leAppender

    log4j.appender.OrderLog.File=/app/IBM/WebSphere/PortalServer1/log/applogs/OrderLog.txt

    log4j.appender.OrderLog.Append=true

    log4j.appender.OrderLog.MaxFileSize=100KB

    log4j.appender.OrderLog.MaxBackupIndex=5

    log4j.appender.OrderLog.layout=org.apache.log4j.Pa tternLayout

    log4j.appender.OrderLog.layout.ConversionPattern= %d : %-5p %F : %L: - %m%n

    log4j.logger.com.bowstreet.solutions.OrderLog=DEBU G, OrderLog

  5. Re: Interrupted logger writing Issue

    Hi Doug,



    Thank you for your response...

    I am using one logger for one war application( each war has it's one logging file ).

    It is working fine in Windows.. it is giving problem only AIX box.

  6. Re: Interrupted logger writing Issue

    rameshmessages@gmail.com wrote:
    > Hi

    > I am facing a problem some time, logging stopped and again started at some point again..

    >

    > Here is the Log4j.properties file content

    >

    > log4j.rootCategory=DEBUG, OrderLog

    > log4j.appender.OrderLog=org.apache.log4j.RollingFi leAppender

    > log4j.appender.OrderLog.File=C:/logs/OrderLog.txt

    > log4j.appender.OrderLog.Append=true

    > log4j.appender.OrderLog.MaxFileSize=100KB

    > log4j.appender.OrderLog.MaxBackupIndex=5

    > log4j.appender.OrderLog.layout=org.apache.log4j.Pa tternLayout

    > log4j.appender.OrderLog.layout.ConversionPattern= %d : %-5p %F : %L: - %m%n

    > log4j.logger.com.bowstreet.solutions.OrderLog=DEBU G, OrderLog

    >

    > I guess after maxbackupindex reached, it might have giving problem..

    > How to resolve this.. any idea..

    > It is working fine in Windows os.. It is giving problem in AIX box. env..


    What version of WebSphere, and what version of log4j?

    Also, by any chance are you using Crystal Reports jars in any of your WARs?
    Crystal's use of log4j definitely halts application logging and requires a
    custom property to change Crystal's behaviour. (Since we don't have any WAS
    Windows systems, I have no idea whether Crystal libraries on Windows have the
    same effect.)

    However, we have recently had log4j logging stop in cases where we don't
    believe that these known problems are the cause. We're on WAS 6.1.0.7 on AIX.

    The thing is... we've been on that version of WAS for many, many months, and
    we've only seen that problem recently. So while it's possible it's a problem
    with WAS, it's not certain, and it seems it would be very difficult to prove
    that for a PMR. If you can get it to happen consistently, you should probably
    contact support.

    --
    Doug

  7. Re: Interrupted logger writing Issue

    Hi Doug,



    Thanks a lot for sharing your thoughts and ideas.



    Our Application is a Portal using WebSphere Portlet Factory on WebSphere Portal Server v6.

    We are not using Crystal Reports and



    Here is the versions of products used in our project.

    1] AIX version information

    5.3.0.0 and release 05



    2] Log4j Version

    Implementation-Version: 1.2.7



    3] WAS Version

    IBM WebSphere Application Server - ND, 6.0.2.19

    Build Number: cf190715.13

    Build Date: 4/19/07



    4] WPS Version



    product=IBM WebSphere Portal Server

    version=6.0.0.0

    fixlevel=0

    mode=standard

    buildnumber=wp600_245



    5] WebSphere Portlet Factory Version 6.0.1



    Thanks in advance

    :-)



    Ramesh Munagala

  8. Re: Interrupted logger writing Issue

    rameshmessages@gmail.com wrote:
    > Hi Doug,

    >

    > Thanks a lot for sharing your thoughts and ideas.

    >

    > Our Application is a Portal using WebSphere Portlet Factory on WebSphere Portal Server v6.

    > We are not using Crystal Reports and

    >

    > Here is the versions of products used in our project.

    > 1] AIX version information

    > 5.3.0.0 and release 05

    >

    > 2] Log4j Version

    > Implementation-Version: 1.2.7

    >

    > 3] WAS Version

    > IBM WebSphere Application Server - ND, 6.0.2.19

    > Build Number: cf190715.13

    > Build Date: 4/19/07

    >

    > 4] WPS Version

    >

    > product=IBM WebSphere Portal Server

    > version=6.0.0.0

    > fixlevel=0

    > mode=standard

    > buildnumber=wp600_245

    >

    > 5] WebSphere Portlet Factory Version 6.0.1

    >

    > Thanks in advance

    > :-)

    >

    > Ramesh Munagala


    I have no further ideas, then. Again, if you can get this behaviour to repeat
    fairly easily, I think you should contact support.

    --
    Doug

  9. Re: Interrupted logger writing Issue

    Doug Breaux wrote:
    > rameshmessages@gmail.com wrote:
    >> Hi Doug,

    >>

    >> Thanks a lot for sharing your thoughts and ideas.

    >>

    >> Our Application is a Portal using WebSphere Portlet Factory on
    >> WebSphere Portal Server v6.

    >> We are not using Crystal Reports and

    >>

    >> Here is the versions of products used in our project.

    >> 1] AIX version information

    >> 5.3.0.0 and release 05

    >>

    >> 2] Log4j Version

    >> Implementation-Version: 1.2.7

    >>

    >> 3] WAS Version

    >> IBM WebSphere Application Server - ND, 6.0.2.19

    >> Build Number: cf190715.13

    >> Build Date: 4/19/07

    >>

    >> 4] WPS Version

    >>

    >> product=IBM WebSphere Portal Server

    >> version=6.0.0.0

    >> fixlevel=0

    >> mode=standard

    >> buildnumber=wp600_245

    >>

    >> 5] WebSphere Portlet Factory Version 6.0.1

    >>

    >> Thanks in advance

    >> :-)

    >>

    >> Ramesh Munagala

    >
    > I have no further ideas, then. Again, if you can get this behaviour to
    > repeat fairly easily, I think you should contact support.
    >


    Oh, I'd also move to a newer log4j. 1.2.15 is the current 1.2 level.

    --
    Doug

+ Reply to Thread