bugzilla | 1 Jun 2004 21:18
Picon
Favicon

DO NOT REPLY [Bug 29330] New: - Linkage Error when initializing application

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29330>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29330

Linkage Error when initializing application

           Summary: Linkage Error when initializing application
           Product: Log4j
           Version: 1.2
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev <at> jakarta.apache.org
        ReportedBy: cpb <at> trifecta.com

I'm not sure if this really qualifies as a bug, but I was hoping somebody might 
have some idea what cause the following linkage error. Running application on 
WebSphere Application Server V4.0.7.

[4/6/04 12:01:24:850 EDT]   75f5b7 ServletInstan X SRVE0100E: Did not realize  
init() exception thrown by servlet DEsMatterAdminController: 
javax.servlet.ServletException: loader constraints violated when linking 
org/apache/log4j/Level class
(Continue reading)

bugzilla | 1 Jun 2004 21:25
Picon
Favicon

DO NOT REPLY [Bug 29330] - Linkage Error when initializing application

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29330>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29330

Linkage Error when initializing application

ceki <at> apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED
bugzilla | 1 Jun 2004 21:24
Picon
Favicon

DO NOT REPLY [Bug 29330] - Linkage Error when initializing application

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29330>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29330

Linkage Error when initializing application

ceki <at> apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME

------- Additional Comments From ceki <at> apache.org  2004-06-01 19:24 -------

This is most probably a problem with your environment and not a log4j bug.
Your best bet is to ask for help on log4j-user <at> logging.apache.org.
ceki | 1 Jun 2004 22:29
Picon
Favicon

cvs commit: logging-log4j/src/java/org/apache/log4j/db ConnectionSourceSkeleton.java

ceki        2004/06/01 13:29:13

  Modified:    src/java/org/apache/log4j/db ConnectionSourceSkeleton.java
  Log:
  If the JDBC driver is not 3.0 compliant, then it might throw an
  exception when the DatabaseMetaData.supportsGetGeneratedKeys method is
  called.

  We cater for that eventuality.

  Revision  Changes    Path
  1.4       +10 -1     logging-log4j/src/java/org/apache/log4j/db/ConnectionSourceSkeleton.java

  Index: ConnectionSourceSkeleton.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/db/ConnectionSourceSkeleton.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- ConnectionSourceSkeleton.java	24 May 2004 16:14:34 -0000	1.3
  +++ ConnectionSourceSkeleton.java	1 Jun 2004 20:29:13 -0000	1.4
   <at>  <at>  -49,13 +49,22  <at>  <at> 
           return;
         }
         DatabaseMetaData meta = connection.getMetaData();
  -      supportsGetGeneratedKeys = meta.supportsGetGeneratedKeys();
  +      supportsGetGeneratedKeys = supportsGetGeneratedKeys(meta);
         dialectCode = Util.discoverSQLDialect(meta);
       } catch (SQLException se) {
         LogLog.warn("Could not discover the dialect to use.", se);
(Continue reading)

noreply | 1 Jun 2004 22:32
Picon

[GUMP <at> brutus]: logging-log4j/log4j-tests failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact folk at general <at> gump.apache.org.

Project log4j-tests has an issue affecting its community integration, and has been outstanding for 21 runs.
Project State : 'Failed', Reason 'Build Failed'

Full details are available at:

    http://brutus.apache.org:8080/gump/logging-log4j/log4j-tests/index.html

That said, some snippets follow:

The following annotations were provided:
 -INFO- Made directory [/usr/local/gump/public/workspace/logging-log4j/tests/classes]
 -INFO- Enable "debug" output, due to a sequence of 20 previous errors.
 -INFO- Failed with reason build failed

The following work was performed:
http://brutus.apache.org:8080/gump/logging-log4j/log4j-tests/gump_work/build_logging-log4j_log4j-tests.html
Work Name: build_logging-log4j_log4j-tests (Type: Build)
State: Failed
Elapsed: 0 hours, 2 minutes, 4 seconds
Command Line: java -Djava.awt.headless=true
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar
org.apache.tools.ant.Main -debug -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only regression 
[Working Directory: /usr/local/gump/public/workspace/logging-log4j/tests]
(Continue reading)

Shapira, Yoav | 2 Jun 2004 17:03

Log4j article on java.sun.com


Hi,
There's an article on java.sun.com
(http://developers.sun.com/prodtech/appserver/reference/techart/log4j.ht
ml) on using log4j in the SunOne Application Server.  It's nice and
surprising to see an article on using log4j, on the Sun site, on the
front page, written by Sun marketing people.  

Yoav Shapira
Millennium Research Informatics

This e-mail, including any attachments, is a confidential business communication, and may contain
information that is confidential, proprietary and/or privileged.  This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone
else.  If you are not the(an) intended recipient, please immediately delete this e-mail from your
computer system and notify the sender.  Thank you.
ceki | 2 Jun 2004 22:57
Picon
Favicon

cvs commit: logging-log4j/src/java/org/apache/log4j/db ConnectionSourceSkeleton.java

ceki        2004/06/02 13:57:27

  Modified:    src/java/org/apache/log4j/db ConnectionSourceSkeleton.java
  Log:
  java.lang.AbstractMethodError is an error not an exception.
  AbstractMethodErroris thrown when DBAppender is used with older
  JDBC drivers.

  Revision  Changes    Path
  1.5       +3 -2      logging-log4j/src/java/org/apache/log4j/db/ConnectionSourceSkeleton.java

  Index: ConnectionSourceSkeleton.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/db/ConnectionSourceSkeleton.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- ConnectionSourceSkeleton.java	1 Jun 2004 20:29:13 -0000	1.4
  +++ ConnectionSourceSkeleton.java	2 Jun 2004 20:57:27 -0000	1.5
   <at>  <at>  -59,8 +59,9  <at>  <at> 
     boolean supportsGetGeneratedKeys(DatabaseMetaData meta) {
       try {
         return meta.supportsGetGeneratedKeys();
  -    } catch(Exception e) {
  -      LogLog.warn("Could not call supportsGetGeneratedKeys method.", e);
  +    } catch(Throwable e) {
  +      LogLog.warn("The following warning is only informative.");
  +      LogLog.warn("Could not call supportsGetGeneratedKeys method. This may be recoverable", e);
         return false;
       }
(Continue reading)

Henrik Bentel | 3 Jun 2004 09:13
Picon

Wiki TODO up to date?

Hi

I've been using log4j for quite a while and I'm looking forward to 1.3 
(especially WatchDogs and Receivers)
I looked at the wiki page to see how things are going.
http://wiki.apache.org/logging-log4j/Log4JProjectPages/ToDo

Last update date was late January.

I was thinking about helping out with whatever I can so that 1.3 will be 
released sooner.

So if the todo list was updated.....

thanks for a great tool

-Henrik Bentel
sdeboy | 3 Jun 2004 09:17
Picon
Favicon

cvs commit: logging-log4j/src/java/org/apache/log4j/varia LogFilePatternReceiver.java

sdeboy      2004/06/03 00:17:33

  Modified:    src/java/org/apache/log4j/varia LogFilePatternReceiver.java
  Log:
  Added support in LogFilePatternReceiver for PROPERTIES, which can be used to convert MDC or delimited NDC
entries in the file into a PROPERTY
  Use PROP(keyname) in the log format definition - this will assign whatever value is in that position in the
file to the 'keyname' property on the event.
  NOTE the use of parentheses to delimit the property key.

  Revision  Changes    Path
  1.11      +35 -9     logging-log4j/src/java/org/apache/log4j/varia/LogFilePatternReceiver.java

  Index: LogFilePatternReceiver.java
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/java/org/apache/log4j/varia/LogFilePatternReceiver.java,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- LogFilePatternReceiver.java	28 May 2004 07:19:16 -0000	1.10
  +++ LogFilePatternReceiver.java	3 Jun 2004 07:17:33 -0000	1.11
   <at>  <at>  -64,7 +64,8  <at>  <at> 
    * RELATIVETIME
    * MESSAGE
    * *
  - *
  + * PROP(key)
  + * 
    * For example,
    *
(Continue reading)

yoavs | 3 Jun 2004 15:52
Picon
Favicon
Gravatar

cvs commit: logging-log4j/src/xdocs documentation.xml

yoavs       2004/06/03 06:52:03

  Modified:    src/xdocs documentation.xml
  Log:
  Added link to Sun article.

  Revision  Changes    Path
  1.38      +5 -2      logging-log4j/src/xdocs/documentation.xml

  Index: documentation.xml
  ===================================================================
  RCS file: /home/cvs/logging-log4j/src/xdocs/documentation.xml,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- documentation.xml	4 May 2004 14:26:04 -0000	1.37
  +++ documentation.xml	3 Jun 2004 13:52:03 -0000	1.38
   <at>  <at>  -3,6 +3,7  <at>  <at> 

     <properties>
       <author email="ceki <at> apache.org">Ceki Gulcu</author>
  +    <author email="yoavs <at> apache.org">Yoav Shapira</author>
       <title>Documentation</title>
     </properties>

   <at>  <at>  -136,13 +137,15  <at>  <at> 
               </li>
            </p>

  -
(Continue reading)


Gmane