I verified this is no longer an issue with JDG 6.6.0.DR2 server. And I used latest jdg jon plugins -- i.e. those staged with JDG 6.6.0.DR2 release (since now I was testing using released with 6.4.1 - now I switched to the newest one from PROD team) For verification I used JON environment and bundle-like deployment, using procedures mentioned in comments here: https://bugzilla.redhat.com/show_bug.cgi?id=1213818 In short: * install jon * install jdg and agents * create new bundle * use bundle recipe from ^ BZ 1213818 * pick up and upload cache store modified implementation snapshot from target dir on your local drive * create a group for jdg server * select bundle, click deploy * select server group with jdg server * deploy, specify installation folder - deployment field: /standalone/deployments * finish * go to the machine where jdg server is installed * modify server config file manually * add custom cache store (in my case: <store class="org.infinispan.CustomExternalStore" passivation="false"/> as this is my custom implementation, modified and built locally from jdg-ccs archetype) * restart jdg server using jon UI * check logs for outputs, cache store is registered and working * all operations happened in time! (verifying this BZ) Thank you Sebastian for a fix!
Sebastian Łaskawiec <slaskawi> updated the status of jira ISPN-5595 to Resolved