On Fri, 01 Nov 2013 08:14:31 -0200, Ulrich Stärk <[email protected]> wrote:
As the log output says, tests run on port 4444. Also these are the only
open ports atm:
Port 4444 is used by Selenium itself AFAIK. The Tapestry test webapps bind
to 9090.
root@tapbuild:~# lsof -i tcp|grep LISTEN
sshd 698 root 3u IPv4 3425 0t0 TCP *:ssh (LISTEN)
sshd 698 root 4u IPv6 3427 0t0 TCP *:ssh (LISTEN)
java 17807 jenkins 15u IPv6 2792628 0t0 TCP *:3141 (LISTEN)
Cheers,
Uli
On 2013-10-31 23:01, Andreas Ernst wrote:
Am 31.10.13 22:59, schrieb Ulrich Stärk:
I just checked on the machine that is running the Tapestry builds but
there was nothing running
except for a seemingly stale Jenkins client process. I killed it but I
doubt that it was causing
this problem. Port 4444 is not in use. Could it be that another test
instance is started before the
old one completely finished?
Uli
On 2013-10-31 22:16, Thiago H de Paula Figueiredo wrote:
On Thu, 31 Oct 2013 17:35:55 -0200, Apache Jenkins Server
<[email protected]> wrote:
See
<https://builds.apache.org/job/tapestry-trunk-freestyle/1172/changes>
MultiException[java.net.BindException: Address already in use,
java.net.BindException: Address
already in use]
Guys, any hints on how can I solve this? It seems there's some
hanging old
Jetty instance.
What about port 8080?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
