I have a few transforms that I need to do, but I turned set the cache
lifetime very high. I'm just trying to rectify error messages that pop up.
If it's something that I can ignore, then that's OK, I just wanted to be
sure.
Thanks!
-- Chris
On Thu, May 1, 2014 at 10:32 PM, Alexandre Rafalovit
I think the key message here is:
"simplistic XSLT caching mechanism is not appropriate for high load scenarios".
As in, maybe this is not really a production-level component. One
exception is given and it is not just lifetime, it's also a
single-transform.
Are you satisfying both of those conditi
On 5/1/2014 7:30 PM, Christopher Gross wrote:
> The message implies that there is a better way of having XSLT
> transformations. Is that the case, or is there just this perpetual warning
> for normal operations?
When I was using XSLT, I got a warning for every core, even though I had
a cached lif
The message implies that there is a better way of having XSLT
transformations. Is that the case, or is there just this perpetual warning
for normal operations?
-- Chris
On Thu, May 1, 2014 at 5:08 PM, Ahmet Arslan wrote:
> Hi Chris,
>
> Looking at source code reveals that warning message prin
Hi Chris,
Looking at source code reveals that warning message printed always. Independent
of xsltCacheLifetimeSeconds value.
/** singleton */
private TransformerProvider() {
// tell'em: currently, we only cache the last used XSLT transform, and
blindly recompile it
// once cacheLif
I get this warning when Solr (4.7.2) Starts:
WARN org.apache.solr.util.xslt.TransformerProvider â The
TransformerProvider's simplistic XSLT caching mechanism is not appropriate
for high load scenarios, unless a single XSLT transform is used and
xsltCacheLifetimeSeconds is set to a sufficiently hi
