[
https://issues.apache.org/jira/browse/SHIRO-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190102#comment-13190102
]
Les Hazlewood commented on SHIRO-338:
-------------------------------------
Jared can this be resolved now?
> Jenkins builds fail regularly
> -----------------------------
>
> Key: SHIRO-338
> URL: https://issues.apache.org/jira/browse/SHIRO-338
> Project: Shiro
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Jared Bunting
> Assignee: Jared Bunting
> Fix For: 1.2.0
>
>
> The Jenkins builds are failing on regular basis. There seems to be two
> reasons for this:
> # The build runs out of memory. This is a known caveat with the build - it
> can be fixed by adding "-Xmx96m -XX:MaxPermSize=96m" to MAVEN_OPTS.
> # ContainerIntegrationTest in the samples-web module fails to listen on the
> port it attempt to. This is a common issue on build servers as other builds
> or processes may already be occupying the port. This test can be modified to
> select the port dynamically.
> I can fix the second one shortly with a patch to the test class, but I do not
> have access to the Jenkins configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira