Generates the latest/greatest Maven-based artifacts for the Openfire project, every night.

Build: #3231 was successful Scheduled with changes by 3 people

Stages & jobs

  1. Build and Package

Build result summary

Details

Completed
Queue duration
1 second
Duration
11 minutes
Labels
None
Agent
mesonet-ah.agron.iastate.edu (4)
Revision
c7e4bc511c0cb172de77aa19c75c84b8f071fa72
Total tests
1935
Successful since
#3226 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann daryl herzmann c7e4bc511c0cb172de77aa19c75c84b8f071fa72 Merge pull request #3232 from guusdk/OF-3176_Schedule-dont-drop-s2s-stanza-after-async-connection-closure
OF-3176: Fix stanza loss during outgoing S2S session teardown
daryl herzmann daryl herzmann 920ef5651b473433937fc4aeb41fcba34e3ffd7e Merge pull request #3127 from guusdk/OF-3170_Rate-Limit-New-Connections
OF-3170: Implement basic rate limiting for new connections (C2S and S2S)
Guus der Kinderen Guus der Kinderen da9b79727674313021a4a64ad07addf3a1ce6b19 Update xmppserver/src/main/java/org/jivesoftware/openfire/session/LocalOutgoingServerSession.java
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Guus der Kinderen Guus der Kinderen a0a36bf57f2ff4e2ad635762c6cc8cd4aba3fc73 OF-3176: Fix stanza loss during outgoing S2S session teardown
When an outgoing server-to-server (S2S) connection closes, the connection is marked closed immediately, but route removal from the routing table happens asynchronously during teardown. This creates a short race window where routing can still send stanzas to a closing session, which then sees a closed connection and drops the stanza.

This change fixes that behavior by waiting for teardown to fully complete before re-routing a stanza that reached a closed outgoing session. Waiting for close completion ensures stale route cleanup has finished, after which normal routing can use an existing replacement session or create a new one.

A new system property, xmpp.server.session.redelivery-timeout (default: 30 seconds), controls how long Openfire waits for teardown completion before returning an error to the sender.
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> e420222a6fe6791218ad5c076fde9c8fd861ab8a chore(deps): bump org.apache.maven.plugins:maven-compiler-plugin
Bumps [org.apache.maven.plugins:maven-compiler-plugin](https://github.com/apache/maven-compiler-plugin) from 3.14.0 to 3.15.0.
- [Release notes](https://github.com/apache/maven-compiler-plugin/releases)
- [Commits](https://github.com/apache/maven-compiler-plugin/compare/maven-compiler-plugin-3.14.0...maven-compiler-plugin-3.15.0)

---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-compiler-plugin
  dependency-version: 3.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-3170Could not obtain issue details from Jira
Unknown Issue TypeOF-3171Could not obtain issue details from Jira
Unknown Issue TypeOF-3172Could not obtain issue details from Jira
Unknown Issue TypeOF-3173Could not obtain issue details from Jira
Unknown Issue TypeOF-3176Could not obtain issue details from Jira

Shared artifacts

Artifact File size
install4j-generated media 5 KB