[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13840086#comment-13840086
]
Rian Stockbower commented on TIKA-1196:
---
Sounds reasonable. Thanks, Sergey.
-Rian
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=13839706#comment-13839706
]
Rian Stockbower commented on TIKA-1196:
---
Radio silence from the Tika mailing list. Can we get my latest patch rolled in?
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=13825370#comment-13825370
]
Rian Stockbower commented on TIKA-1196:
---
Those are more or less my thoughts. I'll solicit comments from the Tika users
mailing list.
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=13825332#comment-13825332
]
Rian Stockbower commented on TIKA-1196:
---
I can put it back to localhost, but I'm not sure _why_ that's desirable. (Other
than that's the way it was.) What's the reasoning behind having it limited to
loopback addresses by default? This is not the behavior I would expect as a
user. As a user, I would expect it to work like a web service: it does
something when I make a semantically valid call to it.
>From an operational perspective, there's some added complexity as well: when I
>deploy this to N nodes, I'll have to have my invocation script compute the
>local hostname before launching the service. Admittedly this is a small
>problem, but I don't see why it needs to be a problem at all.
What am I missing here?
> 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:
--
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:
--
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] [Commented] (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:comment-tabpanel&focusedCommentId=13824982#comment-13824982
]
Rian Stockbower commented on TIKA-1196:
---
It seems weird to restrict access to the endpoint to only loopback addresses.
That said, I'm working on something a little more interesting/robust.
> 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-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] [Commented] (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:comment-tabpanel&focusedCommentId=13824956#comment-13824956
]
Rian Stockbower commented on TIKA-1196:
---
That worked, Sergey. Changing localhost to 0.0.0.0 now lets me hit the service
using any valid address.
> 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 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] [Commented] (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:comment-tabpanel&focusedCommentId=13824939#comment-13824939
]
Rian Stockbower commented on TIKA-1196:
---
Unfortunately that didn't work. I've just emailed the CXF user list.
> 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 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] [Commented] (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:comment-tabpanel&focusedCommentId=13824538#comment-13824538
]
Rian Stockbower commented on TIKA-1196:
---
I'm new to this, but it looks like there's no way to call
JAXRSServerFactoryBean.setAddress with anything except a literal string. There
doesn't seem to be a way to give it a list of valid hostnames.
http://cxf.apache.org/javadoc/latest/org/apache/cxf/endpoint/AbstractEndpointFactory.html
> 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 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, an
[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:
--
Summary: JAX-RS server only responds to queries to/from http://localhost
(was: JAX-RS server only responds to queries to/from localhost)
> 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 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.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (TIKA-1196) JAX-RS server only responds to queries to/from localhost
Rian Stockbower created TIKA-1196:
-
Summary: JAX-RS server only responds to queries to/from 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
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.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
