[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xmlblaster] JdbcQueuePlugin won't load
Jdbc Support for the queues is currently only tested with ORACLE and
POSTGRES. MySQL has not been tested and I believe MySQL has no support
for transactions either.
I am currently working on an alternate plugin which only uses three
tables (JdbcQueueCommonTable plugin) which has already been tested with
postgres. I will make a last test with ORACLE today. You can find
documentation on how to use it on
The reason why you did'nt get anything on your db and did not get any
logs either is probably that you did'nt switch persitence on in your
Make sure that the following lines are uncommented:
Then, since nobody has tested it yet, you should provide the specific
settings for MYSQL which will be something like this:
Where all the xxx are specific to MySQL. Note that x1 is the name given
back by the metadata of the DB (mysql or MYSQL or something like that).
The other parameters are the name used by mysql to handle their java
- string (choose a type which is sufficiently long for your needs)
- boolean (must be handled as a single character for oracle)
- tables it the name of the table containing all tables on the db
- tablename the name of the attribute (column) of the table containing
all tables, specifying the name of the tables.
I hope it will work. Please let me know.
The JdbcQueueCommonTablePlugin has less transaction dependent code, so
it will probably be more like to work with mySql.
Please let us know about the results
Michael Atighetchi wrote:
I have a xmlblaster scenario with 2 clients that communicate with
eatch other via talking to a xmlblaster slave instance (which in turn
talks to a master).
I'd like to change the master so that it stores messages in a mysql
database instead of keeping them in RAM. First, I changed the qos key
on publishing messages to "<qos> <persistent /> </qos>". I also added the
following line to the xmlblaster.properties file of the master:
NOTE: assume reasonable entries for <...>
Upon starting up the master node, I see that the JdbcDriver
[Feb 25, 2003 6:31:08 PM [32;40mINFO [0m JdbcDriver-/node/psq1] Started successfully JDBC driver with loginName=__sys__jdbc
However, I don't see any printout for the JdbcQueuePlugin, but lots of
printout for RamQueuePlugin.
Upon starting up the clients, messages are still kept in RAM in the
master, and not put into the mysql database.
How can I change the configuration to use jdbc for storing messages ?
mailto:laghi at swissinfo.org
tel. +46 8 7492952 / mob. +46 70 4103964