Can the ageout-history command be executed without starting an JBoss EAP instance?
Issue
- It is a bit inconsistent that we can apply a patch without starting the instance but we need to start an instance to execute the command
core-service=patching:ageout-history
in order to reduce the memory footprint after applying a patch - I'm trying to automate our build process by combining the 6.4.0 GA and a patch file. And the process becomes a bit cumbersome when we have to fire up the instance.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.2+
- 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.