Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Connection Pooling & Cycling DB Servers

 
John Haake
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
One aspect of connection pooling that still troubles me (with errors) is that when we cycle the backend Oracle database once a week for offline backup, the pooled connections go invalid (of course), but when the database is brought back online the pooled connections (in WebSphere AE) seem to all continue to be invalid returning oracle errors "No more data to read from socket" or "Io exception: Broken pipe". Connections (even new ones) continue to return these errors hours after the database was cycled.
My solution has been to cycle WebSphere and all is well again. Is there not a better way? Can't I get WebSphere to automatically re-try establishing the connections? If no access is made during the cycle time I would think the application should never even see an exception.
Help me to understand this.
Thanks
 
John Haake
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Oh, come, come, I know someone out there must have had to deal with this problem. Any ideas?
 
Phil Chuang
Ranch Hand
Posts: 251
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You could build a connection pool wrapper that just checks for certain exceptions, and after x number occur in a row, release and renew all connections?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic