You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2003/04/08 09:03:42 UTC
DO NOT REPLY [Bug 18798] New: -
ActionServlet sets datasource log writer - causes oracle jdbc driver to spew out megabytes of log/run out of memory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18798>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18798
ActionServlet sets datasource log writer - causes oracle jdbc driver to spew out megabytes of log/run out of memory
Summary: ActionServlet sets datasource log writer - causes oracle
jdbc driver to spew out megabytes of log/run out of
memory
Product: Struts
Version: 1.1 Beta 3
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: Other
Component: Standard Actions
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: david@pastornet.net.au
This problem showed up for us in struts 1.02 but I notice the following is still
present in the struts 1.1b3 source code. From ActionServlet.java:
ds.setLogWriter(scw);
When jdbc is used directly from the web tier, the above statement makes the
oracle jdbc driver spew out megabytes (eg 100Mb in a short time) of internal
logging, and slows things down -tremendously-. In fact it causes the container
(tomcat 3.2.1) to run out of memory because the log file isn't written
immediately and the log is cached in memory.
There doesn't seem to be a way to tell struts to not do this.
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org