You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Siveton (JIRA)" <ji...@codehaus.org> on 2009/07/14 13:20:23 UTC
[jira] Commented: (MJAVADOC-238) No timeout set for URLConnection
which can cause build to get stuck
[ http://jira.codehaus.org/browse/MJAVADOC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183501#action_183501 ]
Vincent Siveton commented on MJAVADOC-238:
------------------------------------------
Fixed in [r793854|http://svn.apache.org/viewvc?rev=793854&view=rev], snapshot deployed
Please test it so I could close it.
> No timeout set for URLConnection which can cause build to get stuck
> -------------------------------------------------------------------
>
> Key: MJAVADOC-238
> URL: http://jira.codehaus.org/browse/MJAVADOC-238
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Bugittaa Pahasti
>
> I encountered a release build getting stuck. Stack trace revealed that the culprit was an infinite default timeout in URLConnection.
> [INFO] at java.net.URL.openStream(URL.java:1007)
> [INFO] at org.apache.maven.plugin.javadoc.JavadocUtil.fetchURL(JavadocUtil.java:742)
> [INFO] at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addLinkArguments(AbstractJavadocMojo.java:2982)
> [INFO] at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addStandardDocletOptions(AbstractJavadocMojo.java:3667)
> [INFO] at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1548)
> [INFO] at org.apache.maven.plugin.javadoc.JavadocJar.execute(JavadocJar.java:182)
> [INFO] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> The simple fix is to call setConnectTimeout and setReadTimeout with some sensible default value (jdk 1.5 methods, so might need to use reflection to preseve jdk 1.4 compatibility).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira