[ 
https://issues.apache.org/jira/browse/TIKA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087768#comment-14087768
 ] 

Rob Tulloh commented on TIKA-1371:
----------------------------------

How do we make this work with the tika-server jar? We pulled build 146 and 
tried:

java -jar tika-server-1.7-20140806.080824-51.jar --help
Aug 06, 2014 10:05:48 AM org.apache.tika.server.TikaServerCli main
INFO: Starting Apache Tika 1.7-SNAPSHOT server
usage: tikaserver
 -?,--help         this help message
 -h,--host <arg>   host name (default = localhost)
 -p,--port <arg>   listen port (default = 9998)


java -jar tika-server-1.7-20140806.080824-51.jar -l -p 9998

With this result:

java -jar tika-server-1.7-20140806.080824-51.jar -l -p 9998
Aug 06, 2014 10:06:53 AM org.apache.tika.server.TikaServerCli main
INFO: Starting Apache Tika 1.7-SNAPSHOT server
Aug 06, 2014 10:06:53 AM org.apache.tika.server.TikaServerCli main
SEVERE: Can't start
org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -l
        at org.apache.commons.cli.Parser.processOption(Parser.java:363)
        at org.apache.commons.cli.Parser.parse(Parser.java:199)
        at org.apache.commons.cli.Parser.parse(Parser.java:85)
        at org.apache.tika.server.TikaServerCli.main(TikaServerCli.java:60)



> passing parameters via URL no longer works (regression)
> -------------------------------------------------------
>
>                 Key: TIKA-1371
>                 URL: https://issues.apache.org/jira/browse/TIKA-1371
>             Project: Tika
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 1.5
>            Reporter: Rob Tulloh
>
> In Tika 1.1 and 1.2, it was possible to add some values to the URL that get 
> logged like this:
> http://localhost:9998/tika/GUID/FILENAME
> This was very useful for correlating between client and server in a 
> distributed compute environment. In 1.5 and in the nighty builds (for 1.6), 
> this feature no longer works. Not having this makes it very difficult to 
> troubleshoot problems with document processing in a distributed environment. 
> Please add back this feature so that operations and development teams can 
> more easily figure out which tika instance is processing which document and 
> what the result of the processing resulted in.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to