Bug 1057039 - Setting org.apache.ode log level to DEBUG floods log with WARN messages
Summary: Setting org.apache.ode log level to DEBUG floods log with WARN messages
Keywords:
Status: ON_QA
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: BPEL Integration
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER2
: 6.2.0
Assignee: Rob Cernich
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-23 11:29 UTC by Jiri Pechanec
Modified: 2023-05-15 19:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If you set the org.apache.ode log category to DEBUG it starts to flood the log with error messages. As a result, the log becomes hard to read and uses up drive space.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jiri Pechanec 2014-01-23 11:29:45 UTC 
If org.apache.ode log category is te to DEBUG it starts to genertae a lot of WARN to log
12:15:37,714 WARN  [org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl] (ODEServer-1) HHH000387: ResultSet's statement was not registered
12:15:37,718 INFO  [org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl] (ODEServer-1) HHH000106: Forcing container resource cleanup on transaction completion
12:15:38,724 WARN  [org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl] (ODEServer-1) HHH000387: ResultSet's statement was not registered
12:15:38,726 INFO  [org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl] (ODEServer-1) HHH000106: Forcing container resource cleanup on transaction completion
12:15:39,730 WARN  [org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl] (ODEServer-1) HHH000387: ResultSet's statement was not registered
12:15:39,733 INFO  [org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl] (ODEServer-1) HHH000106: Forcing container resource cleanup on transaction completion
12:15:40,739 WARN  [org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl] (ODEServer-1) HHH000387: ResultSet's statement was not registered

...
Comment 2 kconner 2015-03-05 17:14:06 UTC 
This should have been fixed in the underlying Hibernate version, see https://hibernate.atlassian.net/browse/HHH-8210 for details.
Note You need to log in before you can comment on or make changes to this bug.