Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #2337 was successful Changes by Guus der Kinderen

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
3 minutes
Labels
None
Agent
Default Agent
Revision
bf1382c23e3918541f23728c1277bd5d696d7002
Total tests
625
Successful since
#2137 ()

Tests

Code commits

Author Commit Message Commit date
Guus der Kinderen Guus der Kinderen bf1382c23e3918541f23728c1277bd5d696d7002 OF-2524: Add database index for MUC room log retrieval
When loading the MUC room history for a single room, a query is executed that is not optimized by the existing database indexes:

`SELECT sender, nickname, logTime, subject, body, stanza FROM ofMucConversationLog WHERE logTime>? AND roomID=? AND (nickname IS NOT NULL OR subject IS NOT NULL) ORDER BY logTime`

On Ignite's server, this takes more than 400 milliseconds to execute.

When room preloading is disabled, all rooms that are being used need to be loaded from memory. Looking at the admin console will load all rooms on that page. If that contains 25 rooms, then this query alone causes a delay of many seconds before the page is loaded.
Guus der Kinderen Guus der Kinderen 56ba04f815a163ff2e833c1e5ec04b648cb517f9 OF-2524: Add MUC message history in bulk
Instead of loading message and adding to MUC room history one-by-one, do this in a batch.

With OF-2499, adding a message requires a lock to be held. In clustering, the repeated acquiring and releasing of that lock adds notable delays.

This commit prevents much of this overhead by adding all history in one go, replacing the lock contention for each message, with one singular lock.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-2499Could not obtain issue details from Jira
Unknown Issue TypeOF-2524Could not obtain issue details from Jira