Ok,
I did some further experimentation
>From what I see, the TransactDatabaseLocker has the same behaviour. I
really dont see where they commit in their lockers at all.
The only thing which works for me is setUseDataBaseLock(false). This
is not as dangerous as it sounds, at least for me. My ActiveMQ
instances all have their embedded brokers so there will never be a
failover situation
As for your request how to configure this in the config file, I have
no idea - I dont use their config files but set up everything with
code:
System.setProperty("h2.lobInDatabase", "true");
System.setProperty("h2.defaultMaxLengthInplaceLob2", "4096");
JdbcDataSource ds = new JdbcDataSource();
StringBuffer url = new StringBuffer();
ds.setURL("jdbc:h2:" +
_DataDirectory.getAbsolutePath() + File.separator +
_DataDirectory.getName() +
";DB_CLOSE_DELAY=-1" );
JDBCPersistenceAdapter jdbcPersistenceAdapter = new
JDBCPersistenceAdapter( ds,
new OpenWireFormat() );
jdbcPersistenceAdapter.setUseDatabaseLock( false );
return jdbcPersistenceAdapter;
Again, thanks for your help
Regards
Alex
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
