Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336446

Summary:

First connection to an empty default h2-DB leads to multiple logged errors

Product:

[Technology] Jubula

Reporter:

Markus Tiede <markus.tiede>

Component:

Core

Assignee:

Zeb Ford-Reitz <zeb.ford-reitz>

Status:

CLOSED FIXED

QA Contact:

Oussama <Oussama.Bouchhioua>

Severity:

normal

Priority:

CC:

Achim.Loerke

Version:

0.9.0

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
first login error log	none

Description Markus Tiede

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

2011-02-08 04:37:15 EST

Check with EclipseLink for logging config

Comment 2 Zeb Ford-Reitz

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

2011-03-14 10:15:35 EDT

There are no logged problems after the first connection to the h2-db any more.