Hello once again,
Adrian Brock wrote:
On Thu, 2003-10-02 at 16:00, Stefan Puiu wrote:
My previous mail seems to be Lost in Sourceforge, I provided the same
link.
Actually I wrote and sent my message before your first reply got to my
inbox (let's call it the Sourceforge delay :) ), now I have
On Thursday, Oct 2, 2003, at 17:29 Europe/Stockholm, Adrian Brock wrote:
17:52:18,059 INFO [MainDeployer] Starting deployment of package:
file:/home/fane/builds/jboss-3.2.1/server/default/deploy/jms/jbossmq-
service.xml
JBossMQ uses HSQLDB as default. If You are not using the mq service
Hello list,
I'm having trouble restarting JBoss (I'm using JBoss 3.2.1) after
running some messaging tests that fail, the PersistenceManager throws an
exception which gets thrown in the resolveAllUncomittedTXs method in
org.jboss.mq.pm.jdbc2.PersistenceManager, as you can see in the stack
There is a fundamental problem with the hsql mbean.
When it starts, it creates a new thread to start the db.
JBoss continues on to other services.
If the thread takes too long to bind the sockets,
you get Connection refused.
Somebody hacked jdbc2 so you can do retries
(default 5 times waiting 1.5
Hello Adrian and thanks for the reply,
I'm using the PersistenceManager MBean configured out of the box to use
HypersonicSQL by default, would defining a different datasource using,
say, MySQL (let newDS be its name) and changing the PersistenceManager
configuration to use that one solve the
With an external db, you won't see the same problem.
The db is either started or it isn't.
There are examples configurations coming with jboss-3.2.2
in docs/examples/jms for other dbs
(I welcome contributions for other dbs not included).
The sql properties should work with 3.2.x and 3.0.7+
Hello again,
I've finally managed to make the PersistenceManager to work with MySQL,
using the mysql-jdbc2.xml from this link which I've found searching the
mailing list:
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/etc/server/examples/deploy/
There is an error in the
On Thu, 2003-10-02 at 16:00, Stefan Puiu wrote:
Hello again,
I've finally managed to make the PersistenceManager to work with MySQL,
using the mysql-jdbc2.xml from this link which I've found searching the
mailing list:
