At first blush, I'd suggest you check your DBMS to see what's happening
with your sessions from WebLogic connections. This one seems blocked
waiting for the DBMS to respond to an update request. It may be rightly
blocked because some other session has the data locked in a transaction,
or it may be a driver/DBMS miscommunication where the DBMS thinks the
client is idle, and the client (driver) hasn't gotten what it needs in a response.
thanks a lot for the response.
if i have to debug this issue...as per you what will be my first step..what parameters should i start looking at.
since eveyday we monitor database...and there are two version of weblogic we have on one machine
one of production application is running through weblogic 8 have more than 500 users and second production application running through weblogic 10 have only 50 users.
we facing problem with application that is running from weblogic 10.
both applications hitting the same database.
our weblogic server is 32bit with total of 4GB and only 1gb we allocated to weblogic 10.
request you to guide me..
I am not sure how you'd go about it, but ask your DBA to
find any sessions that seem blocked for minutes, and what
they are blocked on. You may be able to tell from the
stacktrace what data/SQL the application is doing that's
blocked. That info will help the DBA find who may be holding
locks on that data.