my dog learned polymorphism*
The moose likes Websphere and the fly likes Application hangs with prior J2CA0086W warning messages Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Application hangs with prior J2CA0086W warning messages" Watch "Application hangs with prior J2CA0086W warning messages" New topic

Application hangs with prior J2CA0086W warning messages

Anand Gondhiya
Ranch Hand

Joined: Feb 24, 2004
Posts: 155
my application hangs while executing a Stored proc or select/insert/update SQL statements. I am using WebSphere App server 5.1 and WSAD

Case 1 ata Source/Connection pool
I had set up sharable Data source.and It always worked fine.I am making sure that I am closing connections after using them. Suddenly , application started hanging. I increased max connections from 10 to 100 but no diffrence.Application hangs with prior J2CA0086W warning messages.
for more info:
There is no diffrence in behaviour if I restart WebSphere App server or restart WSAD. However ,after rebooting application works fine for first time. and then onwards , It hangs.

Case 2: DriverManager
Before I set up connection pool/Data Source ,Application worked fine with Driver manager. But after switching back from DataSource/Conn Pool , my application hangs even if I use DriverManager.

Can anyone advise ?
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968

Are there any firewalls between the app server and the database?

Can you post your datasource settings? Are there anything peculiar there?

-Cameron McKenzie
I agree. Here's the link:
subject: Application hangs with prior J2CA0086W warning messages
Similar Threads
Oracle data types and WebSphere Connection Pool
use of commons-logging under was 5.0
Oracle-specific data types and WAS conn pool
ArrayDescriptor and java Connection
WAS commons-logging problem SOLVED (without PARENT_LAST)