From users-return-27453-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Tue May 10 11:22:04 2011 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 E54A1502E for ; Tue, 10 May 2011 11:22:03 +0000 (UTC) Received: (qmail 57732 invoked by uid 500); 10 May 2011 11:22:03 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 57697 invoked by uid 500); 10 May 2011 11:22:03 -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 57689 invoked by uid 99); 10 May 2011 11:22:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 May 2011 11:22:03 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of chagupta@us.ibm.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 May 2011 11:21:57 +0000 Received: from joe.nabble.com ([192.168.236.139]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1QJl0R-0002pM-Pt for users@activemq.apache.org; Tue, 10 May 2011 04:21:35 -0700 Date: Tue, 10 May 2011 04:21:35 -0700 (PDT) From: Chaitanya To: users@activemq.apache.org Message-ID: <1305026495792-3511563.post@n4.nabble.com> Subject: Activemq crashing after few days with journaledJDBC MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org We are using Activemq 5.2 with journaledJDBC using DB2 database. Activemq is crashing after few days of up time. Same test used to work if we don't use persistentAdapter. Snippet from conf files - Error seen in log - Error 1 - 2011-03-25 08:43:26,892 [Q Cleanup Timer] ERROR DefaultDatabaseLocker - Failed to update database lock: com.ibm.db2.jcc.b.gm: [jcc][t4][2030][11211][3.50.152] A communication error occurred during operations on the connection's underlying socket, socket input stream, or socket output stream. Error location: Reply.fill(). Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001 at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.keepAlive(DefaultDatabaseLocker.java:118) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.databaseLockKeepAlive(JDBCPersistenceAdapter.java:481) Error 2- 2011-04-28 10:23:03,293 [ker: 1454462641] INFO FailoverTransport - Successfully connected to tcp://localhost:61616 2011-05-05 12:15:00,671 [Q Cleanup Timer] ERROR DefaultDatabaseLocker - Failed to update database lock: com.ibm.db2.jcc.b.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.50.152 com.ibm.db2.jcc.b.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.50.152 at com.ibm.db2.jcc.b.wc.a(wc.java:55) at com.ibm.db2.jcc.b.wc.a(wc.java:126) at com.ibm.db2.jcc.b.tk.b(tk.java:1593) at com.ibm.db2.jcc.b.tk.c(tk.java:1576) at com.ibm.db2.jcc.t4.db.k(db.java:353) at com.ibm.db2.jcc.t4.db.a(db.java:59) at com.ibm.db2.jcc.t4.t.a(t.java:50) at com.ibm.db2.jcc.t4.tb.b(tb.java:200) at com.ibm.db2.jcc.b.uk.Gb(uk.java:2355) at com.ibm.db2.jcc.b.uk.e(uk.java:2832) at com.ibm.db2.jcc.b.uk.zb(uk.java:568) at com.ibm.db2.jcc.b.uk.executeUpdate(uk.java:551) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:94) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:94) Please let me know how to resolve these issues. Appreciate your help. Thanks, Chaitanya -- View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-crashing-after-few-days-with-journaledJDBC-tp3511563p3511563.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.