[jboss-jira] [JBoss JIRA] (JASSIST-150) Performance problem with loading classes under certain circumstances

[Nikita Tovstoles (JIRA)]

    [ https://issues.jboss.org/browse/JASSIST-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680619#comment-12680619 ] 

Nikita Tovstoles commented on JASSIST-150:
------------------------------------------

Hello,

I just checked out trunk (rev 626) and 'mvn clean install' periodically fails testJIRA150b (seemingly 9 out of 10 times). Is that expected?

{noformat}

-------------------------------------------------------------------------------
Test set: javassist.JvstTest
-------------------------------------------------------------------------------
Tests run: 295, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.902 sec <<< FAILURE!
testJIRA150b(javassist.JvstTest4)  Time elapsed: 1.807 sec  <<< FAILURE!
junit.framework.AssertionFailedError
	at junit.framework.Assert.fail(Assert.java:47)
	at junit.framework.Assert.assertTrue(Assert.java:20)
	at junit.framework.Assert.assertTrue(Assert.java:27)
	at javassist.JvstTest4.testJIRA150b(JvstTest4.java:688)
{noformat}
                
> Performance problem with loading classes under certain circumstances
> --------------------------------------------------------------------
>
>                 Key: JASSIST-150
>                 URL: https://issues.jboss.org/browse/JASSIST-150
>             Project: Javassist
>          Issue Type: Enhancement
>    Affects Versions: 3.15.0-GA
>            Reporter: Bruce Garner
>            Assignee: Shigeru Chiba
>             Fix For: 3.16.0-GA
>
>         Attachments: Jassist150.java, Javassist150src.zip
>
>
> There is a performance problem in the class loading in javassist.  Under certain circumastance the parse of the code will mean that javassist will attempt to load classes starting at the base of the package, and get failures for the package base until it finds the class. There is no caching of this failure so each attempt to load the class searches the entire classpath and fails.
> Unfortunately the code in PowerMock exercises this bug, and in large systems with may items on the classpath, large numbers of classes and large classes the process can be slow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira