You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "arpit shah (JIRA)" <ji...@apache.org> on 2007/10/26 16:52:23 UTC
[jira] Created: (AMQ-1478) Can't produce messages after consumer
goes down.
Can't produce messages after consumer goes down.
------------------------------------------------
Key: AMQ-1478
URL: https://issues.apache.org/activemq/browse/AMQ-1478
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 4.1.1
Environment: Producer box( Windows - running a broker - Producer configuration: persistent messages)
Consumer box(Linux - with durable topics for persistence)
Reporter: arpit shah
Attachments: activemq.xml
Configuration is attached below.
Behavior:
Set the persistent to be true in the broker configuration and created a durable topic to consume messages.
Everything was fine until the consumer went down. During that time producer keeps producing messages. Restart consumer to catch all the missed messages but didn't catch them. After that the whole application hangs. can't produce any more messages, hence can't consume them. The heap usage size keeps increasing on the producer side.
Increased memory size, which didn't work either. The received log is shown below on the broker side when it comes up and the message that shows up on the produce client window.
Here is the message from the producer window:
response from futureResponse was invalid
FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
E: 146
FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
E: 153
FILE: ..\src\main\activemq\connector\openwire\OpenWireFormatNegotiator.c
pp, LINE: 105
FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
E: 1454
FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
E: 924
FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 675
FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 194
FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 149
FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 108
Here is broker log:
2007-10-25 15:56:32,576 [main ] INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker (localhost) is starting
2007-10-25 15:56:32,576 [main ] INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/
2007-10-25 15:56:32,654 [JMX connector ] INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
2007-10-25 15:56:33,154 [main ] INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver]
2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker
2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: org.apache.derby.jdbc.EmbeddedDataSource@8a2023
2007-10-25 15:56:34,748 [main ] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: C:\ActiveMQ\apache-activemq-4.1.1\apache-activemq-4.1.1\activemq-data\journal
2007-10-25 15:56:34,764 [main ] INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered.
2007-10-25 15:56:34,967 [main ] INFO TransportServerThreadSupport - Listening for connections at: tcp://PCSHAH:61616
2007-10-25 15:56:34,967 [main ] INFO TransportConnector - Connector openwire Started
2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: ssl://PCSHAH:61617
2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector ssl Started
2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: stomp://PCSHAH:61613
2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector stomp Started
2007-10-25 15:56:35,358 [main ] INFO NetworkConnector - Network Connector default-nc Started
2007-10-25 15:56:35,358 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:PCSHAH-2327-1193342192311-1:0) started
2007-10-25 15:56:51,421 [85.37.184:44137] INFO KahaStore - Kaha Store deleted data directory activemq-data\localhost\tmp_storage
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1478) Can't produce messages after consumer
goes down.
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1478:
-------------------------------
Assignee: Rob Davies
> Can't produce messages after consumer goes down.
> ------------------------------------------------
>
> Key: AMQ-1478
> URL: https://issues.apache.org/activemq/browse/AMQ-1478
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.1
> Environment: Producer box( Windows - running a broker - Producer configuration: persistent messages)
> Consumer box(Linux - with durable topics for persistence)
> Reporter: arpit shah
> Assignee: Rob Davies
> Fix For: 5.3.0
>
> Attachments: activemq.xml
>
>
> Configuration is attached below.
> Behavior:
> Set the persistent to be true in the broker configuration and created a durable topic to consume messages.
> Everything was fine until the consumer went down. During that time producer keeps producing messages. Restart consumer to catch all the missed messages but didn't catch them. After that the whole application hangs. can't produce any more messages, hence can't consume them. The heap usage size keeps increasing on the producer side.
> Increased memory size, which didn't work either. The received log is shown below on the broker side when it comes up and the message that shows up on the produce client window.
> Here is the message from the producer window:
> response from futureResponse was invalid
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 146
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 153
> FILE: ..\src\main\activemq\connector\openwire\OpenWireFormatNegotiator.c
> pp, LINE: 105
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 1454
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 924
> FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 675
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 194
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 149
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 108
> Here is broker log:
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker (localhost) is starting
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/
> 2007-10-25 15:56:32,654 [JMX connector ] INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> 2007-10-25 15:56:33,154 [main ] INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver]
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: org.apache.derby.jdbc.EmbeddedDataSource@8a2023
> 2007-10-25 15:56:34,748 [main ] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: C:\ActiveMQ\apache-activemq-4.1.1\apache-activemq-4.1.1\activemq-data\journal
> 2007-10-25 15:56:34,764 [main ] INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered.
> 2007-10-25 15:56:34,967 [main ] INFO TransportServerThreadSupport - Listening for connections at: tcp://PCSHAH:61616
> 2007-10-25 15:56:34,967 [main ] INFO TransportConnector - Connector openwire Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: ssl://PCSHAH:61617
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector ssl Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: stomp://PCSHAH:61613
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector stomp Started
> 2007-10-25 15:56:35,358 [main ] INFO NetworkConnector - Network Connector default-nc Started
> 2007-10-25 15:56:35,358 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:PCSHAH-2327-1193342192311-1:0) started
> 2007-10-25 15:56:51,421 [85.37.184:44137] INFO KahaStore - Kaha Store deleted data directory activemq-data\localhost\tmp_storage
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (AMQ-1478) Can't produce messages after
consumer goes down.
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AMQ-1478 started by Rob Davies.
> Can't produce messages after consumer goes down.
> ------------------------------------------------
>
> Key: AMQ-1478
> URL: https://issues.apache.org/activemq/browse/AMQ-1478
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.1
> Environment: Producer box( Windows - running a broker - Producer configuration: persistent messages)
> Consumer box(Linux - with durable topics for persistence)
> Reporter: arpit shah
> Assignee: Rob Davies
> Fix For: 5.3.0
>
> Attachments: activemq.xml
>
>
> Configuration is attached below.
> Behavior:
> Set the persistent to be true in the broker configuration and created a durable topic to consume messages.
> Everything was fine until the consumer went down. During that time producer keeps producing messages. Restart consumer to catch all the missed messages but didn't catch them. After that the whole application hangs. can't produce any more messages, hence can't consume them. The heap usage size keeps increasing on the producer side.
> Increased memory size, which didn't work either. The received log is shown below on the broker side when it comes up and the message that shows up on the produce client window.
> Here is the message from the producer window:
> response from futureResponse was invalid
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 146
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 153
> FILE: ..\src\main\activemq\connector\openwire\OpenWireFormatNegotiator.c
> pp, LINE: 105
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 1454
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 924
> FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 675
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 194
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 149
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 108
> Here is broker log:
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker (localhost) is starting
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/
> 2007-10-25 15:56:32,654 [JMX connector ] INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> 2007-10-25 15:56:33,154 [main ] INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver]
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: org.apache.derby.jdbc.EmbeddedDataSource@8a2023
> 2007-10-25 15:56:34,748 [main ] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: C:\ActiveMQ\apache-activemq-4.1.1\apache-activemq-4.1.1\activemq-data\journal
> 2007-10-25 15:56:34,764 [main ] INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered.
> 2007-10-25 15:56:34,967 [main ] INFO TransportServerThreadSupport - Listening for connections at: tcp://PCSHAH:61616
> 2007-10-25 15:56:34,967 [main ] INFO TransportConnector - Connector openwire Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: ssl://PCSHAH:61617
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector ssl Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: stomp://PCSHAH:61613
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector stomp Started
> 2007-10-25 15:56:35,358 [main ] INFO NetworkConnector - Network Connector default-nc Started
> 2007-10-25 15:56:35,358 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:PCSHAH-2327-1193342192311-1:0) started
> 2007-10-25 15:56:51,421 [85.37.184:44137] INFO KahaStore - Kaha Store deleted data directory activemq-data\localhost\tmp_storage
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1478) Can't produce messages after consumer
goes down.
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1478.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 5.4.0)
5.3.0
> Can't produce messages after consumer goes down.
> ------------------------------------------------
>
> Key: AMQ-1478
> URL: https://issues.apache.org/activemq/browse/AMQ-1478
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.1
> Environment: Producer box( Windows - running a broker - Producer configuration: persistent messages)
> Consumer box(Linux - with durable topics for persistence)
> Reporter: arpit shah
> Assignee: Rob Davies
> Fix For: 5.3.0
>
> Attachments: activemq.xml
>
>
> Configuration is attached below.
> Behavior:
> Set the persistent to be true in the broker configuration and created a durable topic to consume messages.
> Everything was fine until the consumer went down. During that time producer keeps producing messages. Restart consumer to catch all the missed messages but didn't catch them. After that the whole application hangs. can't produce any more messages, hence can't consume them. The heap usage size keeps increasing on the producer side.
> Increased memory size, which didn't work either. The received log is shown below on the broker side when it comes up and the message that shows up on the produce client window.
> Here is the message from the producer window:
> response from futureResponse was invalid
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 146
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 153
> FILE: ..\src\main\activemq\connector\openwire\OpenWireFormatNegotiator.c
> pp, LINE: 105
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 1454
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 924
> FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 675
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 194
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 149
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 108
> Here is broker log:
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker (localhost) is starting
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/
> 2007-10-25 15:56:32,654 [JMX connector ] INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> 2007-10-25 15:56:33,154 [main ] INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver]
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: org.apache.derby.jdbc.EmbeddedDataSource@8a2023
> 2007-10-25 15:56:34,748 [main ] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: C:\ActiveMQ\apache-activemq-4.1.1\apache-activemq-4.1.1\activemq-data\journal
> 2007-10-25 15:56:34,764 [main ] INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered.
> 2007-10-25 15:56:34,967 [main ] INFO TransportServerThreadSupport - Listening for connections at: tcp://PCSHAH:61616
> 2007-10-25 15:56:34,967 [main ] INFO TransportConnector - Connector openwire Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: ssl://PCSHAH:61617
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector ssl Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: stomp://PCSHAH:61613
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector stomp Started
> 2007-10-25 15:56:35,358 [main ] INFO NetworkConnector - Network Connector default-nc Started
> 2007-10-25 15:56:35,358 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:PCSHAH-2327-1193342192311-1:0) started
> 2007-10-25 15:56:51,421 [85.37.184:44137] INFO KahaStore - Kaha Store deleted data directory activemq-data\localhost\tmp_storage
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1478) Can't produce messages after consumer
goes down.
Posted by "Greg Griffin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40573 ]
Greg Griffin commented on AMQ-1478:
-----------------------------------
Saw exact same exception but in different environment. On one Windows box, CPP2.1 as producer, 4.1.1 for broker and receiver and producers. Nothing persistent or durable. No errors in broker log.
Repeatedly restarting the CPP producer gave same error. However when I took down all my java producer/receivers and restarted them, then the CPP producer worked fine.
Have been using 4.1.1 since May, and CPP2.1 for a week with no problems before. (run 100msg/second everyday)
> Can't produce messages after consumer goes down.
> ------------------------------------------------
>
> Key: AMQ-1478
> URL: https://issues.apache.org/activemq/browse/AMQ-1478
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.1
> Environment: Producer box( Windows - running a broker - Producer configuration: persistent messages)
> Consumer box(Linux - with durable topics for persistence)
> Reporter: arpit shah
> Attachments: activemq.xml
>
>
> Configuration is attached below.
> Behavior:
> Set the persistent to be true in the broker configuration and created a durable topic to consume messages.
> Everything was fine until the consumer went down. During that time producer keeps producing messages. Restart consumer to catch all the missed messages but didn't catch them. After that the whole application hangs. can't produce any more messages, hence can't consume them. The heap usage size keeps increasing on the producer side.
> Increased memory size, which didn't work either. The received log is shown below on the broker side when it comes up and the message that shows up on the produce client window.
> Here is the message from the producer window:
> response from futureResponse was invalid
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 146
> FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LIN
> E: 153
> FILE: ..\src\main\activemq\connector\openwire\OpenWireFormatNegotiator.c
> pp, LINE: 105
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 1454
> FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LIN
> E: 924
> FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 675
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 194
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 149
> FILE: ..\src\main\activemq\core\ActiveMQProducer.cpp, LINE: 108
> Here is broker log:
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - ActiveMQ 4.1.1 JMS Message Broker (localhost) is starting
> 2007-10-25 15:56:32,576 [main ] INFO BrokerService - For help or more information please see: http://incubator.apache.org/activemq/
> 2007-10-25 15:56:32,654 [JMX connector ] INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> 2007-10-25 15:56:33,154 [main ] INFO JDBCPersistenceAdapter - Database driver recognized: [apache_derby_embedded_jdbc_driver]
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Attempting to acquire the exclusive lock to become the Master broker
> 2007-10-25 15:56:33,904 [main ] INFO DefaultDatabaseLocker - Becoming the master on dataSource: org.apache.derby.jdbc.EmbeddedDataSource@8a2023
> 2007-10-25 15:56:34,748 [main ] INFO JournalPersistenceAdapter - Journal Recovery Started from: Active Journal: using 5 x 20.0 Megs at: C:\ActiveMQ\apache-activemq-4.1.1\apache-activemq-4.1.1\activemq-data\journal
> 2007-10-25 15:56:34,764 [main ] INFO JournalPersistenceAdapter - Journal Recovered: 0 message(s) in transactions recovered.
> 2007-10-25 15:56:34,967 [main ] INFO TransportServerThreadSupport - Listening for connections at: tcp://PCSHAH:61616
> 2007-10-25 15:56:34,967 [main ] INFO TransportConnector - Connector openwire Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: ssl://PCSHAH:61617
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector ssl Started
> 2007-10-25 15:56:35,280 [main ] INFO TransportServerThreadSupport - Listening for connections at: stomp://PCSHAH:61613
> 2007-10-25 15:56:35,280 [main ] INFO TransportConnector - Connector stomp Started
> 2007-10-25 15:56:35,358 [main ] INFO NetworkConnector - Network Connector default-nc Started
> 2007-10-25 15:56:35,358 [main ] INFO BrokerService - ActiveMQ JMS Message Broker (localhost, ID:PCSHAH-2327-1193342192311-1:0) started
> 2007-10-25 15:56:51,421 [85.37.184:44137] INFO KahaStore - Kaha Store deleted data directory activemq-data\localhost\tmp_storage
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.