Win2008 - Jenkins slave generates a lot of FIN_WAIT_2 socket status
18 views
Skip to first unread message
morten bjoernsvik
unread,
Aug 19, 2015, 3:34:14 AM8/19/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Jenkins Users
Hi All
We have this irritating problem when restarting jenkins that it hangs with port already in use:
INFO: Winstone shutdown successfully
aug 10, 2015 11:57:41 AM winstone.Logger logInternal
SEVERE: Container startup failed
java.io.IOException: Failed to start Jetty
at winstone.Launcher.<init>(Launcher.java:156)
at winstone.Launcher.main(Launcher.java:354)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at Main._main(Main.java:293)
at Main.main(Main.java:98)
Caused by: java.net.BindException: Address already in use: bind
when they are gone it starts fine.We are running latest Jenkins 1.624. But I've not done anything on the slave it just starts a jekins.war file. should this also be updated?