Hi Geert,
I faced those issues very often using the cloud connection either with XMI 1.1, Asset Service (=XMI) or Native. I have already reported it to Sparx end of 2019.
Shortly, for those big imports where a lot of references are missing in the new repos, using cloud connection will fail on our side with a timeout.
However in the intranet (not via VPN) it is working most of the times with a direct ODBC mySQL connection. Native is working only with ODBC mySQL and EA1558 - I used it last week that way quite successfully.
For me it is a bug introduced in EA14 handling unresolvable relationships together with the cloud connection backend, so I use ODBC only for that.
Here my bug description, maybe it helps you investigating:
Summary:
EA crashes with data loss on bigger transaction (XMI Import, Baseline...)
Details:
If I want to exchange bigger data among different repositories than I use first an XMI export with Version 1.1(in EA15 I also tried "Native") that is working so far.
But the import is crashing or hanging when using larger files and often when there are a lot of references not solvable as I update a sub package of a larger context.
So I will have an inconsistent project afterwards.
I often get an WAIT_TIMEOUT from the Cloud Service, based on a OBDC Warning of a found Deadlock.
"Pro Cloud Server: Query in batch execute failed with message: FAIL: Microsoft OLE DB Provider for ODBC Drivers [-2147467259] [MySQL][ODBC 8.0(w) Driver][mysqld-8.0.19]Deadlock found when trying to get lock; try restarting transaction"
Either EA will hang (and GUI will soften in the background) at the import stage "Resolving Link" or "Fix Up external References" for example, the adding stage is often not critical.
Or I will get the message OLED Persistence Provider : ....not enough Memory for the transaction that ends in an "Out of Memory" error of EA. Then EA will not react anymore.
I guess it is even worse if I keep on working with other programs and the focus to the EA GUI is lost.
I is a little bit more stable using a direct OBDC connection from the client instead of the Cloud connection but it crashes likewise.
However if I use the EA1354 the deadlock warning still appears from time to time but EA13 will keep on importing and fixing all references and so right without and Out of Memory error.
Sparx Support answer:
When you were importing the XML file(s) and receiving the deadlock error, did the folder containing the information being imported already exist in the repository? The only time we were able to duplicate that error is when EA had to delete the previous information before doing the import, this occurs for all XMI 1.1 imports. We will need to investigate the cause of these deadlocks.
One of your comments mentioned Native imports. Can you round trip Native XML export/imports without errors? We ask because the Native XML import does not delete previous information before importing, it simple updates any data already present. The Native XML export/import has been designed from the ground up to be as fast as possible by reducing the amount of data being transferred over the network which greatly improves performance.
Can you described your environment in particular the location of the Pro Cloud and Database servers? The communications between EA and the Pro Cloud Server have been optimized however the Pro Cloud Server requires/assumes it has near immediate access to the database server, and will open 100's (if not 1000's) of database queries, therefore if the PCS is located in one network and the database server in another general performance will be impacted and in the worst cases, timeouts will occur.
Regards
Roman