You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/10/02 12:14:00 UTC
[jira] [Commented] (SLING-7169) FullTextIndexingTest fails after
upgrading to commons.threads 3.2.10
[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187918#comment-16187918 ]
Konrad Windszus commented on SLING-7169:
----------------------------------------
I currently fail to see the relation to commons.threads and cannot reproduce either. For me the ITs run fine with
{code}
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
Maven home: /usr/local/Cellar/maven/3.5.0/libexec
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13", arch: "x86_64", family: "mac"
{code}
Isn't this more likely to be a timing issue? I.e. Oak not having indexed yet the according PDF? Also I don't think anywhere in the {{FullTextIndexingTest}} there is commons.threads being used. Neither for the upload of the PDF nor for the execution of the query ({{o.a.s.lanuchpad.testservices.jcr.FullTextQueryServlet}}), both should IMHO be blocking operations being executed within the request's thread. Can you provide the server logs for the failing test?
> FullTextIndexingTest fails after upgrading to commons.threads 3.2.10
> --------------------------------------------------------------------
>
> Key: SLING-7169
> URL: https://issues.apache.org/jira/browse/SLING-7169
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Reporter: Robert Munteanu
> Assignee: Konrad Windszus
>
> After upgrading the launchpad to commons.threads 3.2.10 the FullTextIndexingTest failed ( [build 1547|https://builds.apache.org/job/sling-launchpad-testing-1.8/1547/] ).
> I also reproduced it once locally.
> [~kwin] - since the commons.threads release is the potential root cause, can you please take a look at the failure and see if it's related?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)