Bug 1213818

Created attachment 1016788 [details]
here you can see reversed (wrong) order of cache start and deployment registration

Created attachment 1017823 [details]
RHQ deployment bundle with custom cache

It seems that deployments added by JON are scanned in different phase then those which are placed in the filesystem. Unfortunately I can't tell why - it needs further investigation.

Luckily, there is a workaround - use Bundle deployment with the following recipe:

# Recipe for Custom Cache
bundle --name "Custom Cache Store" --version=1.0.0 --description "A Custom Cache"
file --source custom-store.jar --destination "@@rhq.deploy.dir@@/deployments/custom-store.jar"

(An exemplary file has been attached to this issue.)

This simulates placing the file on the filesystem, so everything works just like it was deployed locally.

We agreed with Tristan not to implement it. This kind of features will be provided in our own console.

JON plugin is in maintenance mode.

Closing as WONTFIX. 

This use-case will not be supported. Users and Admins will use copy or CLI deployment procedures in order to deploy custom cache store implementations on server.

Trying the same process with JON 3.3.0.GA, getting: 

[Distribution File] Failed to upload bundle distribution file : javax.ejb.EJBException:java.lang.IllegalArgumentException: Invalid bundle distribution file. BundleType/Recipe not recognized by any deployed server bundle plugin. -> java.lang.IllegalArgumentException:Invalid bundle distribution file. BundleType/Recipe not recognized by any deployed server bundle plugin.
javax.ejb.EJBException: java.lang.IllegalArgumentException: Invalid bundle distribution file. BundleType/Recipe not recognized by any deployed server bundle plugin.

I also tried replace deploy.txt with deploy.xml, getting the same error. The strange thing is that the plugin responsible for that functionality is installed properly: 

Display Name :	
Wildfly Patch Bundle Processor
	Name :	
WflyPatchBundleServerPlugin
Version :	
4.12.0.JON330GA

I recommend to ask JON team for help. I might overlook some minor or major fact and this will be probably the fastest way to get it work -- or to find out other actions.

Created attachment 1020526 [details]
JON deployment bundle with custom cache

The correct Custom Cache installation procedure via JON:
1. Create a deployment bundle
  a. Use "JON deployment bundle with custom cache" attachment as a template or create your own bundle. This should be a zip file with a custom cache store jar and a deploy.xml in it:
<?xml version="1.0"?>
<project name="cc-bundle" default="main" xmlns:rhq="antlib:org.rhq.bundle">
 
  <rhq:bundle name="Mongo DB Custom Cache Store" version="1.0" description="Custom Cache Store">
  	<rhq:deployment-unit name="JDG" compliance="full">
  	  <rhq:file name="custom-store.jar" replace="true"/>
  	</rhq:deployment-unit>
  </rhq:bundle>

  <target name="main" />
    
</project>
2. Log into JON
3. Navigate to "Bundles" (upper bar)
4. Click "New" button and choose "Upload" radio button
5. Click "Select File" and upload bundle created in #1
6. Finish the wizard using default options
7. Get back to "Bundles" tab
8. Select newly created bundle and click Deploy
9. Enter "Destination Name" and choose proper Resource Group (there should be only JDG servers in that group)
10. Choose "Install Directory" from "Base Location"s radio box group
11. Enter "/standalone/deployments" in "Deployment Directory" below
12. Proceed with the wizard using default options
13. Validate the deployment using "find $JDG_HOME -name "custom-store.jar" 2>/dev/null" on server host
14. Note that the bundle should be installed in $JDG_HOME/standalone/deployments

Setting back to assigned. There is ongoing parallel email discussion with regards to this issue.

Doc text describing an issue...

We have to remove replace="true" from our bundle file. When the property is enabled it is supposed to read the file as a string and replace tokens with bundle input parameters. If you remove that attribute, it does not modify your jar.

If anyone wants to thank someone - Filib Brychta from JON QE is the right person and credit goes to him ;)


The corrected version looks like this: 

<?xml version="1.0"?>
<project name="cc-bundle" default="main" xmlns:rhq="antlib:org.rhq.bundle"> 
  <rhq:bundle name="External Custom Cache Store" version="1.1" description="Custom Cache Store">
  	<rhq:deployment-unit name="JDG" compliance="full">
  	  <rhq:file name="external-store-1.0-SNAPSHOT.jar" />
  	</rhq:deployment-unit>
  </rhq:bundle>
  <target name="main" />    
</project>

I verified this is working now! 

I was able to create a bundle like putting this content into JON dialog window, specify my custom cache store .jar file (from my local disk), upload it to jon, finish bundle creating ... select bundle, open, select a group where to deploy (preprepared to include a JDG server) and I deploy that. Then I reconfigured a cache on JDG server to add a cache store... and issued a restart from JON. 

Looking at server logs, the custom cache store .jar file was PUT into standalone/deployments folder (now unchanged!!!) and was registered by our deployment scanner, deployed and was USED SUCCESSFULLY by a cache. 

That works! 
Thank you everyone involved.

Closing this one...
We have a workaround -- we will use JON Bundles and recipe for Custom Cache Store .jar file deployment