[
https://issues.apache.org/jira/browse/TIKA-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613188#comment-16613188
]
Nick Burch commented on TIKA-2558:
----------------------------------
Based on
https://stackoverflow.com/questions/35842/how-can-a-java-program-get-its-own-process-id
we can't implement this in a safe/generic way until we bump the minimum Java
version to Java 9 (we've only fairly recently moved to Java 8)
I'm also not sure if there are security implications of having this on by
default? Or if we should add a flag to enable it like we do for other
potentially dangerous things?
The Fork Parser stuff might make things interesting too, as with that you'd
actually have multiple java instances and hence interesting pids.
Either way, will need to be parked for a bit until we move to a minimum of Java
9
> Add a new pid api to Tika
> -------------------------
>
> Key: TIKA-2558
> URL: https://issues.apache.org/jira/browse/TIKA-2558
> Project: Tika
> Issue Type: New Feature
> Components: general
> Affects Versions: 1.17
> Environment: All platforms on which Tika can run.
> Reporter: Stefan Sveen
> Priority: Minor
> Fix For: 2.0.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Using Tika with Mono on Windows, Linux and Mac I miss a simple and
> OS-independent way to get the Process ID of a running Tika service.
> Therefore, I suggest that the following API is added to Tika:
> *GET* _[/pid|http://localhost:16200/version]_
> Class: org.apache.tika.server.resource.TikaPID (guessing that this would be
> the class)
> Method: getPID
> Produces: text/plain
> The output would be the integer value (as a string) of the PID
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
