tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TIKA-827) ForkServer fails to report issues if an exception is not properly serializable
Date Sat, 30 Jun 2012 15:18:44 GMT

     [ https://issues.apache.org/jira/browse/TIKA-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting resolved TIKA-827.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2

Resolving this as fixed based on Nick's changes.
                
> ForkServer fails to report issues if an exception is not properly serializable
> ------------------------------------------------------------------------------
>
>                 Key: TIKA-827
>                 URL: https://issues.apache.org/jira/browse/TIKA-827
>             Project: Tika
>          Issue Type: Bug
>            Reporter: Jerome Lacoste
>             Fix For: 1.2
>
>         Attachments: 0002-TIKA-827-try-to-report-something-if-the-exception-is.patch
>
>
> {code}
>         try {
>             method.invoke(object, args);
>             output.write(DONE);
>         } catch (InvocationTargetException e) {
>             output.write(ERROR);
>             // warning if an exception isn't really serializable, this can fail.
>             /**
>             File tempFile = File.createTempFile("tika", ".trace");
>             PrintWriter pw = new PrintWriter(tempFile);
>             e.printStackTrace(pw);
>             pw.close();
>             e = new Exception(tempFile.getAbsolutePath());
>             */
>             ForkObjectInputStream.sendObject(e, output);
>         }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message