You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2015/05/09 10:18:59 UTC

[jira] [Commented] (CONNECTORS-1198) SearchBlox connector session management is completely broken

    [ https://issues.apache.org/jira/browse/CONNECTORS-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536291#comment-14536291 ] 

Karl Wright commented on CONNECTORS-1198:
-----------------------------------------

To fix this problem, parameters which are currently specification parameters must instead become connection parameters.  That's going to necessarily break backwards compatibility, but since the connector is broken beyond repair right now anyway, this should not be a problem.

Another issue is that we have people in the field attempting to work with the connector right now.  I will therefore need to attach a patch to this ticket to deal with the short-term issues first.


> SearchBlox connector session management is completely broken
> ------------------------------------------------------------
>
>                 Key: CONNECTORS-1198
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1198
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: SearchBlox connector
>    Affects Versions: ManifoldCF 1.9, ManifoldCF 2.1
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Critical
>             Fix For: ManifoldCF 1.10, ManifoldCF 2.2
>
>
> The SearchBlox connector's session management attempts to create a global pool with pool parameters etc on a per-job basis.  This does not work properly with ManifoldCF's connection pools and causes NullPointerExceptions when documents are deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)