Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP 5.1.0 Post Release
    • Fix Version/s: EAP_EWP 5.1.1
    • Component/s: None
    • Labels:
      None
    • Release Notes Text:
      If paging files previous used by HornetQ were removed, it would fail to start at the next attempt. The logic relating the existence of paging files has been modified to resolve this issue.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      1) We restarted one of our HQ instances and it failed to startup since there existed a empty paging folder.
      The server complained that it could not find "address.txt" and did not startup cleanly.
      No JMS clients could connect to the server. See attached file for data folder + logs. From server.log =============== 2011-07-08 10:07:50,300 WARN [org.hornetq.core.paging.impl.PagingStoreFactoryNIO] (main) Directory /jms-md1/paging/732910a didn't have an identification file address.txt 2011-07-08 10:08:09,449 SEVERE [org.hornetq.core.server.impl.HornetQServerImpl] (main) Failure in initialisation java.lang.NullPointerException at org.hornetq.core.paging.cursor.impl.PageSubscriptionImpl.getPageInfo(PageSubscriptionImpl.java:726) at org.hornetq.core.paging.cursor.impl.PageSubscriptionImpl.getPageInfo(PageSubscriptionImpl.java:712) at org.hornetq.core.paging.cursor.impl.PageSubscriptionImpl.processReload(PageSubscriptionImpl.java:655) at org.hornetq.core.paging.cursor.impl.PageCursorProviderImpl.processReload(PageCursorProviderImpl.java:241) at org.hornetq.core.paging.impl.PagingStoreImpl.processReload(PagingStoreImpl.java:355) at org.hornetq.core.paging.impl.PagingManagerImpl.processReload(PagingManagerImpl.java:250) at org.hornetq.core.persistence.impl.journal.JournalStorageManager.loadMessageJournal(JournalStorageManager.java:1229) at org.hornetq.core.server.impl.HornetQServerImpl.loadJournals(HornetQServerImpl.java:1619) at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1469) at org.hornetq.core.server.impl.HornetQServerImpl.access$100(HornetQServerImpl.java:132) at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreLiveActivation.run(HornetQServerImpl.java:356) at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:570) at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:262) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59) at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150) at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) 2) We deleted the empty paging folder and tried to start again. Again the server failed to startup cleanly. From server.log: ================ 2011-07-08 12:17:29,620 INFO [org.hornetq.core.server.impl.AIOFileLockNodeManager] (main) Live Server Obtained live lock 2011-07-08 12:17:48,522 SEVERE [org.hornetq.core.server.impl.HornetQServerImpl] (main) Failure in initialisation java.lang.NullPointerException at org.hornetq.core.paging.cursor.impl.PageSubscriptionImpl.getPageInfo(PageSubscriptionImpl.java:726) at org.hornetq.core.paging.cursor.impl.PageSubscriptionImpl.getPageInfo(PageSubscriptionImpl.java:712) at org.hornetq.core.paging.cursor.impl.PageSubscriptionImpl.processReload(PageSubscriptionImpl.java:655) at org.hornetq.core.paging.cursor.impl.PageCursorProviderImpl.processReload(PageCursorProviderImpl.java:241) at org.hornetq.core.paging.impl.PagingStoreImpl.processReload(PagingStoreImpl.java:355) at org.hornetq.core.paging.impl.PagingManagerImpl.processReload(PagingManagerImpl.java:250) at org.hornetq.core.persistence.impl.journal.JournalStorageManager.loadMessageJournal(JournalStorageManager.java:1229) at org.hornetq.core.server.impl.HornetQServerImpl.loadJournals(HornetQServerImpl.java:1619) at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1469) at org.hornetq.core.server.impl.HornetQServerImpl.access$100(HornetQServerImpl.java:132) at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreLiveActivation.run(HornetQServerImpl.java:356) at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:570) at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:262) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 3) Restarted the server and had the same behavior as (2) 4) Deleted the entire contents of the "journal" folder. The "paging" and "large-messages" folders were already empty. Restarted the server. Server started up fine.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  clebert.suconic Clebert Suconic
                  Reporter:
                  rogerhui Roger Hui
                  Writer:
                  Russell Dickenson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: