The JDBC2 PM configuration in jbossmq-service.xml is generic, not postgres-specific. So yes, it will fail if you start JBoss with the default settings.
Anyway, you have to change the DataSource of the JBossMQ Persistence manager. If you change it for a Postgres DB, then just change object into BYTEA
If you have a working configuration, please post it.
I will include it in docs folder of the jboss distribution.
Attached two XML files. One for postgres (7.3) and one for mySQL 4
here's my xml config for JBoss 3.2.2RC2.
I notice that I have not set the BLOB_TYPE from
OBJECT_BLOB to BYTES_BLOB as "Dark_Lord" has -- I
assume this would be the more elegant solution?
I just changed the type of MESSAGEBLOB from OBJECT
Adrian, by the way, why is the MessageCache configured to
be so huge? 500 MB HighMemoryMark and 600 MB MaxMemoryMark
If it's left at these default values JMS behaves like having
a memory leak... Whould it be possible/useful to change these
defaults to a more conservative scale?