Hi,
Sorry, I don't know what the problem might be. I guess I would add a few
lines System.out to understand what is executed and what not.
Regards,
Thomas
On Fri, Nov 1, 2013 at 7:56 PM, marcolopes wrote:
> No. Jars are never modified by Eclipse Product Export.
>
> On Friday, November 1, 201
Hi,
I don't know what you do exactly, but I can not reproduce it. Could you
provide a simple, reproducible test case? My test case is: I create a
database "test". After that there is a file called "test.h2.db". Then I
backup this file 4 times, and that works, and no .lock.db files are created.
*p
I opted to ZIP it myself using zip4j and avoid H2 internal methods. Works
flawlessly.
On Saturday, November 2, 2013 9:08:36 AM UTC, Thomas Mueller wrote:
>
> Hi,
>
> Sorry, I don't know what the problem might be. I guess I would add a few
> lines System.out to understand what is executed and wha
Thomas, i know what's going on...
1) The first backup is made
2) The database is opened (i'm using Datanucleus persistence, so, no
control from my code)
3) A database LOCK file is created
4) I close the "Persistence Manager Factory" but the LOCK file is not
released... (it is released only when
Then it sounds like the problem is with datanucleus not closing it's
connection to the db. Perhaps it needs some special call or parameter to
tell it that?
Or are you using db_close_delay in your db URL? Which would also cause the
db to not close when the last connection is closed.
Or maybe you are
Personally I would say that this is a bug in the application logic that
should be fixed. Silent data loss is a very big no-no :-)
On Saturday, 2 November 2013, Frank Ratzlow wrote:
> Hallo Thomas,
>
> I hoped for some undocumented Sybase compatibility mode :) but trigger
> sounds interesting. The
Hi,
Copying the database file while the database is open is not a good idea. It
will work in most cases, but not in all cases (for example if the
transaction log is rolled over while the backup is in progress). When it
doesn't work, the database will be corrupt. Don't blame us for that.
If you wa
Hi,
Copying the database file while the database is open is not a good idea. It
will work in most cases, but not in all cases (for example if the
transaction log is rolled over while the backup is in progress). When it
doesn't work, the database will be corrupt. Don't blame us for that.
If you wa
Hi,
I would probably also change the application. I don't know a database
engine that silently truncates data in the way Sybase does. See also
http://stackoverflow.com/questions/13912434/how-to-detect-string-truncation
Regards,
Thomas
On Sat, Nov 2, 2013 at 3:53 PM, Noel Grandin wrote:
> Per
Thomas, this only happens if the user misses the "login"...
1) Backup the **closed** database
2) Login is attempted and fails
3) Database is closed (well, i issue the datanucleus PFM.close that shoud
close ALL connections / poolmanager)
4) Back to step 1 - and that is where it might be problemati
Hi,
H2 doesn't "miss the unlock". I'm sure this is not a problem in the
database. It is clearly a problem on your side.
Regards,
Thomas
On Sat, Nov 2, 2013 at 4:27 PM, marcolopes wrote:
> Thomas, this only happens if the user misses the "login"...
>
> 1) Backup the **closed** database
> 2) Lo
Thomas, i was looking at the H2 sources and i believe that you monitor the
file LOCK with a daemon Thread. My question is: HOW do you create the File
Lock? Using the java native TEMP file creator?
*TEST CASE*:
File lock=new File(DATABASE_NAME+".lock.db");
Cl
UPDATE: In my test case, *the unlock is reached, after ~10 seconds*... is
the default DB_CLOSE_DELAY changed to this default? This was confusing me,
as i thought the unlock was never reached, so, it would be a H2 bug.
I assume now that Datanucleus PMF.close is not closing the connection.
Thanks
"shutdown compact" recovers about 8% of the space.
On Friday, November 1, 2013 10:56:02 AM UTC-7, Thomas Mueller wrote:
>
> Hi,
>
> Did you use the SQL statement SHUTDOWN COMPACT?
> http://h2database.com/html/grammar.html#shutdown
>
> Regards,
> Thomas
>
>
>
> On Fri, Nov 1, 2013 at 6:54 PM, Bria
You are right. After some extensive debug, *is the use of a Pool
Manager*(either internal or external do Datanucleus core) that is causing the
problem.
Can't find any other method than CLOSE (and since DN takes care of the pool
initialization, i believe it's out of my control)
DB_CLOSE_DELAY,
This problem is related to MAC, and not related to the database being
opened.
*The database **is** closed*, and the Internal H2 backup fails to execute,
and does not throw any exception / info.
So, i had to use a third party lib to execute the file ZIP myself.
On Saturday, November 2, 2013 2:5
16 matches
Mail list logo
