Christopher,

"For dev/test, we sometimes have weeks with no activity, and I've never
seen any problems."

Let's suppose that during this no-activity period, you're restarting once
or twice the database. Or that a firewall silently dropped the connection.
Is the first request lost, Tomcat returning a 500 ?

"If you have to bounce Tomcat every day to keep your applications
running smoothly, it's the fault of your application, not of Tomcat."

Not only "my" applications, but many among the thousands that I had to deal
with in different large companies. Maybe there is a wrong understanding of
JDBC and how to use it, but if so many are failing to understand, this
means the poor documentation is somewhat responsible. Another point is that
developers like to copy/paste their old code which they believe is
fail-safe, bringing the same bugs again and again.

best regards





2016-08-23 22:33 GMT+02:00 Christopher Schultz <ch...@christopherschultz.net
>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Aurélien,
>
> On 8/22/16 3:36 PM, Aurélien Terrestris wrote:
> > "We have a Tomcat 7 and Axis 2 for our Java SOAP web service over
> > https on our Ubuntu server. We also use C3PO connection pooling
> > (also in other web services which is working fine). However, I´m
> > not sure if this is related to the topic."
> >
> > I believe it is. Is the faulty web service getting requests all the
> > time, or there are some long time without requests ? I can't speak
> > for all the mailing list, but myself I do a daily restart of my
> > Tomcats to prevent such problem.
>
> I only restart my Tomcats for application upgrades. We use Tomcat's
> DBCP2-based connection pool. We don't have very many periods of
> inactivity in production.
>
> For dev/test, we sometimes have weeks with no activity, and I've never
> seen any problems.
>
> If you have to bounce Tomcat every day to keep your applications
> running smoothly, it's the fault of your application, not of Tomcat.
>
> - -chris
>
> > 2016-08-22 17:32 GMT+02:00 Matthias Schmitt
> > <m.schm...@colo21.com>:
> >
> >> Hello everybody,
> >>
> >> We have a Tomcat 7 and Axis 2 for our Java SOAP web service over
> >> https on our Ubuntu server. We also use C3PO connection pooling
> >> (also in other web services which is working fine). However, I´m
> >> not sure if this is related to the topic.
> >>
> >> The web service is working for about two/three days and after
> >> that time period it´s not working anymore. Then our consuming
> >> customer receives a Read Timeout Exception. After restarting the
> >> Tomcat servlet everything is working fine again. Processing the
> >> request has a duration of about 3 seconds. The Axis 2 has a
> >> default socket timeout of 30 seconds. Our customer has a wait
> >> timeout of 60 seconds. The strange thing about the problem is
> >> that it´s working for amount of time and then the problem occurs.
> >> Even if we increase the client timeout it seems like the request
> >> will be not processed. Also increasing the socket timeout value
> >> in axis configuration does not take effect. There is no exception
> >> message in the log that could help us to reproduce the problem.
> >>
> >> Thanks for your help,
> >>
> >> Mit besten Grüßen/with best regards
> >>
> >> Matthias Schmitt
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >>
> >>
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >>
> >
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJXvLMWAAoJEBzwKT+lPKRYwsgQAJKGwx+rRl8L/PM/rQKX/3Mz
> ml0aYb+9rHeALymvzqy7Q+AcrYZOUqxCnyl9JtYbjIw12QHqUa5KKt2aAS2Uha8B
> H3yOs7cVCW/ZIdYEtyFwDGKvbexM5nXEeE8ZeNn184Qdb+r9bSAZs3mrM3QWxfG3
> aw51J2h0dCEG2sHE7P/N4U/IvbthoI5OSVWsSEB7AJs8GOrHhX9ZJ/KRiY/i5bna
> 5I9BlzOHgCUBDUaD7p2BTBiMSAolB0SA5wT9sm5ITJRUvvBCs/kg1kA6EMJBTX1A
> RNBGlPJus91DthG/a39dcb/PbrXwGpTc4E1g4QtdpVAQEKrmZK7hOrhD9EeYiSOr
> ADyPM7WRNdemdmrJhMmS9gbGfbCSFhFnxKHxeRUBC/lSPCsVFX89CDfCRoqpya6L
> 1scIt0eOC68I40Z6ME/0vVSevtcjvESXBRhPquIKviHYKlEeLpqZ+/0V8wC3sCmG
> 9E3OAPmY5C5EuMtV5XMTT4iojojR0dt73/CZFvvhrc1e2GY0bdgFaXf5/+nGDUcr
> TYuGzPwyQTnJRnBOXfF8i6KiG77OnQ8vE8TtS6CEcVXNusSK2mjf8zxvGcs9Ietw
> 8eqLPPLyWYrnqyXUMBZXa/XJeH8qHZYmBpv4O6xgeYRTcnERC1EJof5KzsXtjDJT
> mueggk9xS2aBwMGgk04M
> =II6y
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to