Red Hat Bugzilla – Bug 1285131
KIE server state xml file create in root of server start in filesystem
Last modified: 2015-12-02 07:00:21 EST
Created attachment 1098473 [details]
kie server state xml file?
Description of problem: When I install and start bpm suite 6.2.CR1 it generates an XML file that contains the following:
$ cat 15ad5bfa-7532-3eea-940a-abbbbc89f1e8.xml
This is placed in the filesystem at the location of where the bpm suite server is started.
Version-Release number of selected component (if applicable): bpm suite 6.2.CR1
How reproducible: install product, start server
Steps to Reproduce:
1. see above.
Actual results: XML file in location server started.
Expected results: XML configuration files in eap server configuration directory, in this case expect it in jboss-eap6.4/standalone/configuration/15ad5bfa-7532-3eea-940a-abbbbc89f1e8.xml
Attachement is screenshot of file in root of my demo project, where I start the standalone bpm suite product from.
you can change it by setting system property:
Value: desired location where this xml file should be created
Thanks Maciej, that is what I suspected.
I suggest the bug here would be about setting the default to the EAP configuration directory to avoid losing that file somewhere on your system when starting the BPM Suite server.
in this case I'd say this is more for the installer to be consistent with other system properties we set (like org.kie.demo=false, etc). wdyt?
(In reply to Maciej Swiderski from comment #4)
> in this case I'd say this is more for the installer to be consistent with
> other system properties we set (like org.kie.demo=false, etc). wdyt?
Yes, this is fine, a sane default.
moving to installer component as discussed in the comments above
I'm thinking of setting the property to jboss.server.config.dir; this means that the xml will be created in different places depending on if standalone / domain is executed. is that acceptable?
(In reply to Thomas Hauser from comment #7)
> I'm thinking of setting the property to jboss.server.config.dir; this means
> that the xml will be created in different places depending on if standalone
> / domain is executed. is that acceptable?
(In reply to Eric D. Schabell from comment #8)
> (In reply to Thomas Hauser from comment #7)
> > I'm thinking of setting the property to jboss.server.config.dir; this means
> > that the xml will be created in different places depending on if standalone
> > / domain is executed. is that acceptable?
> Perfectly acceptable.
Just thinking that this file is not a config file, but saves the state of the KIE server... maybe into the data dir of EAP? That's where I have been storing it in my demos.
Alright, I'll give that property the default value for the data dir :)
After the changes above, here's where the kie state xmls are saved; also included is what the property is assigned to. Looks pretty good to me, let me know if something should change.
That's exactly what I have in my demo projects now. Works for me, thanks.
Kie server state xml file is now created in data dirs instead of root of server start in filesystem.
Verified in 6.2.0.CR2.
Same fix needed for BRMS 6.2.0.CR2 installer, still puts state xml file in root of server start in filesystem. Same bug or new bug?
Confirm fix for BPM Suite 6.2.0.CR2 installer.
I have tried it with both BPMS and BRMS installers and the results were same.
I didn't manage to reproduce with BRMS on CR2.
Path to xml state files after standalone.sh on BRMS:
Path to xml state files after domain.sh on BRMS:
Yes, my bad, need to update my installation xml files. Confirm works here too.