You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by pollotek <cl...@gmail.com> on 2012/06/09 02:38:04 UTC
Suspicious ActiveMQSession messages in my log
I am running ActiveMQ 5.6 on Java 6 on Ubuntu 11.10 inside Tomcat 6. I have a
Master-Slave shared file system setup with Kaha DB and Spring 3.0.6. I just
restarted my Tomcat server and I just started seeing TONS of messages
similar to the following ones:
00:15:28,566 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:3
Transaction Commit :null
00:15:28,567 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:15
Transaction Commit :null
00:15:29,084 DEBUG AbstractInactivityMonitor:80 - 30000 ms elapsed since
last read check.
00:15:29,090 DEBUG AbstractInactivityMonitor:107 -
org.apache.activemq.transport.AbstractInactivityMonitor$2@75148588 10000 ms
elapsed since last write check.
00:15:29,345 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:4
Transaction Commit :null
00:15:29,527 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:9
Transaction Commit :null
00:15:29,565 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:1
Transaction Commit :null
00:15:29,566 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:6
Transaction Commit :null
00:15:29,566 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:12
Transaction Commit :null
00:15:29,566 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:8
Transaction Commit :null
00:15:29,566 DEBUG ActiveMQSession:559 - ID:mc03-47361-1339199838898-1:1:13
Transaction Commit :null
My Spring configuration looks like this:
<amq:connectionFactory
id="jmsFactory"
brokerURL="failover:(broker1, broker2)" />
<bean id="jmsConsumerConnectionFactory"
class="org.springframework.jms.connection.SingleConnectionFactory"
p:targetConnectionFactory-ref="jmsFactory" />
<jms:listener-container container-type="default"
connection-factory="jmsConsumerConnectionFactory"
acknowledge="transacted"
concurrency="10-10">
<jms:listener destination="my.queue.destination"
ref="myJmsMessageListener" />
</jms:listener-container>
Any ideas what could be happening?
--
View this message in context: http://activemq.2283324.n4.nabble.com/Suspicious-ActiveMQSession-messages-in-my-log-tp4653127.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Suspicious ActiveMQSession messages in my log
Posted by pollotek <cl...@gmail.com>.
I think the obvious question would be:
- Why would my client be trying to commit messages if I'm not generating
new ones and why don't they have an id?
- If these messages don't get committed nor rolled back, how do I make them
go away?
Looks to me like there are some transactions in a strange state that are
not started but can't be committed either.
On Mon, Jun 11, 2012 at 12:23 AM, mickhayes [via ActiveMQ] <
ml-node+s2283324n4653150h6@n4.nabble.com> wrote:
> It means you are at the bolded part below of ActiveMQSession.java and have
> DEBUG level logging on and
> transactionContext.getTransactionId() is null:
>
> /**
> * Commits all messages done in this transaction and releases any
> locks
> * currently held.
> *
> * @throws JMSException if the JMS provider fails to commit the
> transaction
> * due to some internal error.
> * @throws TransactionRolledBackException if the transaction is rolled
> back
> * due to some internal error during commit.
> * @throws javax.jms.IllegalStateException if the method is not called
> by a
> * transacted session.
> */
> public void commit() throws JMSException {
> checkClosed();
> if (!getTransacted()) {
> throw new javax.jms.IllegalStateException("Not a transacted
> session");
> }
> * if (LOG.isDebugEnabled()) {
> LOG.debug(getSessionId() + " Transaction Commit :" +
> transactionContext.getTransactionId());*
> }
> transactionContext.commit();
> }
>
> Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://activemq.2283324.n4.nabble.com/Suspicious-ActiveMQSession-messages-in-my-log-tp4653127p4653150.html
> To unsubscribe from Suspicious ActiveMQSession messages in my log, click
> here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4653127&code=Y2xhdWRpby5zYW50YW5hQGdtYWlsLmNvbXw0NjUzMTI3fC0xNTA0MDM5ODky>
> .
> NAML<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://activemq.2283324.n4.nabble.com/Suspicious-ActiveMQSession-messages-in-my-log-tp4653127p4653180.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Suspicious ActiveMQSession messages in my log
Posted by mickhayes <mi...@gmail.com>.
It means you are at the bolded part below of ActiveMQSession.java and have
DEBUG level logging on and
transactionContext.getTransactionId() is null:
/**
* Commits all messages done in this transaction and releases any locks
* currently held.
*
* @throws JMSException if the JMS provider fails to commit the
transaction
* due to some internal error.
* @throws TransactionRolledBackException if the transaction is rolled
back
* due to some internal error during commit.
* @throws javax.jms.IllegalStateException if the method is not called
by a
* transacted session.
*/
public void commit() throws JMSException {
checkClosed();
if (!getTransacted()) {
throw new javax.jms.IllegalStateException("Not a transacted
session");
}
* if (LOG.isDebugEnabled()) {
LOG.debug(getSessionId() + " Transaction Commit :" +
transactionContext.getTransactionId());*
}
transactionContext.commit();
}
-----
Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA
--
View this message in context: http://activemq.2283324.n4.nabble.com/Suspicious-ActiveMQSession-messages-in-my-log-tp4653127p4653150.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.