You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by sparky2708 <da...@columbia.edu> on 2007/10/30 22:32:38 UTC
All kinds of errors while running the ActiveMQ Broker. Please help!
I am getting all kinds of errors when I run the broker. And then the broker
stops responding. Does anyone have any suggestions:
[teprod@amqdev /tmp]$ more activemq_master.log
ACTIVEMQ_HOME: /usr/local/activemq
Loading message broker from: xbean:file:activemq_master.xml
INFO BrokerService - ActiveMQ 4.1.0-incubator JMS Message
Broker (master) is starting
INFO BrokerService - For help or more information please
see: http://incubator.apache.org/activemq/
INFO ManagementContext - JMX consoles can connect to
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO JDBCPersistenceAdapter - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
INFO DefaultDatabaseLocker - Attempting to acquire the exclusive
lock to become the Master brokerINFO DefaultDatabaseLocker -
Becoming the master on dataSource:
org.apache.derby.jdbc.EmbeddedDataSource@b8176d
INFO JournalPersistenceAdapter - Journal Recovery Started from: Active
Journal: using 5 x 20.0 Megs at: /tmp/activemq-data/MASTER/journal
INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
transactions recovered.
INFO TransportServerThreadSupport - Listening for connections at:
tcp://amqdev:61616
INFO TransportConnector - Connector openwire Started
INFO TransportServerThreadSupport - Listening for connections at:
ssl://amqdev:61617
INFO TransportConnector - Connector ssl Started
INFO TransportServerThreadSupport - Listening for connections at:
stomp://amqdev:61613
INFO TransportConnector - Connector stomp Started
INFO BrokerService - ActiveMQ JMS Message Broker (master,
ID:amqdev-51402-1193750950190-1:0) started
ERROR TransportConnector - Could not accept connection from
/10.0.1.8:49212: java.net.SocketException: Socket closed
java.net.SocketException: Socket closed
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:109)
at java.io.DataOutputStream.flush(DataOutputStream.java:106)
at
org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:119)
at
org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:141)
at
org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormatNegotiator.java:155)
at
org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:73)
at
org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:54)
at
org.apache.activemq.broker.TransportConnection.start(TransportConnection.java:816)
at
org.apache.activemq.broker.TransportConnector$1.onAccept(TransportConnector.java:148)
at
org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer.java:167)
at java.lang.Thread.run(Thread.java:595)
ERROR JournalPersistenceAdapter - Failed to checkpoint a message store:
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.io.IOException: Not started.
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.io.IOException: Not started.
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:386)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
Caused by: java.io.IOException: Not started.
at
org.apache.activemq.store.jdbc.TransactionContext.rollback(TransactionContext.java:168)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.rollbackTransaction(JDBCPersistenceAdapter.java:368)
at org.apache.aERROR JournalPersistenceAdapter - Failed to
checkpoint a message store:
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.io.IOException: An SQL data change is not
permitted for a read-only connection, user or database.
edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
java.io.IOException: An SQL data change
is not permitted for a read-only connection, user or database.
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:386)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
Caused by: java.io.IOException: An SQL data change is not permitted for a
read-only connection, user or database.
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:43)
at
org.apache.activemq.store.jdbc.TransactionContext.commit(TransactionContext.java:159)
at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.commitTransaction(JDBCPersistenceAdapter.java:363)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter.commitTransaction(JournalPersistenceAdapter.java:193)
at
org.apache.activemq.util.TransactionTemplate.run(TransactionTemplate.java:59)
at
org.apache.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:247)
at
org.apache.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:221)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter$4.call(JournalPersistenceAdapter.java:356)
at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.sql.BatchUpdateException: An SQL data change is not
permitted for a read-only connection, user or database.
at org.apache.derby.impl.jdbc.EmbedStatement.executeBatch(Unknown
Source)
at
org.apache.activemq.store.jdbc.TransactionContext.executeBatch(TransactionContext.java:96)
at
org.apache.activemq.store.jdbc.TransactionContext.executeBatch(TransactionContext.java:79)
at
org.apache.activemq.store.jdbc.TransactionContext.commit(TransactionContext.java:154)
... 10 more
ERROR JournalPersistenceAdapter - Failed to mark the Journal:
org.apache.activeio.journal.InvalidRecordLocationException: The location is
less than the last mark.
org.apache.activeio.journal.InvalidRecordLocationException: The location is
less than the last mark.
at
org.apache.activeio.journal.active.JournalImpl.setMark(JournalImpl.java:340)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:403)
at
org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
SQL Exception: An SQL data change is not permitted for a read-only
connection, user or database.
--
View this message in context: http://www.nabble.com/All-kinds-of-errors-while-running-the-ActiveMQ-Broker.-Please-help%21-tf4721228s2354.html#a13497614
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: All kinds of errors while running the ActiveMQ Broker. Please
help!
Posted by Nicky Sandhu <ka...@gmail.com>.
You probably have permission problems with the user running the broker and
the directory being used by it
sparky2708 wrote:
>
> I am getting all kinds of errors when I run the broker. And then the
> broker stops responding. Does anyone have any suggestions:
>
> [teprod@amqdev /tmp]$ more activemq_master.log
> ACTIVEMQ_HOME: /usr/local/activemq
> Loading message broker from: xbean:file:activemq_master.xml
> INFO BrokerService - ActiveMQ 4.1.0-incubator JMS
> Message Broker (master) is starting
> INFO BrokerService - For help or more information please
> see: http://incubator.apache.org/activemq/
> INFO ManagementContext - JMX consoles can connect to
> service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> INFO JDBCPersistenceAdapter - Database driver recognized:
> [apache_derby_embedded_jdbc_driver]
> INFO DefaultDatabaseLocker - Attempting to acquire the exclusive
> lock to become the Master brokerINFO DefaultDatabaseLocker -
> Becoming the master on dataSource:
> org.apache.derby.jdbc.EmbeddedDataSource@b8176d
> INFO JournalPersistenceAdapter - Journal Recovery Started from:
> Active Journal: using 5 x 20.0 Megs at: /tmp/activemq-data/MASTER/journal
> INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in
> transactions recovered.
> INFO TransportServerThreadSupport - Listening for connections at:
> tcp://amqdev:61616
> INFO TransportConnector - Connector openwire Started
> INFO TransportServerThreadSupport - Listening for connections at:
> ssl://amqdev:61617
> INFO TransportConnector - Connector ssl Started
> INFO TransportServerThreadSupport - Listening for connections at:
> stomp://amqdev:61613
> INFO TransportConnector - Connector stomp Started
> INFO BrokerService - ActiveMQ JMS Message Broker
> (master, ID:amqdev-51402-1193750950190-1:0) started
> ERROR TransportConnector - Could not accept connection from
> /10.0.1.8:49212: java.net.SocketException: Socket closed
> java.net.SocketException: Socket closed
> at
> java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:99)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at
> org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBufferedOutputStream.java:109)
> at java.io.DataOutputStream.flush(DataOutputStream.java:106)
> at
> org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:119)
> at
> org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:141)
> at
> org.apache.activemq.transport.WireFormatNegotiator.sendWireFormat(WireFormatNegotiator.java:155)
> at
> org.apache.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:73)
> at
> org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:54)
> at
> org.apache.activemq.broker.TransportConnection.start(TransportConnection.java:816)
> at
> org.apache.activemq.broker.TransportConnector$1.onAccept(TransportConnector.java:148)
> at
> org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer.java:167)
> at java.lang.Thread.run(Thread.java:595)
> ERROR JournalPersistenceAdapter - Failed to checkpoint a message
> store: edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
> java.io.IOException: Not started.
> edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
> java.io.IOException: Not started.
> at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
> at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:386)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
> at
> org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
> Caused by: java.io.IOException: Not started.
> at
> org.apache.activemq.store.jdbc.TransactionContext.rollback(TransactionContext.java:168)
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.rollbackTransaction(JDBCPersistenceAdapter.java:368)
> at org.apache.aERROR JournalPersistenceAdapter - Failed to
> checkpoint a message store:
> edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
> java.io.IOException: An SQL data change is not
> permitted for a read-only connection, user or database.
> edu.emory.mathcs.backport.java.util.concurrent.ExecutionException:
> java.io.IOException: An SQL data change
> is not permitted for a read-only connection, user or database.
> at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.getResult(FutureTask.java:299)
> at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.get(FutureTask.java:118)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:386)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
> at
> org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
> Caused by: java.io.IOException: An SQL data change is not permitted for a
> read-only connection, user or database.
> at
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:43)
> at
> org.apache.activemq.store.jdbc.TransactionContext.commit(TransactionContext.java:159)
> at
> org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.commitTransaction(JDBCPersistenceAdapter.java:363)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter.commitTransaction(JournalPersistenceAdapter.java:193)
> at
> org.apache.activemq.util.TransactionTemplate.run(TransactionTemplate.java:59)
> at
> org.apache.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:247)
> at
> org.apache.activemq.store.journal.JournalMessageStore.checkpoint(JournalMessageStore.java:221)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter$4.call(JournalPersistenceAdapter.java:356)
> at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: java.sql.BatchUpdateException: An SQL data change is not
> permitted for a read-only connection, user or database.
> at org.apache.derby.impl.jdbc.EmbedStatement.executeBatch(Unknown
> Source)
> at
> org.apache.activemq.store.jdbc.TransactionContext.executeBatch(TransactionContext.java:96)
> at
> org.apache.activemq.store.jdbc.TransactionContext.executeBatch(TransactionContext.java:79)
> at
> org.apache.activemq.store.jdbc.TransactionContext.commit(TransactionContext.java:154)
> ... 10 more
> ERROR JournalPersistenceAdapter - Failed to mark the Journal:
> org.apache.activeio.journal.InvalidRecordLocationException: The location
> is less than the last mark.
> org.apache.activeio.journal.InvalidRecordLocationException: The location
> is less than the last mark.
> at
> org.apache.activeio.journal.active.JournalImpl.setMark(JournalImpl.java:340)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter.doCheckpoint(JournalPersistenceAdapter.java:403)
> at
> org.apache.activemq.store.journal.JournalPersistenceAdapter$2.iterate(JournalPersistenceAdapter.java:129)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
> at
> org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
> WARN JDBCPersistenceAdapter - Old message cleanup failed due to:
> SQL Exception: An SQL data change is not permitted for a read-only
> connection, user or database.
>
>
--
View this message in context: http://www.nabble.com/All-kinds-of-errors-while-running-the-ActiveMQ-Broker.-Please-help%21-tf4721228s2354.html#a13502148
Sent from the ActiveMQ - User mailing list archive at Nabble.com.