Uploaded image for project: 'Jopr (CLOSED)'
  1. Jopr (CLOSED)
  2. JOPR-429

jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP


    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Migrated to another ITS
    • Affects Version/s: 2.3
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:

      JON 2.3 with EAP plug-in pack
      Sun JVM 1.6.0_16
      RHEL5 (kernel: 2.6.18-128.el5)
      EAP5 production install/configuration


      When JON discovers JBoss Cache 3 services all seems fine. At some future point all the discovered cache services show an unavailable state. This is because EAP will only deploy the caches that are needed or requested by a deployed application. For example, standard-session-cache is only deployed when a web application that utilizes the session cache is deployed and started.

      So, if a user deploys an application to EAP that requires a cache, the cache will be deployed and started. Later, if the application no longer requires the cache or is un-deployed, the user will continue to see this false unavailable state.

      To demonstrate:

      1. Make a copy of production configuration as jon-jbcache3-status-issue
        cd $ {JBOSS_HOME}/server
        cp -R production jon-jbcache3-status-issue
        cd jon-jbcache3-status-issue/conf/props
        sed -i.orig 's/^# admin=admin/admin=admin/' jmx-console-users.properties
        cd ../../..

        # Statup EAP5 instance using service binding manager
        cd ${JBOSS_HOME}

        rm boot.log cluster.log server.log
        cd $

        ./run.sh -c jon-jbcache3-status-issue -Djboss.partition.name=MyPartition -Djboss.platform.mbeanserver -Djboss.service.binding.set=ports-01 -b &
        sleep 10
        # EAP instance should be at http://localhost:8180

        # Startup RHQ-Server
        cd ${JON_HOME}/logs
        rm boot.log rhq-server-log4j.log
        cd ${JON_HOME}/bin
        ./rhq-server.sh start
        sleep 10
        # JON Server should be at http://localhost:7080

        # Startup RHQ-Agent
        cd ${JON_AGENT_HOME}/logs
        rm agent.log
        cd ${JON_AGENT_HOME}/bin
        export RHQ_AGENT_DEBUG=1
        ./rhq-agent-wrapper.sh start
        sleep 10

        * From JON, import the newly deployed EAP instance
        * Once imported and available, expand its JBoss Cache resource
        Notice ha-partition and MyPartition-HAPartitionCache are the only caches listed
        * Expand ha-partition
        Notice all cache services show as available
        * Expand MyPartition-HAPartitionCache
        Notice all cache services show as available

        Deploy the sample counter.war web application:

        cd /tmp
        curl -O http://community.jboss.org/servlet/JiveServlet/download/11823-10-5589/counter.zip
        rm -r counter_DIR
        unzip counter.zip -d counter_DIR
        cp counter_DIR/counter/dist/counter.war ${JBOSS_HOME}


      • Wait for EAP to pick-up the new deployment
      • Wait for JON to discover and inventory new WAR
      • Once inventoried and available, expand JBoss Cache resource
        Notice ha-partition, MyPartition-HAPartitionCache, MyPartition-SessionCache, and standard-session-cache are listed
      • Select each of the four cache services
        Notice all cache services show as available

      You can also see these cache services via JMX in EAP:
      cd $


      ./twiddle.sh -s localhost:1199 -u admin -p admin query 'jboss.cache:*'

      • Un-inventory and remove the counter.war web application (Inventory tab of EAP instance)

      At this point (once JON reflects the change in availability), some of the cache services for standard-session-cache and SessionCache will show as unavailable.

      If you restart the EAP instance, all the cache services for these two cache resources will show unavailable. This is because as application deployments no longer need the caches service, they are no longer needed.

      If the counter.war application is re-deployed, the caches will reflect available again.

      It is understood that "unavailable" mean that something is no longer available, but it gives the user a false sense of a failure in this situation.

        Gliffy Diagrams




              • Assignee:
                loleary Larry O'Leary
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created: