[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-12-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #25 from jones...@oildex.com --- We'd recently migrated from Weblogic 11g to Tomcat 8/Java 8. We very quickly found this to be a critical problem as well in highly concurrent environment. Glad to have come across it and have the re

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #24 from Alex Koturanov --- (In reply to Mark Thomas from comment #22) > (In reply to Alex Koturanov from comment #21) > > I attached a patch that solves my Tomcat7.0 problem with waiting on lock for > > 3-10 sec in https://bz.apach

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #23 from Mark Thomas --- (In reply to Christopher Schultz from comment #20) > (In reply to Konstantin Kolinko from comment #19) > > This needs > > 1. Refactoring, involving extraction of common parent class. > > > > 2. Implementat

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #22 from Mark Thomas --- (In reply to Alex Koturanov from comment #21) > Is there a use case were WebappClassLoader must not be parallel? Parallel class loading has proved to be unreliable in the past. Until the stability of parall

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #21 from Alex Koturanov --- Is there a use case were WebappClassLoader must not be parallel? Is it an option to re-implement jdk1.7 method java.lang.ClassLoader#getClassLoadingLock(String) directly in WebappClassLoader for Tomcat7.

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #20 from Christopher Schultz --- (In reply to Konstantin Kolinko from comment #19) > (In reply to Christopher Schultz from comment #18) > > > > 2. If the branch is not tolerable at runtime, perhaps the branch can be > > executed a

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #19 from Konstantin Kolinko --- (In reply to Christopher Schultz from comment #18) > > 2. If the branch is not tolerable at runtime, perhaps the branch can be > executed a single time to install a delegate adapter, something like t

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #18 from Christopher Schultz --- The performance hit would only occur during class loading. By the time a few requests have been processed, class loading should have settled-down quite a bit. Some thoughts about performance: 1. Th

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #17 from Alex Koturanov --- Please consider not only the performance impact but also stability of web application. I am seeing 2-10 sec pauses for all requests in my web application caused by some bad code in just one request. --

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 Mark Thomas changed: What|Removed |Added CC||kotur...@amazon.com --- Comment #16 from

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #15 from Mark Thomas --- Oracle's public support has ended for Java 6 but other vendors may have different policies and if you pay Oracle $ you can still get support, updates etc. (and lots of companies do). Using JreCompat looks d

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #14 from Christopher Schultz --- (In reply to Mark Thomas from comment #13) > No. It requires Java 7 and Tomcat 7 has to run on Java 6. Could we wrap some of this capability in Jre7Compat.isSupported()? Lots of folks are running T

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #13 from Mark Thomas --- No. It requires Java 7 and Tomcat 7 has to run on Java 6. -- You are receiving this mail because: You are the assignee for the bug. - To

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-03-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #12 from kotur...@amazon.com --- Hi, is it possible to port this change to Tomcat 7 in /tomcat/tc7.0.x/trunk/java/org/apache/catalina/loader/WebappClassLoader.java ? -- You are receiving this mail because: You are the assignee for

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-02-03 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #11 from Stepan --- The problem occurred in eclipse and context.xml was not loaded properly. Right now everything works good. Thanks for the help. -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-02-03 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #10 from Mark Thomas --- The stack trace shows you aren't using parallel class loading. The lock is on the ClassLoader rather than a class specific object. -- You are receiving this mail because: You are the assignee for the b

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2015-02-03 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #9 from Stepan --- Still not sure the problem is solved. The problem tested in apache-tomcat-8.0.18 with ParallelWebappClassLoader loader. And apache-tomcat-7.0.35 has much better performance. Do you have unit tests to check w

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-09-09 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #8 from Konstantin Kolinko --- Just some documentation notes. As a reference about this new feature. 1. This feature is off by default. 2. To enable it, add the following XML element either to the context file of your web appli

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-09-08 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-07-02 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 Mario Lukica changed: What|Removed |Added CC||mluk...@gmail.com -- You are recei

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 Mark Thomas changed: What|Removed |Added Component|Catalina|Catalina Version|7.0.53

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 Sebastien Tardif changed: What|Removed |Added CC||sebtar...@ncf.ca

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #2 from Sebastien Tardif --- The same issues happen to others -> https://groups.google.com/forum/#!topic/optiq-dev/amCEv1psDrI -- You are receiving this mail because: You are the assignee for the bug.

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #3 from Mark Thomas --- The partial stack trace is largely useless since it does not show what the critical thread (http-bio-31680-exec-41) is doing. When considering any proposed changes, keep this in mind: http://svn.apache.o

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #4 from Sebastien Tardif --- Thanks for the link. It does mentions for an attempt to provide parallel classloading for Tomcat 7 but that doesn't seem to have happened. http-bio-31680-exec-41 is running loading a class. Any of

[Bug 56530] WebappClassLoader.loadClass synchronization issue due to coarse lock at WebappClassLoader instance level instead of been by class name

2014-05-16 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=56530 --- Comment #5 from Sebastien Tardif --- The implementation of GlassFish "working" on JDK 6, is avoiding "systematic" synchronization on the instance, and so that seems to have been enough to be fast, see http://grepcode.com/file/repo1.mave