]
Roland Schenner commented on JBAS-2503:
---------------------------------------
There is a typo in the above config example, should be:
<mbean code="org.jboss.mq.pm.jdbc2.OracleThinPersistenceManager"
name="jboss.mq:service=PersistenceManager">
JBossMQ JDBC2 Blob workaround for Oracle 4k limit
-------------------------------------------------
Key: JBAS-2503
URL:
https://jira.jboss.org/jira/browse/JBAS-2503
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMS (JBossMQ)
Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.3 SP1
Reporter: Adrian Brock
Assignee: Ryan Campbell
Priority: Optional
Fix For: JBossAS-3.2.8 Final, JBossAS-4.0.4.CR2, JBossAS-5.0.0.Beta1
Allow override of the blob processing and create a subclass of JBossMQ's JDBC2
persistence manager
such that it can workaround the 4k limit of the thin driver.
Effectively we translate:
INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, TXID, TXOP, MESSAGEBLOB) VALUES
(?,?,?,?,?)
into
INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, TXID, TXOP, MESSAGEBLOB) VALUES
(?,?,?,?, EMPTY_BLOB())
SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID = ? FOR UPDATE
UPDATE JMS_MESSAGES SET MESSAGEBLOB = ? WHERE MESSAGEID = ?
If we knew how to generically retrieve the primary key column and key values from the
insert
we could do this as a plugin to the JDBC resource adapter.
But parsing SQL is not really an option.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: