Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336446 - First connection to an empty default h2-DB leads to multiple logged errors
Summary: First connection to an empty default h2-DB leads to multiple logged errors
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Zeb Ford-Reitz CLA
QA Contact: Oussama CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-06 06:15 EST by Markus Tiede CLA
Modified: 2011-03-14 10:15 EDT (History)
1 user (show)

See Also:

Attachments
first login error log (74.28 KB, text/plain)
2011-02-06 06:15 EST, Markus Tiede CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Tiede CLA 2011-02-06 06:15:44 EST 
Created attachment 188404 [details]
first login error log

The first connection attempt to an empty default h2-DB leads to multiple logged errors. See the attached log file for further details.
Comment 1 Achim Loerke CLA 2011-02-08 04:37:15 EST 
Check with EclipseLink for logging config
Comment 2 Zeb Ford-Reitz CLA 2011-03-09 10:19:34 EST 
fixed by http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=a1fe7e6b6c9aae11d045f55620d9c03af0eca814

I've set EclipseLink's log level to SEVERE, so the warnings (caused by trying to drop non-existing tables) are not logged.
Comment 3 Markus Tiede CLA 2011-03-14 10:15:35 EDT 
There are no logged problems after the first connection to the h2-db any more.