Thank you for your patience! More documentation is on the way.

Best,
   Tim

On Wed, Jun 16, 2021 at 6:03 PM Cristian Zamfir <[email protected]>
wrote:

> Thanks Tim, you're absolutely right, this works. I forgot about the change
> to pass arguments to the forked process despite using it recently.
>
>
>
> On Wed, Jun 16, 2021 at 5:49 PM Tim Allison <[email protected]> wrote:
>
>> Are you configuring that via tikaconfig.xml?
>>
>> <properties>
>>   <server>
>>     <params>
>>       <port>9999</port>
>>       <taskTimeoutMillis>120000</taskTimeoutMillis>
>>       <enableUnsecureFeatures>true</enableUnsecureFeatures>
>>       <forkedJvmArgs>
>>         <arg>-Xmx2g</arg>
>>         <arg>-Dlog4j.configurationFile=logging.xml</arg>
>> ...
>>
>> On Wed, Jun 16, 2021 at 10:17 AM Cristian Zamfir <[email protected]>
>> wrote:
>> >
>> > Got it, that works, however that only works for the parent process. How
>> can I pass it to the spawned processes? I tried TIKA_CHILD_JVM_OPTS but it
>> seems to be ignored.
>> >
>> >
>> > On Wed, Jun 16, 2021 at 3:30 PM Tim Allison <[email protected]>
>> wrote:
>> >>
>> >> Try:
>> >>
>> >> java -Dlog4j.configurationFile=logging.xml -jar
>> >> tika-server-standard-2.0.0-SNAPSHOT.jar
>> >>
>> >> I'm getting errors with *-v2.xml, but the above at least loads
>> >> correctly for logging.xml.
>> >>
>> >> On Wed, Jun 16, 2021 at 9:06 AM Cristian Zamfir <[email protected]>
>> wrote:
>> >> >
>> >> > Yes, certainly.Please find two versions attached. I get the same
>> error with both. The first one should be the default Tika server config.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > > On 16 Jun 2021, at 14:56, Tim Allison <[email protected]> wrote:
>> >> > >
>> >> > > Is that a log4j2 formatted xml file? Are you able to share it?
>> >> > >
>> >> > > On Wed, Jun 16, 2021 at 8:34 AM Cristian Zamfir <
>> [email protected]> wrote:
>> >> > > Hi,
>> >> > >
>> >> > > I am hitting this error when trying to reconfigure logging for
>> Tika server using the latest 2.0 snapshot. The actual logging configuration
>> does not seem to matter, for instance I used the default configuration and
>> ran this command:
>> >> > >
>> >> > > > java -Dlog4j.configuration=file:./logging.xml -jar
>> ./tika-server-standard-2.0.0-SNAPSHOT.jar
>> >> > > ERROR StatusLogger Reconfiguration failed: No configuration found
>> for '277050dc' at 'null' in 'null'
>> >> > >
>> >> > > The changes in the logging configuration are ignored after this
>> error. I confirmed that this used to work in 1.26.
>> >> > >
>> >> > > Thanks,
>> >> > > Cristi
>>
>

Reply via email to