[ http://issues.apache.org/jira/browse/SANDBOX-27?page=all ]
Henri Yandell updated SANDBOX-27:
---------------------------------
Component: JCI
> JCI: CompilingClassLoader race conditions
> -----------------------------------------
>
> Key: SANDBOX-27
> URL: http://issues.apache.org/jira/browse/SANDBOX-27
> Project: Commons Sandbox
> Type: Bug
> Components: JCI
> Environment: Operating System: other
> Platform: Other
> Reporter: Patrick Lightbody
>
> Right now, when you create a new classloader, the FilesystemAlterationMonitor
> kicks off. However, it may not get done loading classes before the application
> using the CL requests one of those classes. Currently, the parent CL will be
> used, and from that point on everything gets goofed.
> I suggest changing the CLs such that when they are created, they block until
> they have made an initial pass through the directories. I was able to hack
> this
> by taking the FilesystemAlterationMonitor.run() method (the part inside the
> loop) and refactoring it to doRun() and then calling that right after creating
> the class. Ghetto, but it seemed to help.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
