2009/6/10 Gintare Ragaisiene <gintare.ragaisi...@gmail.com>: > Hello everyone, > > I've installed cocoon 2.2 webapp on Tomcat 6. For this I deployed .war file > in Tomact's webapps directory. > After a day I looked at the logs and found this exception: > > Jun 9, 2009 8:31:51 PM org.apache.catalina.core.StandardWrapperValve invoke > SEVERE: Servlet.service() for servlet DispatcherServlet threw exception > java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3121) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1834) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1976) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2497) > at com.mysql.jdbc.ConnectionImpl.setAutoCommit(ConnectionImpl.java:4692) ... > Do anybody knows or can explain to me what is wrong? Where I should research > farther about it? >And maybe what outcome of this exception is? > > Thank you, > Gintare
"Broken pipe" usually means something tried to write to an established socket connection, but the other end was no longer there or had closed the connection prematurely. I've seen it most often with the servlet output stream or JSP writer, if the user hits the "stop" button in their browser or closes it while the response is still being generated and/or sent, or there's some networking problem along the way causes the connection to die. In your case, however, looks more like it was trying to issue some command to the database due to a setAutoCommit call (BEGIN TRANSACTION, maybe?) and discovered that the database was no longer listening to that connection. Perhaps the database had timed out the connection due to inactivity, though in that case if things had closed & cleaned up properly I'd have thought a "connection already closed" type SQLException would be more likely next time the invalid connection is got from the pool. But maybe that depends on the particular database driver; we don't use MySQL, so I can't say for sure. Do you get a lot of these exceptions or was this the only one? Are you aware of any problems with the database or network around the time this happened? Was the database server restarted at that time? Andy -- http://pseudoq.sourceforge.net/ Open source java sudoku application --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org