Wake discovered a problem nearly identical to
SAK-22210 when upgrading to 2.9.
When they deployed to all their dev and test environments, there was no issue. The same set of artifacts was scheduled for prod deployment in the same environmental setup - however this resulted in the errors seen in the above ticket.
Some trial and error showed that by loading samigo-app after everything else had loaded would not produce the error, but restarts would cause problems unless the samigo app was removed and added after the other tools started up (ie startup tomcat/sakai without samigo-app and then deploy it separately after sakai had started).