activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chaitanya <chagu...@us.ibm.com>
Subject Activemq crashing after few days with journaledJDBC
Date Tue, 10 May 2011 11:19:35 GMT
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 -

 <journaledJDBC journalLogFiles="5"
dataDirectory="${activemq.base}/activemq-data" dataSource="#db2-ds"
lockKeepAlivePeriod="0"/>

<bean id="db2-ds" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName" value="com.ibm.db2.jcc.DB2Driver"/>
<property name="url" value="jdbc:db2://bssdb.mydb.com:50000/AMQDB1"/>
<property name="username" value="db2admin"/>
<property name="password" value="admin"/>
<property name="poolPreparedStatements" value="true"/>
</bean>

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-tp3511562p3511562.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Mime
View raw message