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

Build result summary

Details

Completed
Queue duration
5 minutes
Duration
1 minute
Labels
None
Revision
bcfb0a2fe2e41c22579815376384dcf91fd03bc7
Total tests
475
Successful since
#922 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> bcfb0a2fe2e41c22579815376384dcf91fd03bc7 Merge pull request #1982 from guusdk/OF-2368_MUC-dont-kick-nonghosts-redux
OF-2368: Register MUC ping responses as user activity
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 2975e73cd39a88b93914c7da97bfdb872e6d0464 Merge pull request #1980 from guusdk/OF-2371_Outbound-promise-queue-size
OF-2371: Increase queue capacity for OutgoingSessionPromise
Guus der Kinderen Guus der Kinderen c93622d00a3a943d2768b34bc654b031ab7d669b OF-2368: Register MUC ping responses as user activity
Previously, Openfire was sending an IQ Ping to inactive users, but didn't register the response as activity.
Guus der Kinderen Guus der Kinderen 9362257904127cd0611417f8341d8a03ead4e823 OF-2371: Increase queue capacity for OutgoingSessionPromise
The queue should be large enough to easily hold the stanzas sent back to a federated user that is joining a MUC room.
Guus der Kinderen Guus der Kinderen 05bab329c19fcfbe90d65652999027cc0ba8031c OF-2369: Do not do outbound S2S when inbound disabled.
When Openfire is configured to not allow inbound S2S of a particular flavor (direct or non-direct TLS) do not try to establish outbound S2S of the same type.

This effectively makes an outbound S2S attempt impossible when Openfire is configured to not accept any inbound S2S.

Jira issues

IssueDescriptionStatus
4 more issues…
Unknown Issue TypeDIRMINA-1156Could not obtain issue details from Jira
Unknown Issue TypeOF-910Could not obtain issue details from Jira
Unknown Issue TypeOF-2209Could not obtain issue details from Jira
Unknown Issue TypeOF-2354Could not obtain issue details from Jira
Unknown Issue TypeOF-2367Could not obtain issue details from Jira