Build failed in Jenkins: Nutch-trunk #2030

[Apache Jenkins Server]

See 

--
Started by timer
Building remotely on solaris1 in workspace 

Cleaning local Directory trunk
Checking out http://svn.apache.org/repos/asf/nutch/trunk
ERROR: Failed to check out http://svn.apache.org/repos/asf/nutch/trunk
org.tmatesoft.svn.core.SVNException: svn: OPTIONS /repos/asf/nutch/trunk failed
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:533)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1011)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180)
at 
org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:482)
at 
org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations(SVNBasicClient.java:876)
at 
org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:534)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:901)
at 
hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:84)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2200)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS 
/repos/asf/nutch/trunk failed
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89)
... 26 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: OPTIONS request failed on 
'/repos/asf/nutch/trunk'
svn: timed out waiting for server
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:662)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:292)
... 25 more
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS request failed 
on '/repos/asf/nutch/trunk'
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:660)
... 26 more
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: timed out waiting for 
server
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:412)
... 26 more
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:367)
at java.net.Socket.connect(Socket.java:524)
at 
org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57)
... 1 more
FATAL: null
java.lang.NullPointerException
at java.util.ArrayList.addAll(ArrayList.java:530)
at hudson.scm.SubversionSCM.checkout(Subve

[jira] [Commented] (NUTCH-1481) When using MySQL as storage unicode characters within URLS cause nutch to fail

[Yang Xiao (JIRA)]

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

Yang Xiao commented on NUTCH-1481:
--

It's not right to have unicode in URLs. It's more convenient to use url as id. 
Adding a url normalizer plug-in would be a better solution.

> When using MySQL as storage unicode characters within URLS cause nutch to fail
> --
>
> Key: NUTCH-1481
> URL: https://issues.apache.org/jira/browse/NUTCH-1481
> Project: Nutch
>  Issue Type: Bug
>  Components: crawldb
>Affects Versions: 2.1
> Environment: mysql 5.5.28 on centos
>Reporter: Arni Sumarlidason
>  Labels: database, sql, unicode, utf8
>
> MySQL's (innodb) primary key / unique key is restricted to 767 bytes.. 
> currently the url of a web page is used as a primary key in nutch storage.
> when using latin1 character set on the 'id' column @ length 767 
> bytes/characters; unicode characters in urls cause jdbc to throw an exception,
> java.io.IOException: java.sql.BatchUpdateException: Incorrect string value: 
> '\xE2\x80\x8' for column 'id' at row 1
> when using utf8mb4 character set on the 'id' column @ length 190 characters / 
> 760 bytes to fully support unicode characters; the field length becomes 
> insufficient
> It may be better to use a hash of the url as the primary key instead of the 
> url itself. This would allow urls of any length and full utf8 support.

--
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

[jira] [Commented] (NUTCH-1499) Usage of multiple ipv4 addresses and network cards on fetcher machines

[Sebastian Nagel (JIRA)]

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

Sebastian Nagel commented on NUTCH-1499:


Short and precise patch. However, is there a reason why the problem is not 
solved on hardware or system level, cf. 
[[bonding|http://www.linuxfoundation.org/collaborate/workgroups/networking/bonding]]?

> Usage of multiple ipv4 addresses and network cards on fetcher machines
> --
>
> Key: NUTCH-1499
> URL: https://issues.apache.org/jira/browse/NUTCH-1499
> Project: Nutch
>  Issue Type: New Feature
>  Components: fetcher
>Affects Versions: 1.5.1
>Reporter: Walter Tietze
>Priority: Minor
> Attachments: apache-nutch-1.5.1.NUTCH-1499.patch
>
>
> Adds for the fetcher threads the ability to use multiple configured ipv4 
> addresses.
> On some cluster machines there are several ipv4 addresses configured where 
> each ip address is associated with its own network interface.
> This patch enables to configure the protocol-http and the protocol-httpclient 
>  to use these network interfaces in a round robin style.
> If the feature is enabled, a helper class reads at *startup* the network 
> configuration. In each http network connection the next ip address is taken. 
> This method is synchronized, but this should be no bottleneck for the overall 
> performance of the fetcher threads.
> This feature is tested on our cluster for the protocol-http and the 
> protocol-httpclient protocol.
>  

--
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