[jira] [Updated] (TIKA-1196) JAX-RS server only responds to queries to/from http://localhost
[
https://issues.apache.org/jira/browse/TIKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rian Stockbower updated TIKA-1196:
--
Attachment: tika-1196.patch
I've attached a patch file that just changes localhost to 0.0.0.0, which allows
users to hit the endpoint using any valid IP or hostname.
Attempting to move the JAX-RS server to CXF 2.7.8 is a little beyond my skill.
JAX-RS server only responds to queries to/from http://localhost
---
Key: TIKA-1196
URL: https://issues.apache.org/jira/browse/TIKA-1196
Project: Tika
Issue Type: Bug
Components: server
Affects Versions: 1.4
Environment: Mac OS X, Windows Server 2008
Reporter: Rian Stockbower
Priority: Minor
Labels: JAXRS, hostname, web-service
Attachments: tika-1196.patch
I'm not sure if this is a problem with the Tika JAX-RS server, or with how it
uses CXF under the hood. Anyway:
I have a large text extraction job (10-15 million documents) that I'm using
the web service for. It would be nice to be able to distribute this
horizontally across multiple nodes to speed up the processing. I had thought
to have a job queue with a couple consumers, farming out PUT requests across
several Tika web service endpoints.
But the JAX-RS web service will only respond to queries made to
{{http://localhost:9998/tika}}.
I can't call {{http://hostname:9998/tika}} -- even if it's still a local
operation.
Here is a list of things I've tried:
* I changed line 89 of TikaServerCLI.java to compute the name of the host at
runtime. No go: the server starts up, and immediately terminates.
* I changed line 89 of TikaServerCLI.java to be a hostname (not a FQDN), and
re-compiled:
** {{mvn compile -rf :tika-server}} compiles successfully. Start up the
server, and it terminates, just like when I tried to compute the hostname at
runtime
** {{mvn install}} from the topmost Tika directory gets the service
responding to both {{http://hostname:9998/tika}} and
{{http://hostname.domain.net:9998/tika}} (Seemed weird, this is why I was
thinking it was further up the chain in CXF?)
In a perfect world:
# The server should respond to any valid calls that make sense:
#* 127.0.0.1
#* localhost
#* hostname
#* host.domain.tld
#* ip_address
# A {{hostname}} invocation parameter could be used to limit what the service
responds to when it's started up. (A very optional, nice-to-have.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TIKA-1196) JAX-RS server only responds to queries to/from http://localhost
[
https://issues.apache.org/jira/browse/TIKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rian Stockbower updated TIKA-1196:
--
Attachment: tika-1196b.patch
Disregard my first patch. This one changes the default behavior to make the
service respond to any valid hostname/ip address. It also adds a CLI parameter
to control the address with instructions for the user on how to restrict usage
to only loopback addresses.
JAX-RS server only responds to queries to/from http://localhost
---
Key: TIKA-1196
URL: https://issues.apache.org/jira/browse/TIKA-1196
Project: Tika
Issue Type: Bug
Components: server
Affects Versions: 1.4
Environment: Mac OS X, Windows Server 2008
Reporter: Rian Stockbower
Priority: Minor
Labels: JAXRS, hostname, web-service
Attachments: tika-1196.patch, tika-1196b.patch
I'm not sure if this is a problem with the Tika JAX-RS server, or with how it
uses CXF under the hood. Anyway:
I have a large text extraction job (10-15 million documents) that I'm using
the web service for. It would be nice to be able to distribute this
horizontally across multiple nodes to speed up the processing. I had thought
to have a job queue with a couple consumers, farming out PUT requests across
several Tika web service endpoints.
But the JAX-RS web service will only respond to queries made to
{{http://localhost:9998/tika}}.
I can't call {{http://hostname:9998/tika}} -- even if it's still a local
operation.
Here is a list of things I've tried:
* I changed line 89 of TikaServerCLI.java to compute the name of the host at
runtime. No go: the server starts up, and immediately terminates.
* I changed line 89 of TikaServerCLI.java to be a hostname (not a FQDN), and
re-compiled:
** {{mvn compile -rf :tika-server}} compiles successfully. Start up the
server, and it terminates, just like when I tried to compute the hostname at
runtime
** {{mvn install}} from the topmost Tika directory gets the service
responding to both {{http://hostname:9998/tika}} and
{{http://hostname.domain.net:9998/tika}} (Seemed weird, this is why I was
thinking it was further up the chain in CXF?)
In a perfect world:
# The server should respond to any valid calls that make sense:
#* 127.0.0.1
#* localhost
#* hostname
#* host.domain.tld
#* ip_address
# A {{hostname}} invocation parameter could be used to limit what the service
responds to when it's started up. (A very optional, nice-to-have.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TIKA-1196) JAX-RS server only responds to queries to/from http://localhost
[
https://issues.apache.org/jira/browse/TIKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rian Stockbower updated TIKA-1196:
--
Attachment: tika-1196c.patch
Patch C fixes a careless error where the default port was always used,
regardless of what was specified by the user.
JAX-RS server only responds to queries to/from http://localhost
---
Key: TIKA-1196
URL: https://issues.apache.org/jira/browse/TIKA-1196
Project: Tika
Issue Type: Bug
Components: server
Affects Versions: 1.4
Environment: Mac OS X, Windows Server 2008
Reporter: Rian Stockbower
Priority: Minor
Labels: JAXRS, hostname, web-service
Attachments: tika-1196.patch, tika-1196b.patch, tika-1196c.patch
I'm not sure if this is a problem with the Tika JAX-RS server, or with how it
uses CXF under the hood. Anyway:
I have a large text extraction job (10-15 million documents) that I'm using
the web service for. It would be nice to be able to distribute this
horizontally across multiple nodes to speed up the processing. I had thought
to have a job queue with a couple consumers, farming out PUT requests across
several Tika web service endpoints.
But the JAX-RS web service will only respond to queries made to
{{http://localhost:9998/tika}}.
I can't call {{http://hostname:9998/tika}} -- even if it's still a local
operation.
Here is a list of things I've tried:
* I changed line 89 of TikaServerCLI.java to compute the name of the host at
runtime. No go: the server starts up, and immediately terminates.
* I changed line 89 of TikaServerCLI.java to be a hostname (not a FQDN), and
re-compiled:
** {{mvn compile -rf :tika-server}} compiles successfully. Start up the
server, and it terminates, just like when I tried to compute the hostname at
runtime
** {{mvn install}} from the topmost Tika directory gets the service
responding to both {{http://hostname:9998/tika}} and
{{http://hostname.domain.net:9998/tika}} (Seemed weird, this is why I was
thinking it was further up the chain in CXF?)
In a perfect world:
# The server should respond to any valid calls that make sense:
#* 127.0.0.1
#* localhost
#* hostname
#* host.domain.tld
#* ip_address
# A {{hostname}} invocation parameter could be used to limit what the service
responds to when it's started up. (A very optional, nice-to-have.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (TIKA-1196) JAX-RS server only responds to queries to/from http://localhost
[
https://issues.apache.org/jira/browse/TIKA-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rian Stockbower updated TIKA-1196:
--
Description:
I'm not sure if this is a problem with the Tika JAX-RS server, or with how it
uses CXF under the hood. Anyway:
I have a large text extraction job (10-15 million documents) that I'm using the
web service for. It would be nice to be able to distribute this horizontally
across multiple nodes to speed up the processing. I had thought to have a job
queue with a couple consumers, farming out PUT requests across several Tika web
service endpoints.
But the JAX-RS web service will only respond to queries made to
{{http://localhost:9998/tika}}.
I can't call {{http://hostname:9998/tika}} -- even if it's still a local
operation.
Here is a list of things I've tried:
* I changed line 89 of TikaServerCLI.java to compute the name of the host at
runtime. No go: the server starts up, and immediately terminates.
* I changed line 89 of TikaServerCLI.java to be a hostname (not a FQDN), and
re-compiled:
** {{mvn compile -rf :tika-server}} compiles successfully. Start up the server,
and it terminates, just like when I tried to compute the hostname at runtime
** {{mvn install}} from the topmost Tika directory gets the service responding
to both {{http://hostname:9998/tika}} and
{{http://hostname.domain.net:9998/tika}} (Seemed weird, this is why I was
thinking it was further up the chain in CXF?)
In a perfect world:
# The server should respond to any valid calls that make sense:
#* 127.0.0.1
#* localhost
#* hostname
#* host.domain.tld
#* ip_address
# A {{hostname}} invocation parameter could be used to limit what the service
responds to when it's started up. (A very optional, nice-to-have.)
was:
I'm not sure if this is a problem with the Tika JAX-RS server, or with how it
uses CXF under the hood. Anyway:
I have a large text extraction job (10-15 million documents) that I'm using the
web service for. It would be nice to be able to distribute this horizontally
across multiple nodes to speed up the processing. I had thought to have a job
queue with a couple consumers, farming out PUT requests across several Tika web
service endpoints.
But the JAX-RS web service will only respond to queries made to
{{http://localhost:9998/tika}}.
I can't call {{http://hostname:9998/tika}} -- even if it's still a local
operation.
Here is a list of things I've tried:
* I changed line 89 of TikaServerCLI.java to compute the name of the host at
runtime. No go: the server starts up, and immediately terminates.
* I changed line 89 of TikaServerCLI.java to be a hostname (not a FQDN), and
re-compiled:
** {{mvn compile -rf :tika-server}} compiles successfully. Start up the server,
and it terminates, just like when I tried to compute the hostname at runtime
** {{mvn install}} from the topmost Tika directory gets the service responding
to both {{http://hostname:9998/tika}} and
{{http://hostname.domain.net:9998/tika}} (Seemed weird, this is why I was
thinking it was further up the chain in CXF?)
In a perfect world:
# The server should respond to any valid calls that make sense:
#* 127.0.0.1
#* localhost
#* hostname
#* host.domain.tld
#* ip_address
# An hostname invocation parameter could be used to limit how what the service
responds to when it's started up. (A very optional, nice-to-have.)
JAX-RS server only responds to queries to/from http://localhost
---
Key: TIKA-1196
URL: https://issues.apache.org/jira/browse/TIKA-1196
Project: Tika
Issue Type: Bug
Components: server
Affects Versions: 1.4
Environment: Mac OS X, Windows Server 2008
Reporter: Rian Stockbower
Priority: Minor
Labels: JAXRS, hostname, web-service
I'm not sure if this is a problem with the Tika JAX-RS server, or with how it
uses CXF under the hood. Anyway:
I have a large text extraction job (10-15 million documents) that I'm using
the web service for. It would be nice to be able to distribute this
horizontally across multiple nodes to speed up the processing. I had thought
to have a job queue with a couple consumers, farming out PUT requests across
several Tika web service endpoints.
But the JAX-RS web service will only respond to queries made to
{{http://localhost:9998/tika}}.
I can't call {{http://hostname:9998/tika}} -- even if it's still a local
operation.
Here is a list of things I've tried:
* I changed line 89 of TikaServerCLI.java to compute the name of the host at
runtime. No go: the server starts up, and immediately terminates.
* I changed line 89 of TikaServerCLI.java to be a hostname (not a FQDN), and
re-compiled:
** {{mvn compile -rf :tika-server}} compiles successfully. Start up the
server, and it terminates, just like when
