ent gets a new connection from the pool.
--- On Sat, 21/7/12, Felix Schumacher wrote:
> From: Felix Schumacher
> Subject: Re: java.sql.SQLException: No more data to read from socket
> To: users@tomcat.apache.org
> Date: Saturday, 21 July, 2012, 6:41 PM
> Am Samstag, den 21.07.
Thanks a bunch Daniel for your help. Also for the patience in answering my
question.
The solution to this issue to make Tomcat handle the connection pooling instead
of the application code OR to restart the application servers along with the DB.
--- On Fri, 20/7/12, Daniel Mikusa wrote:
> Fro
.07.2012, 08:44
> +0800 schrieb vijay mathew:
> > For the last 2 failures, this issue appeared on
> Monday and DB gets restarted every Saturday. So I assume
> that this issue has to do something with the DB restart for
> the last 2 failures.
> >
> > However 1 months b
-BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> - -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Vijay,
>
> On 7/19/12 8:25 PM, vijay mathew wrote:
>
> > java.sql.SQLException: No more data to read from socket
> at
> >
> oracle.jdbc.driver.SQLState
> >
> > > > > Are you restarting the Oracle database
> without
> > > restarting
> > > > > your Tomcat instance? Depending on how
> your
> > > > > application gets a database connection
> this could
> > > be an
> &g
32 AM
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Vijar,
>
> On 7/19/12 12:49 AM, vijay mathew wrote:
> > My application is using Tomcat 5.5 It works fine all
> the time
>
> Great.
>
> > however at times when I try to login to the application
the
> > > following link.
> > >
> > > https://commons.apache.org/dbcp/configuration.html
> > >
> > > Dan
> > >
> > >
> > > >
> > > > Thanks and Regards,
> > > > Vijay Mathew
> > >
ag.
>
> > Not sure how we can avoid this situation
>
> If you are using a DataSource, you could try adding
> validation. With DBCP this is done by adding a
> "validationQuery" option. For more details, see the
> following link.
>
> https://commons.apach
Jose,
Tomcat is using JDK 1.5 and its JDBC driver.So I am not sure if I need to
upgrade the JDBC driver.
I suspect that whene DB is getting restarted, the idle connections are being
removed. Not sure how we can avoid this situation
Thanks and Regards,
Vijay Mathew
--- On Thu, 19/7/12, Jose
My application is using Tomcat 5.5 It works fine all the time however at times
when I try to login to the application I get the below exception
java.sql.SQLException: No more data to read from socket
at
oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
at
10 matches
Mail list logo
