Open spring-projects-issues opened 10 years ago
I had this situation about Caused by: java.net.BindException: Address already in use
, but not sure if for that module based on LDAP
It happens for multiple Gradle executions, for example Testings or Build.
What I did do was:
gradle --stop
and always check with jps
if exists some Gradle/Kotlin/MainWrapper running because I did realise that practically always the IDE - (i.e: STS) creates its own Gradle Daemon and that one only appears with jps
.
Therefore exists some Gradle's daemons working for Spring Security, some created by the console and other by the IDE itself. Both in parallel, therefore there the reason about the Caused by: java.net.BindException: Address already in use
. Since then I have the IDE open, but any Gradle command is executed in command.
If the Gradle
views are opened or if the Gradle
refresh is executed for the project through the IDE, it triggers the daemon of the IDE too
Thanks for the detailed feedback @manueljordan ! I also logged #9394 last week and this feedback is very helpful.
Hi @jgrandja - No problem, perhaps should be considered to do mention here to Marting Lippert?, perhaps should be valuable that the IDE itself through a special view or through BuildShip (I prefer the former) shows the Gradle's Daemons created by the STS itself.
Filip Hanik (Migrated from SEC-2691) said:
Using
new TcpTransport("127.0.0.1", port)
causes the following failure on some systems: