C:\jdk1.5.0_12\jre

Set your JAVA_HOME to a JDK?

On Wed, Apr 20, 2011 at 10:42 AM, Heck, Gus (Patrick)
<[email protected]> wrote:
> Hi Folks,
>
> I didn't find anything when I searched the site/lists for
> "ForkedParserTest" wanted to check if anyone can spot something silly
> before I file a bug.
>
> In the following environment:
>
> Microsoft Windows XP [Version 5.1.2600]
> Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500)
> Java version: 1.5.0_12, vendor: Sun Microsystems Inc.
> Java home: C:\jdk1.5.0_12\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
>
> running under cygwin bash shell I did:
>
> svn checkout http://svn.apache.org/repos/asf/tika/tags/0.9 tika-site
> cd tika-site
> mvn package
>
> I expected that this would create distributable jar files. Next I will
> be attempting to rip out PDF support to get rid of the crypto
> export/import issue for our offshore workers. So my goal is to build a
> jar they can use over there (in fact I don't know for sure they can't
> use the crypto, but IANAL and we need to make progress while the lawyers
> try to figure that out).
>
> Unfortunately the result is:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Tika parent ................................ SUCCESS
> [0.579s]
> [INFO] Apache Tika core .................................. FAILURE
> [39.484s]
> [INFO] Apache Tika parsers ............................... SKIPPED
> [INFO] Apache Tika application ........................... SKIPPED
> [INFO] Apache Tika OSGi bundle ........................... SKIPPED
> [INFO] Apache Tika ....................................... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
>
> In the tests I see:
>
> org.apache.tika.exception.TikaException: Failed to communicate with a
> forked parser process. The process has most likely crashed due to some
> error like running out of memory. A new process will be started for the
> next parsing request.
>        at org.apache.tika.fork.ForkParser.parse(ForkParser.java:120)
>        at
> org.apache.tika.fork.ForkParserTest$1.run(ForkParserTest.java:80)
> Caused by: java.io.IOException: The pipe has been ended
>        at java.io.FileOutputStream.writeBytes(Native Method)
>        at java.io.FileOutputStream.write(FileOutputStream.java:260)
>        at
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
>        at
> java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
>        at java.io.DataOutputStream.flush(DataOutputStream.java:106)
>        at
> org.apache.tika.fork.ClassLoaderResource.process(ClassLoaderResource.jav
> a:65)
>        at
> org.apache.tika.fork.ForkClient.waitForResponse(ForkClient.java:174)
>        at
> org.apache.tika.fork.ForkClient.sendObject(ForkClient.java:137)
>        at org.apache.tika.fork.ForkClient.call(ForkClient.java:108)
>        at org.apache.tika.fork.ForkParser.parse(ForkParser.java:117)
>        ... 1 more
>
> Is this a known issue? Is there set-up with maven I've not done? I'm a
> long time Ant person and not particularly good with maven, but I think
> the idea in maven is that one is supposed be able to do it as easy as
> above. (properly constructed Ant builds are similarly easy and don't
> hide stuff in auto-magic, but never-mind that :) *grumble* ).
>
> -Gus
>
>
> This e-mail and any attachments are intended only for use by the
> addressee(s) named herein and may contain legally privileged and/or
> confidential information. If you are not the intended recipient of
> this e-mail, you are hereby notified any dissemination,
> distribution or copying of this email, and any attachments thereto,
> is strictly prohibited. If you receive this email in error please
> immediately notify the sender and permanently delete the original
> copy and any copy of any e-mail, and any printout thereof.
>

Reply via email to