Thanks for you reply, shall I fill a bug for this ?

On 12/02/2020 16:43, Rémy Maucherat wrote:
On Wed, Feb 12, 2020 at 3:05 PM Arnaud Yahoo <>


Recently storeConfig has been fixed thanks to

It is very interesting, because it allows to persist across restart
configurations made to tomcat itself and deployed webapp through JMX.

In my case after saving a configuration to my webapp I lost my
cacheMaxSize customization.

I had in my context xml file this:

<Resources cachingAllowed="true" cacheMaxSize="102400" />

and after calling storeConfig It has been changed to this

<Resources className="org.apache.catalina.webresources.StandardRoot"> so
cacheMaxSize has been reverted to default value.

I understand it is because in
/org/apache/catalina/storeconfig/server-registry.xml /

//        tag="Resources"//
//        standard="false"//
//        default="false"//
//        children="true"//
//        tagClass="org.apache.catalina.WebResourceRoot"//
//     </Description>/

cacheMaxSize is declared as Transient so not saved in updated context
xml file.

Is it something expected ? or can it be considered as a bug ?

The old resources were configured on the Context so that's where this
transient attribute list comes from. However, that doesn't work like this
anymore with the new resources so the list must be empty except domain.




To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to