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

Karl Wright commented on CONNECTORS-1180:
-----------------------------------------

Thanks.

With this simple configuration, it does cut down on the possibilities.
FWIW, as you can see by the tickets, there were occasional transactional 
integrity problems with Postgresql from 9.2 back.  8.4 would certainly be in 
that range.  While nobody has reported seeing this problem on 9.3 or above, 
that does not guarantee that it has been fixed.

I can't exactly open a Postgresql ticket against something as old as 8.4, 
though, so you may want to consider upgrading in case we can reproduce it on a 
modern version, and you and I have the fortitude to follow up.  Dealing with 
the Postgres people has been a bit challenging in the past because they tend to 
demand a reproducible test case along with the ticket, and even when you 
provide one there's often not a lot of urgency to fix it.  Still it is better 
than dealing with the Derby folks, who have had far more extensive problems 
that they've simply ignored, even when I provided them a whole branch full of 
test cases.

Hopefully this will not degenerate into that kind of situation.


> Jobs abort with "Error: Unexpected jobqueue status - record id 1427880204801, 
> expecting active status, saw 4"
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-1180
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1180
>             Project: ManifoldCF
>          Issue Type: Bug
>    Affects Versions: ManifoldCF 2.0.2
>         Environment: Using the Windows Share repository, Solr output 
> connectors.
> Using Zookeeper.
>            Reporter: Andreas Baumann
>            Assignee: Karl Wright
>
> Jobs abort out of the blue with
> "Error: Unexpected jobqueue status - record id 1427880204801, expecting 
> active status, saw 4"
> I had the impression that I could force it by clicking in the admin interface
> and for instance when I pressed refresh in "Status and Job Management".



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

Reply via email to