Upgrade jdk for moqui

[Alessio Guerriero]

hello,

i collaborate with a company in italy and we are interested in the moqui project, we currently use it, and we would like to update the JDK to one of the most recent (better would be openjdk 21). 

 In your opinion what would be the necessary steps to perform the update? I have already tried but I got problems with bitronix with both 17 and 21 of JDK. 

 Thanks and see you soon, 

 Alessio

[Ayman Abi Abdallah]

Hi Alessio,

Thank you for your email! The main issue with updating the JDK version is that most if not all components in the ecosystem would require updates as well. This is a time consuming task. If you’re only interested in updating the framework version to JDK 21 then you could check my fork at https://github.com/moquiup/moqui-framework. It runs on JDK 21 and has a few minor additions. I’m planning on contributing my changes later once I get the change to review and update all the components.

Regards,

Ayman Abi Abdallah

--
You received this message because you are subscribed to the Google Groups "Moqui Ecosystem" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moqui+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/moqui/a639f8c5-ceb1-4348-be63-5b402d7423d3n%40googlegroups.com.

[Adam Heath]

The bitronix thing is concerning.  Upstream for that seems abandoned, and what's deployed in moqui is a custom binary compile, with no source code.

To view this discussion visit https://groups.google.com/d/msgid/moqui/A2E29AB3-DA25-43BE-95B8-36FA4C6E1A97%40gmail.com.

[Alessio Guerriero]

Hi, sorry for the late reply. I’d like to give you an overview of our project. The company I work for is a leader in industrial automation systems for the food sector (we are based in the Italian Food Valley). Since 2018, we have been developing components for managing machines, production cells, and factories—including the integration with automated vertical storage, AGVs, and LGVs—as well as product traceability and production management (Pull style), all based on Moqui. So far, we have deployed Moqui for about 50 factories/plants. For real-time machine control, we have developed a framework in standard IEC 61131-3 Structured Text (*moqui-plc*) for PLCs from various manufacturers, including Siemens, Codesys, ABB, and others. Additionally, we have extended the control layer by implementing logic directly on drives and servo drives. The drive brands we have integrated so far include ABB, Schneider, Danfoss, and Control Techniques. For input-output modules, we have integrated these same brands, along with Siemens and Allen-Bradley. Furthermore, we have integrated CNC machines (Mazak via MTConnect) and ABB robots. Moqui continuously exchanges data with all these devices through Eclipse Milo (OPC UA), Modbus TCP libraries, and, more recently, Apache PLC4X. The company has gained confidence in the platform and is now eager to invest in developing a second release. This would allow us to eliminate various compromises and workarounds that were initially introduced due to time constraints. The data model we have built covers multiple aspects—not just devices or groups of devices, device requests but also trajectory modeling, control algorithms, and production cycles. The company is willing to allocate resources, including financial support, to these updates. However, we seek guidance from the Moqui community. We are also willing to contribute part of our code, including the PLC framework we developed. Currently, we are in the process of porting the PLC framework to the new Siemens Simatic AX platform, which is still in beta. We expect to have a first usable version around July 2025. We would be happy to provide more details if needed.

[Alessio Guerriero]

today i have upgrade the atomikos component and moqui works fine with the JDK 21..

 @Ayman i have seen your work but the problem with bitronix maybe is not resolved only with upgrade of gradle..

see you soon 

Alessio

[Alessio Guerriero]

this is the result of upgrade:

The code of atomikos is here if you want verify it

[Michael]

I have java 17 working well in production with Bitronix here.

Once it is more widely used it will eventually be used in master. 

[Michael]

The sourcecode for bitronix is a stabilization fork from here, and works fine.

I think the java transaction manager ecosystem is so closely tied into hibernate and spring that most alternatives have gone commercial or are stale, so unless we write our own I'm not sure we have great options.