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

Mark Miller commented on SOLR-4006:
-----------------------------------

The good news is, I can duplicate this on my FreeBSD VM. The bad news is, I 
don't have a fix yet.

I suspect the fails started happening because of the switch to using the nio 
jetty connector. I don't think it's acceptable that I have to avoid using that 
(plus it makes one test randomly take 3 minutes rather than 3 seconds if I 
don't use it), but I'm not sure how to get around this yet.

If the hurricane does not eat me up, I'll continue trying to overcome this.
                
> Many tests on Apache Jenkins are failing with lingering threads.
> ----------------------------------------------------------------
>
>                 Key: SOLR-4006
>                 URL: https://issues.apache.org/jira/browse/SOLR-4006
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>
> I think I've tracked this down to being related to the black hole.
> It seems to be a recovery call to a server that is down or something - it's 
> hanging in the connect method even though we are using a connect timeout.
> {noformat}
> Thread[RecoveryThread,5,TGRP-SyncSliceTest]
> java.net.PlainSocketImpl.socketConnect(Native Method)
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327)
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193)
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180)
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
> java.net.Socket.connect(Socket.java:546)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to