[eclipselink-users] Question about logging levels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipselink-users] Question about logging levels

From: NBW <emailnbw@xxxxxxxxx>
Date: Fri, 12 Aug 2011 15:32:13 -0400
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

The Eclipselink wiki notes [1] that when setting eclipselink.logging.level to WARNING a stack trace is not included. However, with that property set to WARNING I am seeing a stack track printed out in my server.log (Glassfish 3.1 b45) when a org.eclipse.persistence.exceptions.OptimisticLockException is thrown from inside an EJB.

Is this an issue with the documentation, a bug in Eclipselink 2.2.0v20110202-r8913, or a misunderstanding on my part?

Thanks,

-Noah

[1] - http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_%28ELUG%29#Using_EclipseLink_JPA_Extensions_for_Logging

Follow-Ups:
- Re: [eclipselink-users] Question about logging levels
  - From: James Sutherland

Prev by Date: Re: [eclipselink-users] Upgrading from 2.1.3 to 2.3.0
Next by Date: [eclipselink-users] SecondaryTable question
Previous by thread: [eclipselink-users] Upgrading from 2.1.3 to 2.3.0
Next by thread: Re: [eclipselink-users] Question about logging levels
Index(es):
- Date
- Thread

Breadcrumbs