manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CONNECTORS-1524) Documentum Connector fails with NullPointerException under OpenJDK 10
Date Fri, 10 Aug 2018 15:32:00 GMT
James Thomas created CONNECTORS-1524:
----------------------------------------

             Summary: Documentum Connector fails with NullPointerException under OpenJDK 10
                 Key: CONNECTORS-1524
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1524
             Project: ManifoldCF
          Issue Type: Bug
          Components: Documentum connector
    Affects Versions: ManifoldCF 2.10
            Reporter: James Thomas
         Attachments: 500_server_error.txt

I am running ManifoldCF 2.10 patched for issues 1512 and 1517.

I recently upgraded Java to 10.0.2 (for another server on the same machine) and find that
when I try to create jobs using the Documentum connector, clicking on (e.g.) the Paths tab
will give this error dialog:
{code:java}
HTTP ERROR 500
Problem accessing /mcf-crawler-ui/execute.jsp. Reason:
    Server Error
Caused by:

org.apache.jasper.JasperException: An exception occurred processing JSP page /execute.jsp
at line 1542

1539:           {
1540:             threadContext.save("JobObject",job);
1541: %>
1542:             <jsp:forward page="editjob.jsp"/>
1543: <%
1544:           }
1545:           else if (op.equals("Save")){code}
There's a lot of stack trace (which I'll attach) but it includes some ManifoldCF calls:

 
{code:java}
Caused by: java.lang.RuntimeException: Unexpected exception type: java.lang.NullPointerException:
null
    at org.apache.manifoldcf.crawler.connectors.DCTM.DCTM$GetSessionThread.finishUp(DCTM.java:117)
    at org.apache.manifoldcf.crawler.connectors.DCTM.DCTM.getSession(DCTM.java:173)
...
Caused by: java.lang.NullPointerException
    at com.documentum.fc.client.impl.docbase.DocbaseDateFormat.getSeparator(DocbaseDateFormat.java:119)
    at ...
{code}
If I revert to OpenJDK 1.8.0_171 (the version I upgraded from) the issue is not seen.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message