Hi again! Well, I give you more information about our setup...
We have 2 servers ( both with IIS + .NET and Tomcat ) and 1 server DB with MySQL and MS SQL Server. Applications in IIS work with MS SQL and applications in Tomcat work with MySQL. Both 3 servers are virtual machines distributed in 2 differents physical machines and in the same net. We've got a balancer too with an IIS farm and a Tomcar farm. I think that's all... some new idea? some critical thing we don't take care? We'll be waiting your news :) Thanks Alan Chaney escribió: > Hi Andre > > Totally agree with your comments with respect to the OP's first > exception. However, they actually had two exceptions in their original > email with completely different time stamps. The 2nd exception appears > to be a HibernateException > > 01-Mar-2009 11:36:21 org.apache.catalina.core.StandardWrapperValve invoke > SEVERE: Servlet.service() for servlet HumanReadableLinksServlet threw > exception > org.hibernate.TransactionException: Transaction not successfully started > at > org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:100) > > at > > > The cause of this is probably completely unconnected to a remote > client disconnect. The error above is thrown under the following > conditiions: (from > http://www.hibernate.org/hib_docs/v3/api/org/hibernate/TransactionException.html > > > "Indicates that a transaction could not be begun, committed or rolled > back. " > > With the very limited information given it is iimpossible to infer the > exact cause but I would suspect that likely possibilities are a severe > resource contention on the database or possibly a transaction timeout. > > The OP gave these two errors but didn't indicate whether they were > happening repeatedly or just "one offs". One further possibility is a > poor network setup causing failure to access the database and/or > connection failures with the client. More information would be > required to correctly diagnose the problem. I doubt very much that the > problem or problems are directly connected with Tomcat - more likely > the application or the system configuration. > > Regards > > Alan > > > André Warnier wrote: >> Laura Bartolomé wrote: >>> Hi again... >>> >>> We are going on findind errors and problems... and we wanna cry... >> >> We certainly would not want that to happen, because then your >> messages here would get all mushy and more difficult to read. >> And Tomcat would probably not care. >> >>> someone could explain what means these errors? The first: >>> >>> 01-Mar-2009 00:08:46 org.apache.catalina.core.StandardWrapperValve >>> invoke >>> SEVERE: Servlet.service() for servlet HumanReadableLinksServlet threw >>> exception >>> java.net.SocketException: Connection reset by peer: socket write error >>> at java.net.SocketOutputStream.socketWrite0(Native Method) >>> at java.net.SocketOutputStream.socketWrite(Unknown Source) >>> at java.net.SocketOutputStream.write(Unknown Source) >>> >> The above rather self-explanatory message (Connection reset by peer: >> socket write error) typically means what it says : the client >> (browser ?) "went away" before the server could send a response to >> it. That usually means : >> either >> a) the user clicked the "stop" or "cancel" button in the browser, >> before he received the answer to his request >> or >> b) the impatient user clicked on another link on the current page, >> causing the browser to interrupt the current connection to the server >> and load the new page, before the server could send the response to >> the previous request >> >> The above 2 reasons probably cover at least 90% of the cases. It >> could be due to the application being so slow to answer, that the >> human user gets impatient and starts clicking all over. >> >> c) some communication problem occurred between the client and the >> server, causing the TCP connection to be closed prematurely. >> From personal experience, that may be due to some proxy or other >> in-between element, closing the connection because nothing happened >> on that connection for some time. >> >> Anyway, with 100% certainty, it means that when the server was ready >> to send the answer to the client, it could not, because the >> connection with the client had been closed for some reason. >> >> >> >>> and the other: >>> >>> 01-Mar-2009 11:36:21 org.apache.catalina.core.StandardWrapperValve >>> invoke >>> SEVERE: Servlet.service() for servlet HumanReadableLinksServlet threw >>> exception >>> org.hibernate.TransactionException: Transaction not successfully >>> started >>> at >> >> I am no specialist, but according to the above message, that seems to >> be something in the "hibernate" application, not something coming >> from Tomcat itself. So you probably should ask in some "hibernate" >> forum what it means. >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> >> !DSPAM:49aaa5fc82807785049143! >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
