• Post Reply Bookmark Topic Watch Topic
  • New Topic

java.sql.SQLException: Io exception: Broken pipe  RSS feed

 
Suresh Chilakam
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

What could be the reasons for getting the below exception?

java.sql.SQLException: Io exception: Broken pipe

I got this exception in the production twice in the same week and created a huge log file with the exception stack trace until the space available.As a result the production server went down.I was unable to start the production server due to lack of space on the mounted disks. I have deleted very old log files for making some free space and then able to start the production application server and run. I am using connection pooling to connect with Oracle 9i from weblogic 9.2 server. I am willing to know the root cause for this issue.I thought of simulating this issue by restarting the oracle database when the application server(weblogic) is still up and running with the old connection pools.But couldn't simulate the issue again?

Can anyone share your ideas for the possible ways to replicate this exception. Your assistance in finding the root cause for this exception is much appreciated.

Thanks in Advance,
Suresh Chilakam
[ August 07, 2008: Message edited by: Suresh Chilakam ]
 
Marcos Maia
Ranch Hand
Posts: 977
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

usually I've seen this error happening when you have a connection pool set and then your db becames unavailable and then returns, this makes the pool connection invalid and when you try to use them you get this error.
To correct this problem I suggest you to set from admin console for you connection pool at least the following parameters:

check connection on reserve.
Test frequency.
Test Table name and.
Seconds to trust an idle connection pool.

This problably will stop you from getting this kind of error.

To reproduce the problem I suggest you to start the WL Server and after the pool has been created you just reboot your DB server, this will problably make you get this error as it will make connections from the pool invalid.

regards.
 
Suresh Chilakam
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Marcos Maia,

Thank you for your quick response.

I have tried this approach earlier but couldn't simulate the issue.

Thanks,
Suresh Chilakam
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!