Bugzilla – Full Text Bug Listing
| Summary: | Exception logging when rollingback transaction in @PreUpdate | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Pie Mur <piemur2000> | ||||||||||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||||||||||
| Status: | NEW --- | QA Contact: | |||||||||||||
| Severity: | normal | ||||||||||||||
| Priority: | P3 | CC: | martin.grebac, tom.ware | ||||||||||||
| Version: | unspecified | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Hardware: | PC | ||||||||||||||
| OS: | Windows 7 | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Bug Depends on: | |||||||||||||||
| Bug Blocks: | 454792 | ||||||||||||||
| Attachments: |
|
||||||||||||||
Have you tried setting the persistence unit property: eclipselink.logging.exceptions to false? (In reply to comment #1) > Have you tried setting the persistence unit property: > eclipselink.logging.exceptions to false? Yes, I added the property to my persistence.xml file but the result is the same. Created attachment 211260 [details]
The persistence configuration file.
Created attachment 211261 [details]
TestEntity source file
Created attachment 211262 [details]
TestSession source file
Created attachment 211263 [details]
Server log after calling testRollback and testRollback2
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
Created attachment 210787 [details] The entity and session source code + log output. When I rollback a transaction by sending a RuntimeException in the @PreUpdate method of an entity eclipselink log the exception details several times before I can catch it. Steps to reproduce: 1) Modify an entity in a session bean. 2) Flush the entity manager to commit the changes. 3) Throw an exception in @PreUpdate. 4) Catch the exception in the session bean. Actual result: The exception description and stack trace is logged twice before I can catch it.