Skip to Content
Last modified by Erik Bakker on 2022/06/16 13:50
From version 18.1
edited by Erik Bakker
on 2022/06/16 13:50
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2022/06/16 12:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -eMagiz Mendix Connector - 3.0.2
1 +61
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Runtime.WebHome
1 +Main.Release Information.Build numbers.WebHome
Content
... ... @@ -1,34 +1,20 @@
1 -Major update that switches the underlying messaging technology to use AMQP over Websocket Secure protocol.
1 +Small update that fixes three specific issues.
2 2  
3 +Find out more in our [release blog]
3 3  
4 -===== Major changes =====
5 5  
6 -* The eMagiz Mendix Connector now connects to the eMagiz bus using the AMQP over WebSocket Secure (amqpwss) protocol. This should be better compatible with most current and future cloud infrastructures. Also, by switching to a standardized protocol, the new eMagiz Mendix Connector provides better forward compatibility with future changes to the eMagiz messaging technology.
7 -* When sending messages asynchronously from Mendix to the eMagiz bus, the eMagiz Mendix Connector buffers these messages internally in case the bus is unreachable. In previous versions these outgoing messages were always stored in an embedded JMS server first, and then forwarded to the eMagiz bus. From this version onwards the eMagiz Mendix Connector no longer contains an embedded JMS server, but uses the Mendix database to temporarily store these messages. Functionally speaking the overall messaging behaviour is the same, but there are some notable differences:
8 - ** Messages are now only stored locally when the connection to the eMagiz bus is down. During normal operations messages are send in real-time, which might (slightly) increase performance.
9 - ** Max limit for locally stored runtime metrics was 5 MiB and is now 1000 messages. In practice this should be quite similar. The maximum for "normal" user-defined messages is still unlimited.
10 - ** A button "queued messages" has been added that shows how many messages are currently stored locally, waiting to be send to the bus. Previously there was no way to to see this.
11 - ** Mendix logging has been added to inform about messages being stored locally. During startup, the number of messages that are still present in the local message store is logged. The message "switching to 'offline' mode: messages are now being stored locally" is logged when the first message cannot be delivered in real-time to the eMagiz bus, and the message "switching back to 'online' mode: all locally stored messages have been send" is logged when the real-time delivery is available again and the full backlog of stored messages has been processed.
12 - ** To reduce the amount of disk space used, all messages are now compressed before storing them locally.
13 -* Changed and updated many dependencies in 'userlib'. Make sure to run the cleanup tool ('resources/emagiz-cleanup-tool.jar') to remove all old dependencies.
14 - ** Replaced HornetQ 2.3.25 with Qpid JMS 0.40.0 and Proton-J 0.31.0
15 - ** Updated Spring Framework from 4.3.8 to 4.3.20
16 - ** Updated Spring Integration from 4.3.9 to 4.3.17
17 - ** Updated Spring Retry from 1.1.5 to 1.2.2
18 - ** Updated Netty from 3.6.10 to 4.1.34
19 - ** Updated JMS spec from 1.1 to 2.0
20 - ** Updated Joda Time from 2.7.0 to 2.10.1
21 - ** Updated Commons Codec from 1.9.0 to 1.11.0
22 - ** Added JTA spec 1.1
23 - ** Removed JBoss Logging 3.1.4
24 -* From this release onwards, Mendix 5 is no longer supported.
6 +===== Minor Changes =====
25 25  
26 -===== Known Issues =====
8 +* Updated bundle 'com.emagiz.bundles.groovy-all' from 3.0.9.1 to 3.0.9.2
9 +* Removed bundle 'com.sun.mail.javax.mail' because it was not used anymore
10 +* Updated bundle 'com.emagiz.components.security' from 7.1.1 to 7.2.0
11 +* Updated bundle 'com.emagiz.components.http' from 7.2.1 to 7.2.2
12 +* Updated bundle 'com.emagiz.util.codec' from 6.1.0 to 6.1.1
27 27  
28 -* In older versions of the Mendix Desktop Modeler, "emulate cloud security" may cause the eMagiz Mendix connector to fail to connect. This will not occur in the actual cloud. From Mendix 7.21.0 on, this setting has been removed.
14 +===== Bug Fixes =====
29 29  
30 -===== Remarks =====
16 +* The OAuth 2.0 authorization interceptor in the Rest Template component contained client 'Authentication methods’ that were invalid and caused a flow not to start in build 59. Also the clockskew is now configurable so we can handle the requirements of more oauth2 authentication providers.
17 +* The Amazon S3 authentication interceptor in the Rest Template component had a threading issue where the key would be invalid on heavy usage. The threading has been changed and is now behaving correctly.
18 +* In several flow designer components you can add Groovy scripts. Since build 59 using FastStringUtils (JSON parsing) did not work.
19 +* For Gen3 runtimes we upgraded to Spring Boot 2.6.6 to bring the latest security patches.
31 31  
32 -* This version is NOT compatible with HornetQ. Be sure to first upgrade your JMS server to accept AMQP connections before using this connector version to connect to it.
33 -* Versions 3.0.0 and 3.0.1 were given out to a select number of early adopter buses, but were never GA releases. These release notes therefore list all cumulative changes since the last public release (version 2.5.0). We strongly recommend upgrading from versions 3.0.0 and 3.0.1, since 3.0.2 contains an important fix: queue prefetch was enabled to prevent large messages getting stuck in queues.
34 -* Version 3.x of the connector is fully compatible with flows build for version 2.x with one exception: the connector infra needs to be updated to switch from HornetQ to AMQP connections. You can simply tell the difference by the build number of the packages: build number 2 is for EMC version 2.x (HornetQ) and build number 3 is for EMC version 3.x (AMQP).