[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] strange behavior on JDBC persistent database backend

Michael Atighetchi wrote:

Folks,

I'm using a 2 week old cvs checkout of xmlblaster (before all the
mySQL changes happened), and am seeing the following strange behavior:

My client sends multiple persistent messages with the same OID to a xmlblaster
node. However, the node only seems to put the first message into the table, via

[Jul 3, 2003 11:31:20 AM ESC[37;40mTRACEESC[0m RequestBroker-/node/psq_xxx.xxx.xxx.xxx] Persisting topicEntry
[Jul 3, 2003 11:31:20 AM ESC[34;40mCALL ESC[0m JdbcConnectionPool-jdbc:postgresql://localhost/test] getConnection 0 waiting calls: 1
[Jul 3, 2003 11:31:20 AM ESC[34;40mCALL ESC[0m q_xxx_xxx_xxx_xxx/WeatherImage_1.0] put(WeatherImage_1.0/2003-07-03 1JdbcConnectionPool-jdbc:postgresql://localhost/test] get invoked
[Jul 3, 2003 11:31:20 AM ESC[34;40mCALL ESC[0m JdbcManagerCommonTable-XB_-psq_xxx_xxx_xxx_xxx-topicStore_psq_xxx_xxx_xxx_xxx-addSingleEntry()] Entering
[Jul 3, 2003 11:31:20 AM ESC[37;40mTRACEESC[0m JdbcManagerCommonTable-XB_-psq_xxx_xxx_xxx_xxx-topicStore_psq_xxx_xxx_xxx_xxx-addEntry()] INSERT INTO XB_ENTRIES VALUES ( ?, ?, ?, ?, ?, ?, ?, ?)
[Jul 3, 2003 11:31:20 AM ESC[37;40mTRACEESC[0m JdbcManagerCommonTable-XB_-psq_xxx_xxx_xxx_xxx-topicStore_psq_xxx_xxx_xxx_xxx-addEntry()] INSERT INTO XB_ENTRIES VALUES ( ....


All following next messages, however, I don't see any of the JDBC traces. All
I see is

[Jul 3, 2003 11:31:44 AM ESC[34;40mCALL ESC[0m org.xmlBlaster.engine.msgstore.cache.PersistenceCachePlugin-msgUnitStore:psq_xxx_xxx_xxx_xxx/WeatherImage_1.0] put(WeatherImage_1.0/2003-07-03 11:31:44.425000001)
[Jul 3, 2003 11:31:44 AM ESC[34;40mCALL ESC[0m MapPlugin-msgUnitStore:ps1:31:44.425000001)


Any clues ?

Hi Michael,

i have tried this:

  java org.xmlBlaster.Main -trace[jdbc] true

 java javaclients.HelloWorldPublish -persistent true -numPublish 10

After hitting enter first time the topic 'Hello' is created and the msgUnit is stored
and the history entry is stored,
hitting enter again the new msgUnit is added to 'msgUnitStore' and 'history'.

So everything looks OK here,

regards

Marcel