You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "ying (JIRA)" <ji...@apache.org> on 2010/04/01 17:05:08 UTC
[jira] Reopened: (AMQ-2681) set findMessageStatement cause problem
for JDBCPersistenceAdapter due to error in Statements.java
[ https://issues.apache.org/activemq/browse/AMQ-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ying reopened AMQ-2681:
-----------------------
AMQ-2681-2-trunk.patch fixes:
removeMessageStatement has a typo missing a "e".
GenerateJDBCStatements.java will generate the default sql statements for jdbc persistence in spring bean format so people can tune the sql so I put in in util
> set findMessageStatement cause problem for JDBCPersistenceAdapter due to error in Statements.java
> -------------------------------------------------------------------------------------------------
>
> Key: AMQ-2681
> URL: https://issues.apache.org/activemq/browse/AMQ-2681
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.1
> Reporter: ying
> Assignee: Dejan Bosanac
> Priority: Blocker
> Fix For: 5.4.0
>
> Attachments: AMQ-2681-2-trunk.patch, AMQ-2681.patch
>
>
> field findMessageByIdStatement in org.apache.activemq.store.jdbc.Statements.java is never used and getFindMessageByIdStatement is using findMessageStatement which causes problem. Because if someone overwrite the default findMessageStatement, it will cause doGetMessageById to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.