File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes WSVR0605W exception from Websphere Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WSVR0605W exception from Websphere" Watch "WSVR0605W exception from Websphere" New topic
Author

WSVR0605W exception from Websphere

rajesh kartha
Greenhorn

Joined: Jun 29, 2005
Posts: 7
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
Scott Selikoff
author
Saloon Keeper

Joined: Oct 23, 2005
Posts: 3716
    
    5

What is your desired behavior? If the database is down, then what you prefer to happen?


My Blog: Down Home Country Coding with Scott Selikoff
Patrick Finnegan
Ranch Hand

Joined: Mar 05, 2002
Posts: 179
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.
Marcel Friedmann
Greenhorn

Joined: Nov 07, 2014
Posts: 6
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
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WSVR0605W exception from Websphere