RE: [JBoss-dev] hsqldb options

2003-03-31 Thread Bill Burke
Of Peter Fagerlund Sent: Sunday, March 30, 2003 6:29 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] hsqldb options söndagen den 30 mars 2003 kl 20.33 skrev marc fleury: why don't we bring them on then? Send in another X number troops to fix the non result .. Pulezzze what is the non

RE: [JBoss-dev] hsqldb options

2003-03-31 Thread Adrian Brock
-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] hsqldb options Date: Mon, 31 Mar 2003 10:49:10 -0500 Sorry Peter, no offesne, but But could somebody explain what the hell he just posted? Sacha, pointed out McKoi. I'd like to see how good of a DB this is. Anybody have any

RE: [JBoss-dev] hsqldb options

2003-03-31 Thread Sacha Labourey
I had a dream! That one day, babelfish will be able to understand AND TRANSLATE Peter songs. Nice try Adrian, but you've abandonned on the last part! ;) like a iteration of min 1k for a deploy/undeploy repeted test for thejbossteam ploy deploy ... resulting in a non mem fatigue - then

RE: [JBoss-dev] hsqldb options

2003-03-31 Thread Sacha Labourey
, Klafuta. Pudding song. -- I know who is Zahid Ramman -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: lundi, 31. mars 2003 17:49 To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] hsqldb options Sorry Peter, no offesne

RE: [JBoss-dev] hsqldb options

2003-03-30 Thread marc fleury
why don't we bring them on then? marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Saturday, March 29, 2003 1:00 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] hsqldb options -Original Message- From

Re: [JBoss-dev] hsqldb options

2003-03-30 Thread Peter Fagerlund
söndagen den 30 mars 2003 kl 20.33 skrev marc fleury: why don't we bring them on then? Send in another X number troops to fix the non result .. Pulezzze what is the non result U are experiencing ... the real or the non-real ... and You say solve it with numbers -hehe ... You are such a

[JBoss-dev] hsqldb options

2003-03-29 Thread David Jencks
Prompted by a customer, I did some experiments with hsqldb options. Currently we specify a tcp port and require a hsqldb mbean to start the hsqldb server. This opens a port and requires explicit hsqldb shutdown. Two other options that appear to work are: specify url jdbc:hsqldb:. and remove

Re: [JBoss-dev] hsqldb options

2003-03-29 Thread Micael
There is no good reason. At 10:55 AM 3/29/03 -0500, you wrote: Prompted by a customer, I did some experiments with hsqldb options. Currently we specify a tcp port and require a hsqldb mbean to start the hsqldb server. This opens a port and requires explicit hsqldb shutdown. Two other options

Re: [JBoss-dev] hsqldb options

2003-03-29 Thread Scott M Stark
Message - From: David Jencks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, March 29, 2003 7:55 AM Subject: [JBoss-dev] hsqldb options Prompted by a customer, I did some experiments with hsqldb options. Currently we specify a tcp port and require a hsqldb mbean to start the hsqldb

RE: [JBoss-dev] hsqldb options

2003-03-29 Thread Bill Burke
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Jencks Sent: Saturday, March 29, 2003 10:55 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] hsqldb options Prompted by a customer, I did some experiments with hsqldb options. Currently we

RE: [JBoss-dev] hsqldb options

2003-03-29 Thread Sacha Labourey
2003 18:45 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] hsqldb options There is no reason why we can't just document both configs and let the user choose what they want. The pure in memory version seems like the better default configuration. Scott Stark

RE: [JBoss-dev] hsqldb options

2003-03-29 Thread Sacha Labourey
is committed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: samedi, 29. mars 2003 19:00 To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] hsqldb options -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL

Re: [JBoss-dev] hsqldb options

2003-03-29 Thread Scott M Stark
it in the configs so its easy to do. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Scott M Stark [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, March 29, 2003 9:44 AM Subject: Re: [JBoss-dev] hsqldb

RE: [JBoss-dev] hsqldb options

2003-03-29 Thread Bill Burke
could get. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sacha Labourey Sent: Saturday, March 29, 2003 1:09 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] hsqldb options Did you take a look at McKoi? http://www.mckoi.com/database/ From

RE: [JBoss-dev] hsqldb options

2003-03-29 Thread Bill Burke
PROTECTED] Subject: RE: [JBoss-dev] hsqldb options Too many writes, to many Optimistic exceptions. TRANSACTION_SERIALIZABLE usually is considered a performance bottleneck in the same way that our QueuedPessismistic Entity bean lock can be a bottleneck as well. I would like to try out ECPERF

Re: [JBoss-dev] hsqldb options

2003-03-29 Thread Peter Fagerlund
lördagen den 29 mars 2003 kl 18.54 skrev Sacha Labourey: Well, for quick prototyping it is nice to use the persistent version which allows to use JBossMQ for example and restart JBoss without loosing persistent messages. Yes when You want to prototype a remote DB for some reason, the legacy