127.0.0.1 - - [22/Jan/2018:13:33:10 +0800] "GET / HTTP/1.1" 404 1074
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/tutorRegister.jsp HTTP/1.1" 200 13656
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/BootStrap/Checkbox.js HTTP/1.1" 404 1108
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/BootStrap/bootstrap-multiselect.js HTTP/1.1" 404 1121
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/bootstrap.min.js HTTP/1.1" 404 1106
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/jquery.js HTTP/1.1" 404 1099
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/jqBootstrapValidation.js HTTP/1.1" 404 1114
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/contact_me.js HTTP/1.1" 404 1103
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/Image/aa1.png HTTP/1.1" 404 1100
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:34:33 +0800] "POST /Hi5S/addTutor HTTP/1.1" 200 -
127.0.0.1 - - [22/Jan/2018:13:35:29 +0800] "GET / HTTP/1.1" 404 1074
127.0.0.1 - - [22/Jan/2018:13:35:54 +0800] "GET / HTTP/1.1" 404 1074
127.0.0.1 - - [22/Jan/2018:13:36:16 +0800] "GET / HTTP/1.1" 404 1074
Jan 22, 2018 1:10:31 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc
WARNING: The web application [Hi5S] registered the JDBC driver [com.mysql.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.
Jan 22, 2018 1:10:31 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
WARNING: The web application [Hi5S] appears to have started a thread named [Tomcat JDBC Pool Cleaner[1745616951:1516597490962]] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:552)
java.util.TimerThread.run(Timer.java:505)
tangara goh wrote:... and what does 1074 means?
tangara goh wrote:127.0.0.1 - - [22/Jan/2018:13:33:10 +0800] "GET / HTTP/1.1" 404 1074
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/tutorRegister.jsp HTTP/1.1" 200 13656
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/BootStrap/Checkbox.js HTTP/1.1" 404 1108
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/BootStrap/bootstrap-multiselect.js HTTP/1.1" 404 1121
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/bootstrap.min.js HTTP/1.1" 404 1106
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/jquery.js HTTP/1.1" 404 1099
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/jqBootstrapValidation.js HTTP/1.1" 404 1114
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/js/contact_me.js HTTP/1.1" 404 1103
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:33:15 +0800] "GET /Hi5S/Image/aa1.png HTTP/1.1" 404 1100
0:0:0:0:0:0:0:1 - - [22/Jan/2018:13:34:33 +0800] "POST /Hi5S/addTutor HTTP/1.1" 200 -
127.0.0.1 - - [22/Jan/2018:13:35:29 +0800] "GET / HTTP/1.1" 404 1074
127.0.0.1 - - [22/Jan/2018:13:35:54 +0800] "GET / HTTP/1.1" 404 1074
127.0.0.1 - - [22/Jan/2018:13:36:16 +0800] "GET / HTTP/1.1" 404 1074
GET / HTTP/1.1" 404 1074
RFC2616 wrote:
404 Not Found
The server has not found anything matching the Request-URI.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
In other words, you don't have anything defined to handle a URI of "/", so Tomcat has returned an error page with accompanying response code of 404. This tells me that you've removed or altered the TOMCAT_HOME/webapps/ROOT directory, because that's where the default root webapp lives and it would normally return a "400" response with page content.
And 1074 is the number of characters in the Tomcat-generated response page that will be displayed in the client's browser.
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1">
<display-name>Hi5S</display-name>
<welcome-file-list>
<welcome-file>tutorRegister.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
<resource-ref>
<description>MySQL Datasource</description>
<res-ref-name>jdbc/hi5s</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
The message is wrong, in that Java does not leak "memory", it leaks objects. Specifically in your case, I think it's leaking Database Connections, which means that not only is the memory that holds the Connection being leaked, but OS network sockets are leaking as well.
To avoid this, you MUST close connection pool Connections as soon as you are done using them, and make sure that no Exceptions would bypass the close statement. You cannot depend on the garbage collector to handle this for you. And absolutely do not ever store Connections in session-scope objects.
Database connections are the most commonly leaked objects, but another possibility would be if you spawned threads while handling a servlet or JSP request. J2EE standards strictly forbid doing that. Not only can they leak, they can potentially crash any webapp in the server or even the server itself.
Knute Snortum wrote:I'm confused. I don't see any servlets mapping or URL patterns, like:
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:
What I am suspecting, however, is that the webapp that owns this particular web.xml is not deployed as the root webapp, and that the root servlet has been removed. Because the URL in question doesn't have an explict webapp context, which means that the root webapp would be the recipient of the request.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Don't get me started about those stupid light bulbs. |