[
https://issues.apache.org/jira/browse/SOLR-6991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289194#comment-14289194
]
Uwe Schindler commented on SOLR-6991:
-------------------------------------
Hoss: One idea to fix the whole thing could be:
In Solr's main startup method (before any threads or whatever are spawned), I
would suggest the main() method of the startup class (do we have that now, or
do we still use jetty's start.jar) to do something like suggested here:
[https://issues.apache.org/jira/browse/TIKA-1526?focusedCommentId=14289182&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14289182]
It is important to do this early and at a time when the global locale setting
cannot affect other stuff running in the JVM. So definitely not in the webapp
itsself (thats too late):
- check for locale, we do this like that: {{new
Locale("tr").getLanguage().equals(Locale.getDefault().getLanguage())}} (it is
important to do the check like this, because otherwise its not guaranteed that
it really works, especially in newer java versions!!!)
- if its such a locale, switch to Locale.ROOT (save original) in a
single-threaded environment (this is why it should be in main launcher)
- execute a fake UNIX command, like /bin/true. You can also execute some
non-existing bullshit that just fails. The call is just there to statically
initalize the broken UnixProcess class. Once it is initialized correctly it
works
- switch back to saved locale
> Update to Apache TIKA 1.7
> -------------------------
>
> Key: SOLR-6991
> URL: https://issues.apache.org/jira/browse/SOLR-6991
> Project: Solr
> Issue Type: Improvement
> Components: contrib - Solr Cell (Tika extraction)
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: 5.0, Trunk, 5.1
>
> Attachments: SOLR-6991-forkfix.patch, SOLR-6991-forkfix.patch,
> SOLR-6991.patch, SOLR-6991.patch
>
>
> Apache TIKA 1.7 was released:
> [https://dist.apache.org/repos/dist/release/tika/CHANGES-1.7.txt]
> This is more or less a dependency update, so replacements. Not sure if we
> should do this for 5.0. In 5.0 we currently have the previous version, which
> was not yet released with Solr. If we now bring this into 5.0, we wouldn't
> have a new release 2 times. I can change the stuff this evening and let it
> bake in 5.x, so maybe we backport this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
