• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WSVR0605W exception from Websphere

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
I am getting following error when my database is down
I feel that the webcontainer tries to create the connection from the connection pool which causes the problem , The error is attached below


[11/24/05 6:09:04:356 NZDT] 0000000d ThreadMonitor W WSVR0605W: Thread "WebContainer : 141" (00006e56) has been active for 664301 milliseconds and may be hung. There is/are 41 thread(s) in total in the server that may be hung.
[11/24/05 6:09:04:362 NZDT] 0000000d ThreadMonitor W WSVR0605W: Thread "WebContainer : 129" (00006e3e) has been active for 754053 milliseconds and may be hung. There is/are 42 thread(s) in total in the server that may be hung.
[11/24/05 6:09:04:366 NZDT] 0000000d ThreadMonitor W WSVR0605W: Thread "WebContainer : 138" (00006e4b) has been active for 717419 milliseconds and may be hung. There is/are 43 thread(s) in total in the server that may be hung.


How can i solve this ,
Please let me know how to solve this

Thanks in Advance

Rajesh Kartha
 
author
Posts: 4335
39
jQuery Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What is your desired behavior? If the database is down, then what you prefer to happen?
 
Ranch Hand
Posts: 179
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hmmmmmmmmmmmmm.....

WAS will increase the connections in the connection pool up to the specified limit. The default is 10.

Looks like the app is creating multiple threads in the JVM, each waiting for a lock on a resource, in this case a connection in the connection pool and not releasing the connection when the db is not available. The app should time out.
 
Greenhorn
Posts: 6
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Threads in Java EE are a no-go! Probably the connection (and hence the threads) are not properly closed (terminated).
Please use Asynchronous Methods or Work Managers in WebSphere instead of threads. Or in your case - use JDBC Connection pools correctly!

This post explains how to use asynchronous Methods in WebSphere
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic