@phildunlap As you say, I needed to upgrade mangoApi from 3.2.0 to 3.2.1(because of in the free-m2m2-core-3.2.1 mangoApi is the 3.2.0 version) too and mangoUI to 3.2.2 and everything is working now. Thank you
Thank you for your help. It was getting late last night and I made some silly tired brain mistakes. I started over this morning with your instructions and everything seems to be working now. No restore of the databases needed.
My other worry was that we have another piece of software on the server and I thought it may require an older 32 bit version of Java. But it seems to be working with the latest 64 bit java as well.
I couldn't say for sure. I would advise sorting that top window by memory (shift+f, arrows to mem, press 's'). You could experiment with removing the Xms parameter.
Sometimes with larger heaps the garbage collector can be lazy, and then when it does run it has more work to do and a bigger pile of potential garbage to sift through, but I wouldn't expect that to cause what you're describing, as it also generally has more garbage it can collect, and it can meet its targets easily
I've not tried recently with the latest version, but previously I've had issues with applying the license to a docker image.
Joel and i tried a few things, but were unable to make the licence 'stick'.
What would happen is we would install the licence, the mango instance would restart, and in the logs it behaved as though the licence file wasn't created on disk.
The database would undergo the same updates it would if it were upgrading to 2.7.
No the upgrades have not been updated to drop the tables, it slipped my mind to get "DROP IF EXISTS" into the mysql upgrade scripts, so you may have to drop the tables the upgrades create, or restore your MySQL dump into a new MySQL database.
What would bring hesitation in upgrading the core? 2.7.12 is pretty nice! And 2.8 will be along very soon.
To answer your question, maybe. Module's core version compatibility is determined in the module's module.properties file. You could change the core compatibility version and subvert the check if the module matches the core, but we would not offer support in such a circumstance and will not be surprised if there are compilation type errors (NoSuchMethodException, etc) or other unexpected issues in doing so.
I have not run into this problem. This made me think of the first tech class I had, where I was playing Freecell on our Windows computers. If I paused for a second in my game, the cursor would slowly move up to the corner and click the X. It happened several times! I went up to the teacher and said I suspected the computer had a virus that was closing Freecell. Of course, he was closing Freecell. 'Remote assistance' is often enabled by default in Windows these days!
In this case, my teacher is perhaps Windows Defender, and the rest is perhaps a pointless side story. If Windows Defender is enabled, try adding an exclusion for your C:\mango directory. Depending on your File settings C:\ProgramData might be hidden to the searches you're running. If not Defender, might there be another Antivirus program getting ahead of itself and deleting your C:\mango?
After that, if I was facing this problem, I would try (in no particular order)...
A. Downloading Mango again
B. Trying it without modules
C. Checking out the "Event Viewer" for interesting logs
D. Having a text document opened in an editor, and saved in your C:\mango directory.
E. Using the default env.properties
F. Booting on a clean database
G. Disabling networking
H. Trying a different directory
I. Watching C:\mango disappear in Windows Explorer (it'll live update!)
JK. Switch to linux