[
https://issues.apache.org/jira/browse/GERONIMO-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed GERONIMO-5198.
-----------------------------------
Resolution: Won't Fix
Closing old outdated issues.
Note that the Apache Geronimo Application Server itself was declared EOL in
2017 and we do not maintain the server parts anymore.
We still do actively maintain many of the Java EE / Jakarta EE which saw the
light during creation of the Apache Geronimo Aplication Server.
If you feel that this ticket still affects one of those components then please
feel free to reopen the ticket.
thanks, your Apache Geronimo team!
> MultiParentClassLoader caching not found resources
> --------------------------------------------------
>
> Key: GERONIMO-5198
> URL: https://issues.apache.org/jira/browse/GERONIMO-5198
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.2
> Environment: Linux 64 bit
> Reporter: Marco Laponder
> Priority: Major
> Fix For: 2.2.2
>
>
> We have extended the default classpath with a directory by specifying in the
> deployment plan an org.apache.geronimo.system.sharedlib.SharedLib gbean. So
> we are able to read application specific files from this directory.
> It is possbile for out application the resource can not be found at a given
> time, but the resource exists at a later time because it has been added to
> the directory. However when geronimo doesn't find the resource its add its
> name to the 'resourcesNotFound' map in the MultiParentClassLoader.java:571 in
> the 2.2 branch.
> The result of this caching is that we cannot find the resource after it has
> been placed in the direcotry. Would it be possible to configure this
> behaviour, clear the not found cache or is there an other solution to this
> problem ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
