[ http://jira.jboss.com/jira/browse/JBAS-1147?page=history ]

Adrian Brock updated JBAS-1147:
-------------------------------

    Description: 
SourceForge Submitter: sflexus .
It is very good that ApplicationDeadlockException is now 
very verbose. However, it would make finding the 
deadlock cause a piece of cake if it also would include 
stack trace of the other (waiting) thread. If the 
application is complex, only knowing two bean names is 
not enough for me to guess where was the other place 
that current transaction deadlocked with.

  was:
SourceForge Submitter: sflexus .
It is very good that ApplicationDeadlockException is now 
very verbose. However, it would make finding the 
deadlock cause a piece of cake if it also would include 
stack trace of the other (waiting) thread. If the 
application is complex, only knowing two bean names is 
not enough for me to guess where was the other place 
that current transaction deadlocked with.

    Environment: 
      Component: EJBs

> DeadockDetection: print stack trace of waitingResource?
> -------------------------------------------------------
>
>          Key: JBAS-1147
>          URL: http://jira.jboss.com/jira/browse/JBAS-1147
>      Project: JBoss Application Server
>         Type: Feature Request
>   Components: EJBs
>     Versions: JBossAS-3.2.6 Final
>     Reporter: SourceForge User
>     Assignee: Scott M Stark

>
>
> SourceForge Submitter: sflexus .
> It is very good that ApplicationDeadlockException is now 
> very verbose. However, it would make finding the 
> deadlock cause a piece of cake if it also would include 
> stack trace of the other (waiting) thread. If the 
> application is complex, only knowing two bean names is 
> not enough for me to guess where was the other place 
> that current transaction deadlocked with.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to