activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ying (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2681) set findMessageStatement cause problem for JDBCPersistenceAdapter due to error in Statements.java
Date Wed, 31 Mar 2010 15:35:08 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ying updated AMQ-2681:
----------------------

    Attachment: AMQ-2681.patch

AMQ-2681.patch fix the problem and make find findMessageByIdStatement settable

> 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
>            Priority: Blocker
>         Attachments: 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.


Mime
View raw message