History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: AMQ-716
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Rob Davies
Reporter: klaus terjung
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
ActiveMQ

message is read from queue but not removed

Created: 19/May/06 12:01 PM   Updated: 14/Jun/06 06:45 AM
Component/s: Message Store
Affects Version/s: 4.0
Fix Version/s: 4.0.1

Time Tracking:
Not Specified

Environment:
ActiveMQ Release (08.05.2006)
BM Blade JS20 AIX 5.3
DB2 DataBase 8.2
Driver 2.5.33

Configuration:

<jdbcPersistenceAdapter class="org.activemq.store.jdbc.adapter.DefaultJDBCAdapter" dataSource= "#db2-ds"/>

<bean id="db2datasource" class="org.apache.commons.dbcp.BasicDataSource">
    <property name="driverClassName" value="com.ibm.db2.jcc.DB2Driver"/>
    <property name="url" value="URL"/>
    <property name="username" value="USER"/>
    <property name="password" value="PASS"/>
  </bean>


 Description  « Hide
Producer send a message with a non transacted Session

Testing a Consumer with a non transacted Session to receive Messages
the Message is read but not removed.

Testing a Consumer with a transacted Session and commit
the Message is read and not removed.



 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
klaus terjung - 19/May/06 12:11 PM
Bug in Description

Testing a Consumer with a transacted Session and commit
the Message is read and removed !!


klaus terjung - 02/Jun/06 07:15 AM
bug with javax.jms.Session.AUTO_ACKNOWLEDGE in ActiveMQ ?

When I use createQueueSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE)
the Messages are not removed from the Queue.

When I use createQueueSession(true, javax.jms.Session.AUTO_ACKNOWLEDGE) and
call getSession().commit() in the onMessage Method

the Messages are removed from the Queue.


Rob Davies - 12/Jun/06 10:11 AM
optimizeAcknowledge now off by default

James Strachan - 14/Jun/06 06:45 AM
Note that a workaround is to disable optimizeAcknowledge - e.g.

tcp://localhost:61616?jms.optimizeAcknowledge=false