Environment: UDB V7.1, AIX 4.3, Weblogic 5.1.0, java programs using JDBC.
Occasionally we get an offending application freezing weblogic up. We are
trying to find ways we can identify the offending one. Executing "list
applications" gives us the following...
Auth Id Application Appl. Application Id
Name Handle
-------- -------------- ---------- ------------------------------
OMISUSER java 108 AA5E2FC2.9E8D.010801143534
OMISUSER java 18 AA5E2FC2.9F8F.010801144211
OMISUSER java 185 AA5E2FC2.9F91.010801144213
With Weblogic's connection pooling the Auth ID and the applications have the
same name making it difficult to identify the offending program
(bean/servlet). Application snapshots don't help either. Any pointers as to
what we could do ?
Tonmoy Dasgupta,
State of Arkansas,
DBA, Dept. of information Systems.
(501)-682-5109
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
