[
https://issues.apache.org/jira/browse/TIKA-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032252#comment-18032252
]
Tim Allison commented on TIKA-4512:
-----------------------------------
I think there's a cross-process race condition when unpacking the plugins.zip.
I'm getting non-deterministic failures in the tika-app tests when running
{{{}mvn clean install -am -pl :tika-app{}}}, however, if I don't run clean, I
get consistent tests passing.
When there's a failure, I see this:
{noformat}
INFO [main] 16:55:06,493 org.pf4j.DefaultPluginStatusProvider Enabled plugins:
[]INFO [main] 16:55:06,494 org.pf4j.DefaultPluginStatusProvider Disabled
plugins: []INFO [main] 16:55:06,497 org.pf4j.DefaultPluginManager PF4J version
3.13.0 in 'deployment' modeINFO [main] 16:55:06,515
org.pf4j.DefaultPluginStatusProvider Enabled plugins: []INFO [main]
16:55:06,517 org.pf4j.DefaultPluginStatusProvider Disabled plugins: []INFO
[main] 16:55:06,522 org.pf4j.DefaultPluginManager PF4J version 3.13.0 in
'deployment' modeERROR [main] 16:55:06,529
org.pf4j.CompoundPluginDescriptorFinder Cannot find the manifest
pathorg.pf4j.PluginRuntimeException: Cannot find the manifest path at
org.pf4j.ManifestPluginDescriptorFinder.readManifestFromDirectory(ManifestPluginDescriptorFinder.java:142)
at
org.pf4j.ManifestPluginDescriptorFinder.readManifest(ManifestPluginDescriptorFinder.java:72)
at
org.pf4j.ManifestPluginDescriptorFinder.find(ManifestPluginDescriptorFinder.java:58)
at
org.pf4j.CompoundPluginDescriptorFinder.find(CompoundPluginDescriptorFinder.java:65)
at
org.pf4j.AbstractPluginManager.loadPluginFromPath(AbstractPluginManager.java:894)
at
org.pf4j.DefaultPluginManager.loadPluginFromPath(DefaultPluginManager.java:139)
at
org.pf4j.AbstractPluginManager.loadPlugins(AbstractPluginManager.java:246) at
org.apache.tika.pipes.core.fetcher.FetcherManager.load(FetcherManager.java:65)
at
org.apache.tika.pipes.core.fetcher.FetcherManager.load(FetcherManager.java:53)
at
org.apache.tika.pipes.core.PipesServer.initializeResources(PipesServer.java:828)
at
org.apache.tika.pipes.core.PipesServer.processRequests(PipesServer.java:221) at
org.apache.tika.pipes.core.PipesServer.main(PipesServer.java:187)ERROR [main]
16:55:06,535 org.pf4j.AbstractPluginManager Cannot load plugin
'/.../tika-main/tika-app/target/plugins/tika-fetcher-file-system-4.0.0-SNAPSHOT'org.pf4j.PluginRuntimeException:
No PluginDescriptorFinder for plugin
'/.../tika-main/tika-app/target/plugins/tika-fetcher-file-system-4.0.0-SNAPSHOT'
at
org.pf4j.CompoundPluginDescriptorFinder.find(CompoundPluginDescriptorFinder.java:84)
at
org.pf4j.AbstractPluginManager.loadPluginFromPath(AbstractPluginManager.java:894)
at
org.pf4j.DefaultPluginManager.loadPluginFromPath(DefaultPluginManager.java:139)
at
org.pf4j.AbstractPluginManager.loadPlugins(AbstractPluginManager.java:246) at
org.apache.tika.pipes.core.fetcher.FetcherManager.load(FetcherManager.java:65)
at
org.apache.tika.pipes.core.fetcher.FetcherManager.load(FetcherManager.java:53)
at
org.apache.tika.pipes.core.PipesServer.initializeResources(PipesServer.java:828)
at
org.apache.tika.pipes.core.PipesServer.processRequests(PipesServer.java:221) at
org.apache.tika.pipes.core.PipesServer.main(PipesServer.java:187)
{noformat}
> Experiment with pf4j for tika-pipes
> -----------------------------------
>
> Key: TIKA-4512
> URL: https://issues.apache.org/jira/browse/TIKA-4512
> Project: Tika
> Issue Type: Sub-task
> Reporter: Tim Allison
> Priority: Major
>
> This is proof of concept work based on [~ndipiazza] 's TIKA-4272-docker
> branch.
> I really like a lot of that work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
