You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by liquidd <sp...@mail.ru> on 2009/05/13 13:41:33 UTC

Restoring ActiveMQ

AMQ have more than 1.5M messages. After shutdown and restart amq it writes:

jvm 1    | INFO  DefaultCamelContext            - JMX enabled. Using
InstrumentationLifecycleStrategy.
jvm 1    | INFO  BrokerService                  - Using Persistence Adapter:
AMQPersistenceAdapter(../../data)
jvm 1    | INFO  AMQPersistenceAdapter          - AMQStore starting using
directory: ../../data
jvm 1    | INFO  KahaStore                      - Kaha Store using data
directory ../../data/kr-store/state
jvm 1    | INFO  AMQPersistenceAdapter          - Active data files: []
jvm 1    | WARN  AMQPersistenceAdapter          - The ReferenceStore is not
valid - recovering ...
jvm 1    | INFO  KahaStore                      - Kaha Store successfully
deleted data directory ../../data/kr-store/data
jvm 1    | INFO  AMQPersistenceAdapter          - Journal Recovery Started
from: DataManager:(data-)
jvm 1    | INFO  KahaStore                      - Kaha Store using data
directory ../../data/kr-store/data
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_trace from 1024 to 2048
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_data_exchange from 1024 to 2048
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_activity from 1024 to 2048
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_trace from 2048 to 4096
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_data_exchange from 2048 to 4096
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_activity from 2048 to 4096
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_trace from 4096 to 8192
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_activity from 4096 to 8192
jvm 1    | INFO  HashIndex                      - Resize hash bins
queue-data_queue://log_data_exchange from 4096 to 8192

and after last line - nothing: CPU is 0.0%. How long does it takes to
restart?
-- 
View this message in context: http://www.nabble.com/Restoring-ActiveMQ-tp23520138p23520138.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: Restoring ActiveMQ

Posted by Rob Davies <ra...@gmail.com>.
It can take a while - how long have you left it for ?

On 13 May 2009, at 13:41, liquidd wrote:

>
> AMQ have more than 1.5M messages. After shutdown and restart amq it  
> writes:
>
> jvm 1    | INFO  DefaultCamelContext            - JMX enabled. Using
> InstrumentationLifecycleStrategy.
> jvm 1    | INFO  BrokerService                  - Using Persistence  
> Adapter:
> AMQPersistenceAdapter(../../data)
> jvm 1    | INFO  AMQPersistenceAdapter          - AMQStore starting  
> using
> directory: ../../data
> jvm 1    | INFO  KahaStore                      - Kaha Store using  
> data
> directory ../../data/kr-store/state
> jvm 1    | INFO  AMQPersistenceAdapter          - Active data files:  
> []
> jvm 1    | WARN  AMQPersistenceAdapter          - The ReferenceStore  
> is not
> valid - recovering ...
> jvm 1    | INFO  KahaStore                      - Kaha Store  
> successfully
> deleted data directory ../../data/kr-store/data
> jvm 1    | INFO  AMQPersistenceAdapter          - Journal Recovery  
> Started
> from: DataManager:(data-)
> jvm 1    | INFO  KahaStore                      - Kaha Store using  
> data
> directory ../../data/kr-store/data
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_trace from 1024 to 2048
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_data_exchange from 1024 to 2048
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_activity from 1024 to 2048
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_trace from 2048 to 4096
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_data_exchange from 2048 to 4096
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_activity from 2048 to 4096
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_trace from 4096 to 8192
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_activity from 4096 to 8192
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_data_exchange from 4096 to 8192
>
> and after last line - nothing: CPU is 0.0%. How long does it takes to
> restart?
> -- 
> View this message in context: http://www.nabble.com/Restoring-ActiveMQ-tp23520138p23520138.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Re: Restoring ActiveMQ

Posted by Roland Thomas Lichti <ro...@telefonica.de>.
liquidd schrieb:
> AMQ have more than 1.5M messages. After shutdown and restart amq it writes:
>
> [...]
> queue-data_queue://log_activity from 4096 to 8192
> jvm 1    | INFO  HashIndex                      - Resize hash bins
> queue-data_queue://log_data_exchange from 4096 to 8192
>
> and after last line - nothing: CPU is 0.0%. How long does it takes to
> restart?
>   

Well. We had 2.4M messages in a local oracle 10g database and it took 40 
minutes to recover. It read every message into memory and checked it for 
its parameters (queue and so on) before it reopened the network connectors.

bye,
   Roland