Ok, I don't kown if that's a JBoss bug but here's what I did to
solve it:

1'st time I start JBoss I let it create the two JMS tables.
Then I dump the database.
Then I reconfiugre JBoss to NOT create the tables on startup.

When setting up new JBoss instances I use the dump to create
the tables and configure them to NOT create the tables on startup.

May be this whole thing is only behaving bad together with
postgres (because postgres will abort the whole transaction
if it fails to create the already existing tables and thus fails
to recover the old messages).

Regards,
Raphael

Hi Adrian,

I've put together a zip file with:
[AppServer-xc333][all-all]raphael@rigel:~/AppServer/xc333 $ jar tfv JBoss.jar
JBossTomcat/VERSION.txt
JBossTomcat/server/default/log/
JBossTomcat/server/default/log/stdout.log
JBossTomcat/server/default/log/boot.log
JBossTomcat/server/default/log/server.log
JBossTomcat/server/default/log/localhost_access2003-08-14.log
JBossTomcat/server/default/deploy/jms/jbossmq-service.xml
JBossTomcat/server/default/deploy/postgres-ds.xml
JBossTomcat/server/default/conf/standardjbosscmp-jdbc.xml
JBossTomcat/server/default/conf/standardjaws.xml
JBossTomcat/server/default/conf/jboss-service.xml
JBossTomcat/server/default/deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml
JBossTomcat/server/default/conf/log4j.xml
JBossTomcat/server/default/conf/standardjboss.xml


Here's what I did:
1. create new copy of JBoss (named xc333)
2. create postgres database (named xc333)
without the two jms tables.
3. configure JBoss to use this postgres database
4. START 1'st TIME
5. banner neustart >> {logfiles}
6. START 2'nd TIME

Please let me know if you need more files from this test JBoss instance.


Cheers
Raphael

here's the postgres log as well...

Cheers
Raphael

Now I tried sending the first message over JMS with
database persistence on postgres...

It seems that it's not enough to create the database and
the two JMS tables:


It failed with the following exception in JBoss (starting
with the creation of a temporary queue for the client):

[Thu Aug 14 17:14:39.837 CEST 2003] [WARN ] [org.jboss.mq.security.SecurityManager] No SecurityMetadadata was available for JMS_TQ3 adding default security conf
[Thu Aug 14 17:14:42.064 CEST 2003] [WARN ] [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception:
org.jboss.mq.SpyJMSException: Could not store message: 2 msg=2 hard NOT_STORED PERSISTENT queue=QUEUE.MessageProcessor priority=4 hashCode=33372731; - nested throwable: (The table for org.jboss.mq.SpyObjectMessage is not in the database. Contact the DBA, as the database is in an inconsistent state.)
at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:705)
at org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:39)
at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:133)
at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:405)
at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:385)
at org.jboss.mq.server.JMSServerInterceptorSupport.addMessage(JMSServerInterceptorSupport.java:135)
at org.jboss.mq.security.ServerSecurityInterceptor.addMessage(ServerSecurityInterceptor.java:162)
at org.jboss.mq.server.TracingInterceptor.addMessage(TracingInterceptor.java:234)
at org.jboss.mq.server.JMSServerInvoker.addMessage(JMSServerInvoker.java:137)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:248)
at java.lang.Thread.run(Thread.java:536)
Caused by: The table for org.jboss.mq.SpyObjectMessage is not in the database. Contact the DBA, as the database is in an inconsistent state.
at org.postgresql.Connection.storeObject(Unknown Source)
at org.postgresql.jdbc2.PreparedStatement.setObject(Unknown Source)
at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:625)
at org.jboss.mq.pm.jdbc2.PersistenceManager.setBlob(PersistenceManager.java:798)
at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:735)
at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:690)
... 10 more


Here's what Postgres gives me in it's log:

DEBUG: StartTransactionCommand
DEBUG: query: begin;
DEBUG: ProcessUtility: begin;
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: select typname from pg_type,pg_class where typname=relname and typname='org_jboss_mq_spyobjectmessage'
DEBUG: ProcessQuery
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: rollback; begin;
DEBUG: ProcessUtility: rollback; begin;
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: ProcessUtility: rollback; begin;
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: end
DEBUG: ProcessUtility: end
DEBUG: CommitTransactionCommand
DEBUG: StartTransactionCommand
DEBUG: query: show xactisolevel
DEBUG: ProcessUtility: show xactisolevel
NOTICE: TRANSACTION ISOLATION LEVEL is READ COMMITTED
DEBUG: CommitTransactionCommand



Regards,
Raphael