There are numerous ways that Sakai — as a web-based application — can fail, mostly leaving log file evidence that is ready for interpretation behind.
This section's purpose is to give you a glimpse of which types of issues can exist. It explores a small set of messages. The methodology that was used for discovery purposes was to simulate issues by deliberately breaking the demonstration in a number of interesting ways.
During the experiments, failures forced the consumption of CPU time, causing the test computer to heat up, generated many gigabytes of log file within a few seconds, and generally harried and stressed the server.
Maven compiles Sakai 2.7 or above with version 1.6 of Java. If you run the application with an old version of Java, such as version 1.5, the JVM will generate the following error message:
Unsupported major.minor version 50.0
50 is the version number Sun uses to represent Java 1.6!
Java is backwardly compatible. Therefore, if your system...