Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1060025 - [abrt] java-1.7.0-openjdk-headless- Uncaught exception java.lang.RuntimeException in method java.util.concurrent.ThreadPoolExecutor.runWorker()
Summary: [abrt] java-1.7.0-openjdk-headless- Uncaught exception ...
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.7.0-openjdk
Version: 20
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:006f6986d59d214378959b831cf...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-31 09:37 UTC by F.Prates
Modified: 2014-02-03 17:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-02-03 17:08:36 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2014-01-31 09:37 UTC, F.Prates
no flags Details
File: environ (deleted)
2014-01-31 09:37 UTC, F.Prates
no flags Details
File: jvm_environment (deleted)
2014-01-31 09:37 UTC, F.Prates
no flags Details

Description F.Prates 2014-01-31 09:37:41 UTC
Description of problem:
Exceptions like that happens often when I'm deploying software using eclipse and apache tomcat.

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.11
cmdline:        java -agentpath:/usr/lib64/ -Djava.util.logging.config.file=/home/francisco.prates/Downloads/apache-tomcat/conf/ -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n -Djava.endorsed.dirs=/home/francisco.prates/Downloads/apache-tomcat/endorsed -classpath /home/francisco.prates/Downloads/apache-tomcat/bin/bootstrap.jar:/home/francisco.prates/Downloads/apache-tomcat/bin/tomcat-juli.jar -Dcatalina.base=/home/francisco.prates/Downloads/apache-tomcat -Dcatalina.home=/home/francisco.prates/Downloads/apache-tomcat org.apache.catalina.startup.Bootstrap start
executable:     /usr/lib/jvm/java-1.7.0-openjdk-
java_executable: /usr/lib/jvm/java-1.7.0-openjdk-
kernel:         3.12.8-300.fc20.x86_64
pid:            2927
runlevel:       N 5
uid:            1000

Truncated backtrace:
Exception in thread "http-bio-8080-exec-1" java.lang.RuntimeException: Stopping thread http-bio-8080-exec-1 to avoid potential memory leaks after a context was stopped.
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.stopCurrentThreadIfNeeded( [jar:file:/home/francisco.prates/Downloads/apache-tomcat/lib/tomcat-coyote.jar!/org/apache/tomcat/util/threads/ThreadPoolExecutor.class]
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.afterExecute( [jar:file:/home/francisco.prates/Downloads/apache-tomcat/lib/tomcat-coyote.jar!/org/apache/tomcat/util/threads/ThreadPoolExecutor.class]
	at java.util.concurrent.ThreadPoolExecutor.runWorker( [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-!/java/util/concurrent/ThreadPoolExecutor.class]
	at java.util.concurrent.ThreadPoolExecutor$ [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-!/java/util/concurrent/ThreadPoolExecutor$Worker.class]
	at [jar:file:/usr/lib/jvm/java-1.7.0-openjdk-!/java/lang/Thread.class]

Comment 1 F.Prates 2014-01-31 09:37:44 UTC
Created attachment 857759 [details]
File: backtrace

Comment 2 F.Prates 2014-01-31 09:37:46 UTC
Created attachment 857760 [details]
File: environ

Comment 3 F.Prates 2014-01-31 09:37:48 UTC
Created attachment 857761 [details]
File: jvm_environment

Comment 4 Jakub Filak 2014-02-03 17:08:36 UTC
ABRT has failed to recognize that this occurred in the 3rd party code from the jar at file://home/francisco.prates/Downloads/apache-tomcat/lib/tomcat-coyote.jar. ABRT let you file this bug report despite the fact that there is nothing we can do to address this and the bug needs to be filed with the developer of that jar/applet.

Closing as CANTFIX. This is a bug but it's not bug in java-1.7.0-openjdk.

Note You need to log in before you can comment on or make changes to this bug.