[
https://issues.jboss.org/browse/JBMESSAGING-1037?page=com.atlassian.jira....
]
Prashanto Chatterjee commented on JBMESSAGING-1037:
---------------------------------------------------
I apologize if this question has been answered already. I would like to know what was the
final resolution for this issue. I can see that this issue has been rejected but we are
facing this issue very frequently on the field. We use JBoss 4.2.3 GA with Postgres 9.0.2
and the JBM tables go out of sync very often. We do the suggested workaround on JBoss
restart. However we need a viable solution that does not require manual intervention. Any
thoughts?
JDBCPersistenceManager.java - reference should be inserted after
message (ORA-02291: integrity constraint)
----------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1037
URL:
https://issues.jboss.org/browse/JBMESSAGING-1037
Project: JBoss Messaging
Issue Type: Patch
Components: Messaging Core Persistence
Affects Versions: 1.4.0.CR1
Environment: Windows XP / Oracle 10g
Reporter: Mariusz Olejnik
Assignee: Tim Fox
Priority: Critical
Fix For: 1.4.0.CR1
Attachments: jboss-messaging-trunk-rev2988.patch
Reference should be inserted after message because:
oracle-persistence-service.xml
CREATE TABLE JBM_MSG_REF (
CHANNEL_ID INTEGER,
MESSAGE_ID INTEGER REFERENCES JBM_MSG(MESSAGE_ID)
[...]
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira