logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <gyoergy.mag...@bhf.ing.com>
Subject AW: JDK compatibility
Date Fri, 23 Jul 2004 13:50:01 GMT
Sorry,

I don't have the StackTrace any longer. There is only one thing I remember:
It did not come up with a difference (change) in an interface or super class (like "method
has previously been static" or "MethodNotFound") It simply stated that there was a compatbility
issue). I can't remember the exact error message. We removed the jar file from the lib and
everything worked okay afterwards.

György
-----Ursprüngliche Nachricht-----
Von: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com] 
Gesendet: Freitag, 23. Juli 2004 15:38
An: Log4J Users List
Betreff: RE: JDK compatibility


Hi,
Do you remember the specific conflict or error?  I'm very surprised to hear of this between
1.2.5 and 1.2.8 as there were no class hierarchy or interface changes that I'm aware of.

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: gyoergy.magoss@bhf.ing.com [mailto:gyoergy.magoss@bhf.ing.com]
>Sent: Friday, July 23, 2004 9:38 AM
>To: log4j-user@logging.apache.org
>Subject: AW: JDK compatibility
>
>We had a similiar problem, when someone unintentionally deployed a newer
>version of log4j  (1.2.8, but we are still on 1.2.5) as a jar file in the
>lib directory of a webapplication. Depending on which application was
>called first (and thus initialized our environment) sometimes the newer
>log4j classes and interfaces where loaded first. When (after that) another
>application tried to log, the (older versioned) logger in it's class path
>couldn't be instantiated because of a version conflict with the already
>loaded interfaces of the newer log4j version.
>
>
>-----Ursprüngliche Nachricht-----
>Von: Lutz Michael [mailto:michael.h.lutz@siemens.com]
>Gesendet: Donnerstag, 22. Juli 2004 21:22
>An: 'Log4J Users List'
>Betreff: RE: JDK compatibility
>
>
>
>
>Yoav, thank you very much (as always) for your response.
>
>Unfortunately because of the nature of the error (and possibly because of
>the implementation of the MS JVM) we are not getting a stack trace
>pinpointing the problem.  The end of the stack trace is vague.
>
>Most of our application runs on a different VM, so because we wrapped Log4j
>we are going to just substitute a "dumb" file logger for now when we're
>running under J++, this has been deemed an acceptable work-around.  So for
>now we're OK.
>
>If we get a better stack trace I'll follow up with the information.
>
>Regards,
>Mike
>
>-----Original Message-----
>From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
>Sent: Wednesday, July 21, 2004 2:39 PM
>To: Log4J Users List
>Subject: RE: JDK compatibility
>
>
>Hi,
>The Visual J++ JVM is 1.1-compatible supposedly, but it's different from
>Sun's 1.1.  Can you run OK on Sun 1.1?  What's the full stack trace for
>the NoClassDefFoundError?
>
>Yoav Shapira
>Millennium Research Informatics
>
>
>>-----Original Message-----
>>From: Lutz Michael [mailto:michael.h.lutz@siemens.com]
>>Sent: Wednesday, July 21, 2004 2:29 PM
>>To: Log4J Users List; Anderson Ian
>>Subject: JDK compatibility
>>
>>
>>
>>We're experiencing problems with Log4j running on J++, JDK 1.1.4.  We
>found
>>on the FAQ that Log4j is 1.1.x compatible.
>>
>>Specifically, a NoClassDefFound error is being generated.  Does anyone
>have
>>any ideas on a work-around, or are we doing something wrong?  Can we
>run
>>Log4j on Visual J++?
>>
>>Thanks in advance.
>>Mike
>>
>>_______________________________________________
>>Siemens Medical Solutions Health Services
>>Michael Lutz
>>Software Engineer, Soarian Common Components
>>51 Valley Stream Parkway, Malvern, PA 19355
>>Office / Voice Mail	+01 610-219-8613
>>Cell			+01 610-952-2289
>>Home Office		+01 610-989-3623
>>Fax			+01 610-219-4004
>>E-mail <mailto:michael.h.lutz@siemens.com>
>>_______________________________________________
>>
>>
>>-----------------------------------------------------------------------
>----
>>----
>>This message and any included attachments are from Siemens Medical
>>Solutions
>>USA, Inc. and are intended only for the addressee(s).
>>The information contained herein may include trade secrets or
>privileged or
>>otherwise confidential information.  Unauthorized review, forwarding,
>>printing,
>>copying, distributing, or using such information is strictly prohibited
>and
>>may
>>be unlawful.  If you received this message in error, or have reason to
>>believe
>>you are not authorized to receive it, please promptly delete this
>message
>>and
>>notify the sender by e-mail with a copy to
>>Central.SecurityOffice@shs.siemens.com
>>
>>Thank you
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>---------------------------------------------------------------------------
>----
>This message and any included attachments are from Siemens Medical
>Solutions
>USA, Inc. and are intended only for the addressee(s).
>The information contained herein may include trade secrets or privileged or
>otherwise confidential information.  Unauthorized review, forwarding,
>printing,
>copying, distributing, or using such information is strictly prohibited and
>may
>be unlawful.  If you received this message in error, or have reason to
>believe
>you are not authorized to receive it, please promptly delete this message
>and
>notify the sender by e-mail with a copy to
>Central.SecurityOffice@shs.siemens.com
>
>Thank you
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message