[
http://jira.jboss.com/jira/browse/JBAS-3792?page=all ]
Adrian Brock closed JBAS-3792.
------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
JBossAS-4.0.5.SP1
Resolution: Done
I have attached the following FAQ explanation to the error message.
I also include this text when a "delete" fails.
/** FAQ about concurrency problems */
private static String CONCURRENCY_WARNING = "\nCommon reasons for missing messages
are \n1) You have multiple JBossMQs running over the same database.\n2) You are using a
replicating database that is not keeping up with replication.";
Better error reporting when messages "mysteriously" vanish
----------------------------------------------------------
Key: JBAS-3792
URL:
http://jira.jboss.com/jira/browse/JBAS-3792
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.5.GA
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1
It is commonly the case that people try to run two instances of JBossMQ against the same
database tables. This can lead to errors like the ones in the parent task or a similar
message
in the delete when doing acknowledgements.
These error messages need improving and also give a hint to the possible reasons,
e.g.
1) competing JBossMQs trying to share the same database
2) trying to use a replicating database that does not support synchronous replication
(i..e there
is a delay in a row getting written to one database before it appears in the other
database)
The parent issue's error message belongs in org.jboss.mq.pm.jdbc2.PersistenceManager
public SpyMessage loadFromStorage(MessageReference messageRef) throws JMSException
{
...
rs = stmt.executeQuery();
if (rs.next())
return extractMessage(rs);
+ else
throw new JMSException("Unable to load message " + messageRef +
" from storage, are you trying to share database tables between JBossMQ instances?
Are you using a replicating database that does not support synchronous
replication?");
- return null;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira