aspose file tools
The moose likes Beginning Java and the fly likes COMPILATION KILLED BY CONCURRENT CLASS LOADING : index = 1 Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Java » Beginning Java
Reply Bookmark "COMPILATION KILLED BY CONCURRENT CLASS LOADING : index = 1" Watch "COMPILATION KILLED BY CONCURRENT CLASS LOADING : index = 1" New topic
Author

COMPILATION KILLED BY CONCURRENT CLASS LOADING : index = 1

NaChuan Chen
Greenhorn

Joined: Jul 11, 2005
Posts: 2
Hi all,

I met a lot of this error messages in my application log file:
COMPILATION KILLED BY CONCURRENT CLASS LOADING : index = 1
Could anybody explain:
How could they occur?
What effects can it cause to the system?
How to avoid it?

thannk in advance!
Stuart Gray
Ranch Hand

Joined: Apr 21, 2005
Posts: 410
Sounds like a custom error message from your application (perhaps from a failed assertion or an exception). You will likely need to read the docs (or the source!) to find out where and why this message is generated. What program caused this anyway?
Ernest Friedman-Hill
author and iconoclast
Marshal

Joined: Jul 08, 2003
Posts: 24045
    
  13

It sounds like something a JSP container might say. Look in our "Products" section and find the forum appropriate to your app server, and post this question there -- maybe somebody knows more.


[Jess in Action][AskingGoodQuestions]
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: COMPILATION KILLED BY CONCURRENT CLASS LOADING : index = 1
 
Similar Threads
Which three occur during JSP page translationf
Variable Scope
data access class
String tokenizer
java.util.concurrent in JDK 1.4