Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 54911E0A7 for ; Tue, 12 Feb 2013 10:20:58 +0000 (UTC) Received: (qmail 62316 invoked by uid 500); 12 Feb 2013 10:20:57 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 62134 invoked by uid 500); 12 Feb 2013 10:20:57 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 62077 invoked by uid 99); 12 Feb 2013 10:20:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 10:20:55 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 10:20:48 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U5CyQ-0001MY-M5 for users@activemq.apache.org; Tue, 12 Feb 2013 02:20:26 -0800 Date: Tue, 12 Feb 2013 02:20:26 -0800 (PST) From: jliezers To: users@activemq.apache.org Message-ID: <1360664426648-4663232.post@n4.nabble.com> Subject: Successfully delivered message ends up on DLQ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm running ActiveMQ version 5.6.0 on linux. Very occasionaly a message ends up on a DLQ even though consumer logs give every indication that the message has been successfully delivered and processed. The consumer Spring jms listener acknowledge attribute is set to "client" I can't find any errors or warnings logged that relate directly to these DLQ events but I have found a few JDBC warnings in the log. Here's an example. WARN o.a.a.s.jdbc.JDBCPersistenceAdapter - JDBC Failure: Io exception: Connection reset java.sql.SQLRecoverableException: Io exception: Connection reset at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBCDriver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBCDriver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:521) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBCDriver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:969) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:897) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3431) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491) ~[ojdbc6-11.1.0.7.0-Production.jar:Oracle JDBC Driver version - "11.1.0.7.0-Production"] at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) ~[commons-dbcp-1.4.jar:1.4] at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) ~[commons-dbcp-1.4.jar:1.4] at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) ~[commons-dbcp-1.4.jar:1.4] at org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.getStoreSequenceId(DefaultJDBCAdapter.java:278) ~[activemq-core-5.6.0.jar:5.6.0] at org.apache.activemq.store.jdbc.JDBCMessageStore.getStoreSequenceIdForMessageId(JDBCMessageStore.java:335) [activemq-core-5.6.0.jar:5.6.0] at org.apache.activemq.store.jdbc.JDBCMessageStore.removeMessage(JDBCMessageStore.java:190) [activemq-core-5.6.0.jar:5.6.0] Could a JDBC exception be forcing a message onto the DLQ after delivery has been acknowledged? Thanks, John -- View this message in context: http://activemq.2283324.n4.nabble.com/Successfully-delivered-message-ends-up-on-DLQ-tp4663232.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.