Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8305

CacheNotReadyException when hitting HAJNDI during shutdown

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • Clustering
    • None
    • Release Notes
    • Hide
      It was found that, because HAJNDI continued to process requests while shutting down, clients could receive <literal>CacheNotReadyException</literal> errors from components that are not in the correct state. As a resolution to this issue, HAJNDI now throws <literal>javax.naming.ServiceUnavailableException</literal> if a request comes in during shutdown, and the shutdown process waits for existing requests to complete.
      Show
      It was found that, because HAJNDI continued to process requests while shutting down, clients could receive <literal>CacheNotReadyException</literal> errors from components that are not in the correct state. As a resolution to this issue, HAJNDI now throws <literal>javax.naming.ServiceUnavailableException</literal> if a request comes in during shutdown, and the shutdown process waits for existing requests to complete.
    • Documented as Resolved Issue
    • NEW

    Description

      org.jboss.cache.invocation.CacheNotReadyException: Cache not in a valid STARTED state! Cache state is STOPPING
      at org.jboss.cache.invocation.CacheInvocationDelegate.cacheStatusCheck(CacheInvocationDelegate.java:695)
      at org.jboss.cache.invocation.CacheInvocationDelegate.get(CacheInvocationDelegate.java:442)
      at org.jboss.ha.cachemanager.CacheManagerManagedCache.get(CacheManagerManagedCache.java:193)
      at org.jboss.ha.jndi.impl.jbc.JBossCacheDistributedTreeManager.lookup(JBossCacheDistributedTreeManager.java:346)
      at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:202)
      ...

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue JBPAPP-8838 Retry HAJNDI call on ServiceUnavailableException

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-8152 HA-JNDI still processes requests before fully initialized

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-dereed Dennis Reed
              rhn-support-dereed Dennis Reed
              Scott Thomas Scott Thomas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: