You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/11/06 10:47:17 UTC
[jira] [Resolved] (SLING-3232) Sling control port causes trouble in
integration tests
[ https://issues.apache.org/jira/browse/SLING-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-3232.
----------------------------------------
Resolution: Fixed
Fixed in http://svn.apache.org/r1539289
> Sling control port causes trouble in integration tests
> ------------------------------------------------------
>
> Key: SLING-3232
> URL: https://issues.apache.org/jira/browse/SLING-3232
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
>
> Integration tests sometimes fail with
> [ERROR] Failed to start Sling Control Server
> java.net.BindException: Address already in use
> at org.apache.sling.maven.projectsupport.ControlListener.run(ControlListener.java:106)
> at java.lang.Thread.run(Thread.java:662)
> If we actually need that control port in integration tests (and I think we do), it should use a dynamically assigned free port number.
--
This message was sent by Atlassian JIRA
(v6.1#6144)