ActiveMQ startup exception

Source: Internet
Author: User

When you follow the steps in ActiveMQ in Action, once an ActiveMQ exception is terminated, the ActiveMQ cannot be started and an error is always reported.

14:45:13, 552 | ERROR | Failed to start ActiveMQ JMS Message Broker. reason: java. io. EOFException: Chunk stream does not exist at page: 0 | org. apache. activemq. broker. brokerService | main
Java. io. EOFException: Chunk stream does not exist at page: 0
At org. apache. kahadb. page. Transaction $2. readPage (Transaction. java: 454)
At org. apache. kahadb. page. Transaction $2. <init> (Transaction. java: 431)
At org. apache. kahadb. page. Transaction. openInputStream (Transaction. java: 428)
At org. apache. kahadb. page. Transaction. load (Transaction. java: 404)
At org. apache. kahadb. page. Transaction. load (Transaction. java: 361)
At org.apache.activemq.broker.scheduler.jobschedulerstore00003.exe cute (JobSchedulerStore. java: 250)
At org.apache.kahadb.page.Transaction.exe cute (Transaction. java: 728)
At org. apache. activemq. broker. scheduler. JobSchedulerStore. doStart (JobSchedulerStore. java: 239)
At org. apache. activemq. util. ServiceSupport. start (ServiceSupport. java: 53)
At org. apache. activemq. broker. scheduler. SchedulerBroker. getStore (SchedulerBroker. java: 198)
At org. apache. activemq. broker. scheduler. SchedulerBroker. getInternalScheduler (SchedulerBroker. java: 185)
At org. apache. activemq. broker. scheduler. SchedulerBroker. start (SchedulerBroker. java: 85)


After searching, we found that this was a bug in ActiveMQ5.4.1. Solved in 5.5.

Its a known bug and fixed in current trunk (5.5-SNAPSHOT ).

Https://issues.apache.org/jira/browse/AMQ-2935

However, in order to avoid problems due to version mismatch and other reasons during the learning process, the search continued and finally found a solution. This is mainly caused by the introduction of the delayed sending function in version 5.4.1. The solution is to add the schedulerSupport = "false" attribute to <broker> and disable the scheduler function.

Reference http://blog.csdn.net/technofantasy/article/details/6037295

 

Code

 

<Broker xmlns = "http://activemq.apache.org/schema/core" brokerName = "SIBBusModule-TestDeCharge-td0sib01s" useJmx = "true" persistent = "false" useShutdownHook = "false" schedulerSupport = "false">

 

Also, delete all the content in data/xxxx/scheduler under the activemq directory, but I didn't try

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.