Alex "Blex" B

Same problem here. * jakarta.annotation-api-1.3.5.jar: CVE-2022-31569(9.3) * jakarta.transaction-api-1.3.3.jar: CVE-2022-31569(9.3) * spring-data-jpa-2.7.1.jar: CVE-2022-31569(9.3) It looks like all these projects have "projects" in their ``url``-Tag. Is there a reason why the ``url``...

Thank you for having a look at this. > It's not a good guess, but my best guess is that there's something that causes the load balancer to dispatch the...

Full logs of last weeks incident (seen in my comment above), anonymized: [logs.zip](https://github.com/vaadin/flow/files/9297785/logs.zip) All times in MESZ (UTC+2).

Note: This problem is fixed with Wildfly 26.1.2.Final Related issues: * https://issues.redhat.com/browse/WFCORE-5916 (Updates JBoss vfs to ``3.2.17.Final`` in Wildfly Core ``18.1.2.Final``) * https://issues.redhat.com/browse/WFLY-16859 (Updates Wildfly Core to ``18.1.2.Final`` in Wildfly...

So while comparing the changes between [4.3.0 and 4.4.0](https://github.com/SeleniumHQ/selenium/compare/selenium-4.3.0...selenium-4.4.0) I noticed that the [``DEFAULT_RETRY_INTERVAL`` was changed from 0 to 15](https://github.com/SeleniumHQ/selenium/compare/selenium-4.3.0...selenium-4.4.0#diff-4542e77c4ae8c826b6d9b236675ab8745db5be1201b84c72e6bdfe4060c1115fR38)  (was done in [this commit](https://github.com/SeleniumHQ/selenium/commit/5294269c1dee029934a9b3ccd44c47cfc4af8653)) This exactly matches the...

Same problem here. It works mostly fine for Selenium 4.2.2 but with selenium 4.4.0 >60% of our tests suffer from above problem. It looks like sometimes the part of Selenium...

The same bug also persists in Selenium 4.5.0. I created an issue at https://github.com/SeleniumHQ/selenium/issues/11082 so that the underlying problem gets fixed.

I think I found the problem or at least a workaround: https://github.com/SeleniumHQ/selenium/issues/10984#issuecomment-1268011440 Using ``.withEnv("SE_OPTS", "--session-retry-interval 1")`` (in Selenium 4.4+) fixed the timeouts for me

This problem seems to come from the mssql-jdbc-driver directly: https://github.com/microsoft/mssql-jdbc/blob/0f3e0a10f2f85b5b357811907fdb487d63e49830/src/main/java/com/microsoft/sqlserver/jdbc/SQLServerConnection.java#L3107-L3118

I think it's just log spam (however I'm not 100% sure) looks like the port is exposed but the SQL Server is not fully setup / starting. After the container/server...