Page Comparison

...

CONNECT 5.2 was install-tested in multiple environments and with multiple operating systems to support the federal partner environments and application servers/configurations used by the community.  As with each release, CONNECT was regression tested as well as integration tested against prior supported versions of CONNECT. Test summary report is /wiki/spaces/CONNECTWIKI/pages/661323837. See below the testing matrix with the application servers/OS that were utilized for release testing.

...

From a product development perspective, the team uses WildFly as the team-supported open source application server. We are aware of community members using CONNECT on JBoss EAP, the enterprise version of WildFly. We have published instructions for FIPS configurations on /wiki/spaces/CONNECTWIKI/pages/108691466 JBoss EAP 7, WebSphere and /wiki/spaces/CONNECTWIKI/pages/75038722 WildFly.

Development, installation and new feature testing will be done on WebLogic, WebSphere, JBoss EAP 7 and WildFly only.

...

.

...

The following tables display issues resolved or tasks addressed during the release of CONNECT 5.2. The details of these issues can be found in the CONNECT Issue Tracker, linked to in the tables below.

Features and improvements

(User stories, Improvements)  

...

...

...

...

...

...

...

...

...

...

Anchor
Known Issues Known Issues

 Known Issues

Issue
Image RemovedCONN-1218 -  CONNECTDirectConfig - postmasterAddressId Not Populating  OPEN Image RemovedCONN-1138 - when adding a Domain
Direct Interop: Multi-Recipient Messages(Inbound) issue when recipient is one of many recipients in the message OPEN
Garbage Collection (GC) exceptions may occur if CONNECT is undeployed and re-deployed without a server restart in between

...

Details of the functional requirements can be found in the following JIRA user stories. The 'Traceability' column provides useful wiki links, associated ticket information and test case traceability for these requirements.