Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 9.1pe
    • Fix Version/s: not determined
    • Component/s: logging
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      3,905
    • Status Whiteboard:
      Hide

      as91ur1-na

      Show
      as91ur1-na

      Description

      Hi,

      I'm trying to do some load testing of a simple GF2 Instance (cluster profile,
      single server) in a nodeagent (local) hosted on linux 32 bit.

      I have reconfigured the Log directory to be
      /opt/logs/gf/$

      {com.sun.aas.instanceName}

      /server.log because deployer should be
      able to see their log files and we have a virtual host pointing to /opt/logs/gf
      (every server will then have it's own folder).

      Everything is working fine until the log file reach 2 MB (the logger settings
      specifies 2000000 Bytes) at which point, the log is backuped in a file with the
      timestamp. Up to now, everything is working as it should

      The problem starts here: The server doesn't create a new "server.log" file and a
      new log file is created under /opt/glassfish/nodeagents/<node>/<server>/logs
      with a lot of exceptions:

      [#|2007-12-07T10:48:01.750+0100|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=14;_ThreadName=httpSSLWorkerThread-38302-2;_RequestID=5418adb4-e669-4bb4-bee0-0b188d0973b3;|
      Exception in openFile...java.io.FileNotFoundException:
      /opt/logs/gf/lidip_01/server.log (No such file or directory)|#]

      [#|2007-12-07T10:48:01.764+0100|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=14;_ThreadName=httpSSLWorkerThread-38302-2;_RequestID=5418adb4-e669-4bb4-bee0-0b188d0973b3;|
      java.io.FileNotFoundException: /opt/logs/gf/lidip_01/server.log (No such file or
      directory)
      at java.io.FileInputStream.open(Native Method)
      at java.io.FileInputStream.<init>(FileInputStream.java:106)
      at java.io.FileInputStream.<init>(FileInputStream.java:66)
      at
      com.sun.enterprise.server.logging.logviewer.backend.LogFile.getLogFileReader(LogFile.java:281)
      at
      com.sun.enterprise.server.logging.logviewer.backend.LogFile.buildLogFileIndex(LogFile.java:156)
      at
      com.sun.enterprise.server.logging.logviewer.backend.LogFile.<init>(LogFile.java:71)
      at
      com.sun.enterprise.server.logging.FileandSyslogHandler$1.run(FileandSyslogHandler.java:399)
      at java.security.AccessController.doPrivileged(Native Method)
      at
      com.sun.enterprise.server.logging.FileandSyslogHandler.rotate(FileandSyslogHandler.java:366)
      at
      com.sun.enterprise.server.logging.FileandSyslogHandler.publish(FileandSyslogHandler.java:505)
      at java.util.logging.Logger.log(Logger.java:472)
      at java.util.logging.Logger.doLog(Logger.java:494)
      at java.util.logging.Logger.log(Logger.java:517)
      at
      com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:368)
      at java.io.PrintStream.write(PrintStream.java:432)
      at
      com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.write(SystemOutandErrHandler.java:293)
      at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
      at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
      at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
      at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
      ....

      This log file is filling up kind of fast (no wonder with all the stack traces by
      each "log" call) and the rotation is actually working (without making any
      backup, however). After a while, the server restarts on it's own and a new
      server.log in the right directory is created.

        Activity

        Hide
        basler added a comment -

        This will have to be researched for the next release, not a 91ur1 release stopper

        Show
        basler added a comment - This will have to be researched for the next release, not a 91ur1 release stopper
        Hide
        sanandal added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        sanandal added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        vkoniecz added a comment -
            • Issue 3905 has been confirmed by votes. ***
        Show
        vkoniecz added a comment - Issue 3905 has been confirmed by votes. ***
        Hide
        vkoniecz added a comment -

        Reproduced very easily on GF 2.1.1.

        Show
        vkoniecz added a comment - Reproduced very easily on GF 2.1.1.
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

          • Assignee:
            dpatil
            Reporter:
            granat
          • Votes:
            2 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: