[JBoss JIRA] Created: (JOPR-73) Add support for changing arguments passed to start/stop operations
by Charles Crouch (JIRA)
Add support for changing arguments passed to start/stop operations
------------------------------------------------------------------
Key: JOPR-73
URL: https://jira.jboss.org/jira/browse/JOPR-73
Project: Jopr
Issue Type: Feature Request
Components: Plugin - JBoss AS 4, Plugin - JBoss AS 5
Reporter: Charles Crouch
Comes out of case: 264527
Right now if you change the start/stop scripts used by a JBAS instance the new scripts have to understand the same arguments which the default jbas ones takes, e.g. for shutdown thats:
--server=jnp://localhost:1099 --user=myuser --password=mypassword --shutdown
Given we enable people to specify their own scripts for these operations we should enable them to configure the arguments we pass to the scripts, just like we do when executing a JBAS script resource.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (JOPR-429) jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JOPR-429?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on JOPR-429:
----------------------------------------------
Mike Foley <mfoley(a)redhat.com> made a comment on [bug 802902|https://bugzilla.redhat.com/show_bug.cgi?id=802902]
re-evaluate post 3.1 (per triage asantos, loleary, ccrouch, mfoley)
> jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JOPR-429
> URL: https://issues.jboss.org/browse/JOPR-429
> Project: Jopr
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: JON 2.3 with EAP plug-in pack
> Sun JVM 1.6.0_16
> RHEL5 (kernel: 2.6.18-128.el5)
> jopr-jboss-cache-v3-plugin-2.3.0.GA.jar
> EAP5 production install/configuration
> Reporter: Larry O'Leary
>
> 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:
> # 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}/server/jon-jbcache3-status-issue/log
> rm boot.log cluster.log server.log
> cd ${JBOSS_HOME}/bin
> ./run.sh -c jon-jbcache3-status-issue -Djboss.partition.name=MyPartition -Djboss.platform.mbeanserver -Djboss.service.binding.set=ports-01 -b 0.0.0.0 &
> 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/cou...
> rm -r counter_DIR
> unzip counter.zip -d counter_DIR
> cp counter_DIR/counter/dist/counter.war ${JBOSS_HOME}/server/jon-jbcache3-status-issue/deploy
> * 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 ${JBOSS_HOME}/bin
> ./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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JOPR-429) jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JOPR-429?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on JOPR-429:
----------------------------------------------
Larry O'Leary <loleary(a)redhat.com> made a private comment on [bug 802902|https://bugzilla.redhat.com/show_bug.cgi?id=802902]
> jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JOPR-429
> URL: https://issues.jboss.org/browse/JOPR-429
> Project: Jopr
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: JON 2.3 with EAP plug-in pack
> Sun JVM 1.6.0_16
> RHEL5 (kernel: 2.6.18-128.el5)
> jopr-jboss-cache-v3-plugin-2.3.0.GA.jar
> EAP5 production install/configuration
> Reporter: Larry O'Leary
>
> 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:
> # 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}/server/jon-jbcache3-status-issue/log
> rm boot.log cluster.log server.log
> cd ${JBOSS_HOME}/bin
> ./run.sh -c jon-jbcache3-status-issue -Djboss.partition.name=MyPartition -Djboss.platform.mbeanserver -Djboss.service.binding.set=ports-01 -b 0.0.0.0 &
> 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/cou...
> rm -r counter_DIR
> unzip counter.zip -d counter_DIR
> cp counter_DIR/counter/dist/counter.war ${JBOSS_HOME}/server/jon-jbcache3-status-issue/deploy
> * 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 ${JBOSS_HOME}/bin
> ./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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JOPR-429) jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JOPR-429?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated JOPR-429:
-----------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=802902
> jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JOPR-429
> URL: https://issues.jboss.org/browse/JOPR-429
> Project: Jopr
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: JON 2.3 with EAP plug-in pack
> Sun JVM 1.6.0_16
> RHEL5 (kernel: 2.6.18-128.el5)
> jopr-jboss-cache-v3-plugin-2.3.0.GA.jar
> EAP5 production install/configuration
> Reporter: Larry O'Leary
>
> 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:
> # 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}/server/jon-jbcache3-status-issue/log
> rm boot.log cluster.log server.log
> cd ${JBOSS_HOME}/bin
> ./run.sh -c jon-jbcache3-status-issue -Djboss.partition.name=MyPartition -Djboss.platform.mbeanserver -Djboss.service.binding.set=ports-01 -b 0.0.0.0 &
> 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/cou...
> rm -r counter_DIR
> unzip counter.zip -d counter_DIR
> cp counter_DIR/counter/dist/counter.war ${JBOSS_HOME}/server/jon-jbcache3-status-issue/deploy
> * 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 ${JBOSS_HOME}/bin
> ./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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JOPR-429) jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JOPR-429?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated JOPR-429:
-----------------------------------------
Bugzilla Update: Perform
> jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JOPR-429
> URL: https://issues.jboss.org/browse/JOPR-429
> Project: Jopr
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: JON 2.3 with EAP plug-in pack
> Sun JVM 1.6.0_16
> RHEL5 (kernel: 2.6.18-128.el5)
> jopr-jboss-cache-v3-plugin-2.3.0.GA.jar
> EAP5 production install/configuration
> Reporter: Larry O'Leary
>
> 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:
> # 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}/server/jon-jbcache3-status-issue/log
> rm boot.log cluster.log server.log
> cd ${JBOSS_HOME}/bin
> ./run.sh -c jon-jbcache3-status-issue -Djboss.partition.name=MyPartition -Djboss.platform.mbeanserver -Djboss.service.binding.set=ports-01 -b 0.0.0.0 &
> 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/cou...
> rm -r counter_DIR
> unzip counter.zip -d counter_DIR
> cp counter_DIR/counter/dist/counter.war ${JBOSS_HOME}/server/jon-jbcache3-status-issue/deploy
> * 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 ${JBOSS_HOME}/bin
> ./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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JOPR-429) jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
by Larry O'Leary (JIRA)
[ https://issues.jboss.org/browse/JOPR-429?page=com.atlassian.jira.plugin.s... ]
Larry O'Leary resolved JOPR-429.
--------------------------------
Resolution: Migrated to another ITS
JOPR no longer exists and this issue has been re-identified in JON 3.0 and RHQ 4.2. This JIRA is being closed and new BZ https://bugzilla.redhat.com/show_bug.cgi?id=802902 has been created.
> jboss-cache-v3-plugin: Shows invalid "unavailable" state for cache services that are not currently deployed/used in EAP
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JOPR-429
> URL: https://issues.jboss.org/browse/JOPR-429
> Project: Jopr
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: JON 2.3 with EAP plug-in pack
> Sun JVM 1.6.0_16
> RHEL5 (kernel: 2.6.18-128.el5)
> jopr-jboss-cache-v3-plugin-2.3.0.GA.jar
> EAP5 production install/configuration
> Reporter: Larry O'Leary
>
> 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:
> # 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}/server/jon-jbcache3-status-issue/log
> rm boot.log cluster.log server.log
> cd ${JBOSS_HOME}/bin
> ./run.sh -c jon-jbcache3-status-issue -Djboss.partition.name=MyPartition -Djboss.platform.mbeanserver -Djboss.service.binding.set=ports-01 -b 0.0.0.0 &
> 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/cou...
> rm -r counter_DIR
> unzip counter.zip -d counter_DIR
> cp counter_DIR/counter/dist/counter.war ${JBOSS_HOME}/server/jon-jbcache3-status-issue/deploy
> * 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 ${JBOSS_HOME}/bin
> ./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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months