You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2017/03/15 09:52:49 UTC

[Bug 60867] New: Tomcat stops unexpectedly- Deadlock in thread dump

https://bz.apache.org/bugzilla/show_bug.cgi?id=60867

            Bug ID: 60867
           Summary: Tomcat stops unexpectedly- Deadlock in thread dump
           Product: Tomcat 7
           Version: 7.0.23
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Connectors
          Assignee: dev@tomcat.apache.org
          Reporter: preeti.negi88@gmail.com
  Target Milestone: ---

Created attachment 34828
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34828&action=edit
Thread dump

Hi All,

Our application installed on linux server is using Apache Tomcat 7.0.23. Once
in every 15 days(sometimes before) it stops unexpectedly with no exceptions. We
took thread dump and found out one deadlock which could be the reason of
unresponsive application.

"http-bio-8080-exec-6457" daemon prio=10 tid=0x00007fbec04fc800 nid=0x5739
waiting for monitor entry [0x00007fbea1c33000]
waiting to lock <0x00007fbeefcb53e0> (a [Ljava.util.jar.JarFile;)

Setting for connector

<Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" URIEncoding="UTF-8" />

Find attached thread dump.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 60867] Tomcat stops unexpectedly- Deadlock in thread dump

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60867

--- Comment #5 from mgrigorov <mg...@apache.org> ---
Please read http://tomcat.apache.org/lists.html#tomcat-users.
The users mailing list is the place where to ask how to use Tomcat, how to
configure it, etc. You can also answer someone else's questions if you know the
answer.
Bugzilla is used for bug reports and enhancement requests.
It is always better to discuss the bug/enhancement in the mailing lists first.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 60867] Tomcat stops unexpectedly- Deadlock in thread dump

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60867

--- Comment #4 from Preeti Negi <pr...@gmail.com> ---
(In reply to Mark Thomas from comment #3)
> (In reply to Preeti Negi from comment #2)
> > (In reply to Remy Maucherat from comment #1)
> > > I don't see a deadlock there, the other thread holding the lock for
> > > 0x00007fbeefcb53e0 will proceed and release it at some point.
> > > 
> > > Please investigate the performance issue on the user mailing list instead.
> 
> Indeed. There is no bug here.
> 
> > I could see similar problems:
> 
> Those are not similar. Help with how to read thread dumps is available via
> the users list.
> 
> <snip/>
> 
> > And the thread is in blocked state.
> 
> BLOCKED != deadlock
> 
> This belongs on the users mailing list.

Yes my mistake I wrote Deadlock instead of BLOCKED.

But from online dump analyzer, it says, it could be a reason of unresponsive
application.

I am new here. Kindly tell me what is users mailing list ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 60867] Tomcat stops unexpectedly- Deadlock in thread dump

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60867

--- Comment #2 from Preeti Negi <pr...@gmail.com> ---
(In reply to Remy Maucherat from comment #1)
> I don't see a deadlock there, the other thread holding the lock for
> 0x00007fbeefcb53e0 will proceed and release it at some point.
> 
> Please investigate the performance issue on the user mailing list instead.

I could see similar problems:

https://bz.apache.org/bugzilla/show_bug.cgi?id=57779

https://bz.apache.org/bugzilla/show_bug.cgi?id=53173

And the thread is in blocked state.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 60867] Tomcat stops unexpectedly- Deadlock in thread dump

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60867

--- Comment #3 from Mark Thomas <ma...@apache.org> ---
(In reply to Preeti Negi from comment #2)
> (In reply to Remy Maucherat from comment #1)
> > I don't see a deadlock there, the other thread holding the lock for
> > 0x00007fbeefcb53e0 will proceed and release it at some point.
> > 
> > Please investigate the performance issue on the user mailing list instead.

Indeed. There is no bug here.

> I could see similar problems:

Those are not similar. Help with how to read thread dumps is available via the
users list.

<snip/>

> And the thread is in blocked state.

BLOCKED != deadlock

This belongs on the users mailing list.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 60867] Tomcat stops unexpectedly- Deadlock in thread dump

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60867

Remy Maucherat <re...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Remy Maucherat <re...@apache.org> ---
I don't see a deadlock there, the other thread holding the lock for
0x00007fbeefcb53e0 will proceed and release it at some point.

Please investigate the performance issue on the user mailing list instead.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org