This is very likely to create a memory leak

INFO [] - Closing Root WebApplicationContext: startup date [Mon Dec 12 18:31:08 CST 2016]; root of context hierarchy
INFO [] - {dataSource-2} closed
INFO [] - {dataSource-1} closed
Dec 12, 2016 6:35:37 PM clearReferencesJdbc
SEVERE: The web application [/emplatform] registered the JDBC driver [] but failed to unregister it when the web application was stopped.
To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Dec 12, 2016 6:35:37 PM clearReferencesJdbc
SEVERE: The web application [/emplatform] registered the JDBC driver [] but failed to unregister it when the web application was stopped.
To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Dec 12, 2016 6:35:37 PM clearReferencesThreads
SEVERE: The web application [/emplatform] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it.
This is very likely to create a memory leak.
Dec 12, 2016 6:35:37 PM stop
INFO: Stopping ProtocolHandler ["http-bio-9001"]
Dec 12, 2016 6:35:37 PM stop
INFO: Stopping ProtocolHandler ["ajp-bio-8012"]
Dec 12, 2016 6:35:37 PM destroy
INFO: Destroying ProtocolHandler ["http-bio-9001"]
Dec 12, 2016 6:35:37 PM destroy

INFO: Destroying ProtocolHandler ["ajp-bio-8012"]

reason;

Insufficient memory allocation

Solution: In the tomcat directory, modify the bin/file and add the following statement:

JAVA_OPTS="-server -Xms768m -Xmx768m -XX:PermSize=128m"