Logs are filled with stacktraces on ERROR on 404's of servlets. / should use 1.2 bridge
I for example serve images on:
http://michiel.omroep.nl/mm/mmbase/images/
http://michiel.omroep.nl/mm/mmbase/images/12130809123123
is obviously a 404.
But in my logs appear:
22:49:34,725 ERROR mmbase.bridge.implementation.BasicCloud - Something went wrong while getting node with number 12130809123123 (does it exist?)
java.lang.RuntimeException: Node not found !! (key = '12130809123123')
at org.mmbase.module.core.TemporaryNodeManager.getNode(TemporaryNodeManager.java:124)
at org.mmbase.bridge.implementation.BasicCloud.getNode(BasicCloud.java:188)
at org.mmbase.servlet.BridgeServlet.getNode(BridgeServlet.java:116)
at org.mmbase.servlet.HandleServlet.doGet(HandleServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:200)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:309)
at org.mmbase.servlet.MMBaseServlet.service(MMBaseServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind._efb._plc(.:518)
at com.evermind._efb._adc(.:174)
at com.evermind._cs._yqb(.:614)
at com.evermind._cs._yrb(.:189)
at com.evermind._bx.run(.:62)
So any visitor of my site can cause a mess in my logs.
Solution: use 'new hasNode' function of Cloud.
I use hasNode now, but i see now:
16:37:11,364 ERROR mmbase.module.core.MMObjectBuilder getNodeType.762 - java.sql.SQLException: Could not find the otype(no records) using following query:SELECT otype FROM mm_object WHERE number=12313132
at org.mmbase.module.core.MMObjectBuilder.getNodeType(MMObjectBuilder.java:757)
at org.mmbase.module.core.MMObjectBuilder.getNode(MMObjectBuilder.java:868)
at org.mmbase.module.core.MMObjectBuilder.getNode(MMObjectBuilder.java:817)
at org.mmbase.module.core.MMObjectBuilder.getNode(MMObjectBuilder.java:829)
at org.mmbase.module.core.TemporaryNodeManager.getNode(TemporaryNodeManager.java:123)
at org.mmbase.bridge.implementation.BasicCloud.hasNode(BasicCloud.java:232)
at org.mmbase.bridge.implementation.BasicCloud.hasNode(BasicCloud.java:224)
at org.mmbase.servlet.BridgeServlet.getNode(BridgeServlet.java:116)
at org.mmbase.servlet.HandleServlet.doGet(HandleServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:200)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:309)
at org.mmbase.servlet.MMBaseServlet.service(MMBaseServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind._efb._plc(.:518)
at com.evermind._efb._adc(.:174)
at com.evermind._cs._yqb(.:614)
at com.evermind._cs._yrb(.:189)
at com.evermind._bx.run(.:62)
I for example serve images on:
http://michiel.omroep.nl/mm/mmbase/images/
http://michiel.omroep.nl/mm/mmbase/images/12130809123123
is obviously a 404.
But in my logs appear:
22:49:34,725 ERROR mmbase.bridge.implementation.BasicCloud - Something went wrong while getting node with number 12130809123123 (does it exist?)
java.lang.RuntimeException: Node not found !! (key = '12130809123123')
at org.mmbase.module.core.TemporaryNodeManager.getNode(TemporaryNodeManager.java:124)
at org.mmbase.bridge.implementation.BasicCloud.getNode(BasicCloud.java:188)
at org.mmbase.servlet.BridgeServlet.getNode(BridgeServlet.java:116)
at org.mmbase.servlet.HandleServlet.doGet(HandleServlet.java:116)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:200)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:309)
at org.mmbase.servlet.MMBaseServlet.service(MMBaseServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at com.evermind._efb._plc(.:518)
at com.evermind._efb._adc(.:174)
at com.evermind._cs._yqb(.:614)
at com.evermind._cs._yrb(.:189)
at com.evermind._bx.run(.:62)
So any visitor of my site can cause a mess in my logs.
Solution: use 'new hasNode' function of Cloud.