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: #2523 was successful Changes by daryl herzmann <akrherz@iastate.edu> and Guus der Kinderen

Build result summary

Details

Completed
Queue duration
8 minutes
Duration
19 minutes
Labels
None
Agent
Default Agent
Revision
90f2665e83fa0a9423e04ff938a8e68746000424
Total tests
1385
Successful since
#2504 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann <akrherz@iastate.edu> daryl herzmann <akrherz@iastate.edu> 90f2665e83fa0a9423e04ff938a8e68746000424 Merge pull request #2362 from guusdk/OF-2752_StreamManagement-try-to-send-data-on-expected-network-disconnect
OF-2752: Refactor solution
Guus der Kinderen Guus der Kinderen d01f83d0935100e91550de4658b2c0062b1fc9c0 OF-2752: Refactor solution
In the previous commit for this issue, it was assumed that the state of a connection was always known 'good' or 'terminated'. In reality, there are lenghty periods in which Openfire cannot be sure of a connection is terminated, or simply unresponsive.

To avoid clients being disconnected by Openfire without their knowledge, Openfire should always try to send an end-of-stream indication. Without this, clients might assume for indefinite amounts of time that they're connected, while they are not.

Jira issues

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