[openjms-developer] [ openjms-Bugs-816895 ] Exception in purgeMessages

[SourceForge.net]

Bugs item #816895, was opened at 2003-10-03 10:40
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=816895&group_id=54559

Category: persistence
Group: v0.7.6-rc2
Status: Open
Resolution: None
Priority: 5
Submitted By: Tim Anderson (tanderson)
Assigned to: Tim Anderson (tanderson)
Summary: Exception in purgeMessages

Initial Comment:
17:30:10.261 ERROR [EventManager-Worker-2] -
Exception in purgeMessages
org.exolab.jms.persistence.PersistenceException:
com.sap.dbtech.jdbc.translators.ConversionExceptionSap
DB: Cannot convert
data ID:8fb3f464-b833-1004-88ea-39a047ccdc67 to
type BigDecimal.
at
com.sap.dbtech.jdbc.translators.DBTechTranslator.newPa
rseException(DB
TechTranslator.java:1155)
at
com.sap.dbtech.jdbc.translators.StringTranslator.getBigD
ecimal(StringTranslator.java:88)
at
com.sap.dbtech.jdbc.translators.StringTranslator.getLong
(StringTranslator.java:211)
at
com.sap.dbtech.jdbc.ResultSetSapDB.getLong
(ResultSetSapDB.java:1075)
at
org.apache.commons.dbcp.DelegatingResultSet.getLong
(DelegatingResultSet.java:142)
at
org.apache.commons.dbcp.DelegatingResultSet.getLong
(DelegatingResultSet.java:142)
at
org.exolab.jms.persistence.MessageHandles.getMessageI
ds(MessageHandles.java:605)
at
org.exolab.jms.persistence.RDBMSAdapter.purgeMessages
(RDBMSAdapter.java:846)
at
org.exolab.jms.persistence.RDBMSAdapter.handleEvent
(RDBMSAdapter.java:727)
at
org.exolab.jms.events.BasicEventManager$QueueEntry.ru
n(BasicEventManager.java:383)
at
org.exolab.core.threadPool.ThreadPoolWorker.runIt
(ThreadPoolWorker.java:191)
at
org.exolab.core.threadPool.ThreadPoolWorker.runWork
(ThreadPoolWorker.java:178)
at
org.exolab.core.threadPool.ThreadPoolWorker.access$000
(ThreadPoolWorker.java:67)
at
org.exolab.core.threadPool.ThreadPoolWorker$1.run
(ThreadPoolWorker.java:122)
at java.lang.Thread.run(Thread.java:534)



----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)

Date: 2003-10-12 16:38

Message:
Logged In: YES
user_id=557161

This is a bug in the
org.exolab.jms.persistence.MessageHandles.getMessageIds()
method, which hasn't been updated to support the database
schema changes introduced for 0.7.6. This particular method
is only used for database purge support, which isn't
configured by default.
Looking at the code however, the periodic DB purge support
in general is buggy.
Given that:
- existing expired messages are purged at startup;
- messages received that subsequently expire while the
server is running are removed individually; and
- consumed messages are removed as they are consumed

the periodic purge code appears to be redundant.


----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=816895&group_id=54559