JBoss 3.2 uses wrong BLOB type for Postgres

[raphael]

Hi,

it seems that JBoss 3.2 tries to create the JMS persistence
tables using the BLOB type "OBJECT" in jbossmq-service.xml.

This leads to a postgres error on startup:

DEBUG: query: CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB OBJECT, PRIMARY KEY (MESSAGEID, DESTINATION) )
ERROR: Unable to locate type name 'object' in catalog

When I changed this to "BYTEA" in jbossmq-service.xml
(as I learned from another posting in this forum) it worked.

Is this a known bug or do I have to change something in
my config to make postgres work without patching?

Thanks!
Cheers
Raphael

[stephanenicoll]

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

[adrian.brock]

If you have a working configuration, please post it.
I will include it in docs folder of the jboss distribution.

Regards,
Adrian

[stephanenicoll]

Attached two XML files. One for postgres (7.3) and one for mySQL 4

[raphael]

Hi Adrian,

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
to BYTEA.

Cheers
Raphael


PS:

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?

Cheers
Raphael

[raphael]

"raphael" wrote:
attachement