Home » Archived » Test and Performance Tools Platform (TPTP) » Profiling a JUnit 4 test fails with NoClassDefFoundError CbeProbe_probe$Probe_0
| Profiling a JUnit 4 test fails with NoClassDefFoundError CbeProbe_probe$Probe_0 [message #115763] |
Wed, 17 October 2007 12:17  |
Eclipse User |
|
|
|
Originally posted by: wrobinson.gsu.edu
I am unable to Profile a JUnit 4 test. I read through the other posts on
this kind of problem, and it seems the error I have is a bit different. I'm
using the latest TPTP to date, 4.3.x.
I can run JUnit or Profile without any problem. However, when I Profile a
JUnit test, I get a NoClassDefFoundError for the probe class
CbeProbe_probe$Probe_0.
Select Open Profile Dialog and select a JUnit test with the JUnit 4 test
runner.
Under the Monitor tab, select one of the three Instrument Collectors (JME,
CBE, ARM). Selecting any one the produces the same kind of error: a
NoClassDefFoundError related to the probe class (from one of the 3 jar
files)
I did find the missing probe class in a TPTP plugin
(org.eclipse.tptp.monitoring.instrumentation_4.3.0). However, including the
jar in the class or build paths does not change the error message.
Here's the stacktace for the CBE error:
java.lang.NoClassDefFoundError: CbeProbe_probe$Probe_0
at $Proxy0.<clinit>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588)
at
sun.reflect.annotation.AnnotationParser.annotationForMap(Ann otationParser.java:239)
at
sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:229)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
at java.lang.Class.getAnnotation(Class.java:2989)
at sun.reflect.annotation.AnnotationType.<init>(AnnotationType.java:104)
at
sun.reflect.annotation.AnnotationType.getInstance(Annotation Type.java:64)
at
sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:202)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
at
sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
at java.lang.reflect.Method.declaredAnnotations(Method.java:676 )
at java.lang.reflect.Method.getAnnotation(Method.java:663)
at
org.junit.internal.runners.TestIntrospector.getTestMethods(T estIntrospector.java:28)
at
org.junit.internal.runners.TestClassMethodsRunner.<init>(TestClassMethodsRunner.java:27)
at
org.junit.internal.runners.TestClassRunner.<init>(TestClassRunner.java:20)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
at
org.junit.internal.requests.ClassRequest.buildRunner(ClassRe quest.java:33)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequ est.java:28)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init >(JUnit4TestReference.java:26)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassRefere nce. <init>(JUnit4TestClassReference.java:24)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.crea teTest(JUnit4TestLoader.java:40)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.load Tests(JUnit4TestLoader.java:30)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:445)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
|
|
|
| Re: Profiling a JUnit 3.8 with CBE instrumentation fails with NullPointerException [message #115817 is a reply to message #115763] |
Wed, 17 October 2007 14:34  |
| Eclipse User |
|
|
|
Originally posted by: wrobinson.gsu.edu
After converting the test to JUnit 3.8, the JMX and ARM Instrument Collector
options run within out error. So, Profiling a Junit 3.8 test works! (I didn't
notice that JUnit 4 will be supported in a later release.)
However, using the CBE Instrument Collector option generates a (new) error:
java.lang.NullPointerException
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.getMethodParamInfo(InstrumentEvent Helpers.java:42)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeDataMapping. <init>(CbeDataMapping.java:43)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleEvent(CbeInstrument.java:169)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleMethodEntryEvent(CbeInstrument.java:1 00)
at CbeProbe_probe$Probe_0._entry(CbeProbe_probe.java:29)
at org.reqmon.samples.tptp.simple.Test.assertFalsePevalsEquals( Test.java)
at
org.reqmon.samples.tptp.simple.OCLTestExample.testFalsePrope rty(OCLTestExample.java:22)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestRefer ence.run(JUnit3TestReference.java:130)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(Test Execution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
<wrobinson@gsu.edu> wrote in message news:ff4uh1$3em$1@build.eclipse.org...
>I am unable to Profile a JUnit 4 test. I read through the other posts on
>this kind of problem, and it seems the error I have is a bit different.
>I'm using the latest TPTP to date, 4.3.x.
>
> I can run JUnit or Profile without any problem. However, when I Profile a
> JUnit test, I get a NoClassDefFoundError for the probe class
> CbeProbe_probe$Probe_0.
>
> Select Open Profile Dialog and select a JUnit test with the JUnit 4 test
> runner.
> Under the Monitor tab, select one of the three Instrument Collectors (JME,
> CBE, ARM). Selecting any one the produces the same kind of error: a
> NoClassDefFoundError related to the probe class (from one of the 3 jar
> files)
> I did find the missing probe class in a TPTP plugin
> (org.eclipse.tptp.monitoring.instrumentation_4.3.0). However, including
> the jar in the class or build paths does not change the error message.
>
> Here's the stacktace for the CBE error:
>
> java.lang.NoClassDefFoundError: CbeProbe_probe$Probe_0
> at $Proxy0.<clinit>(Unknown Source)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588)
> at
> sun.reflect.annotation.AnnotationParser.annotationForMap(Ann otationParser.java:239)
> at
> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:229)
> at
> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
> at
> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
> at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
> at java.lang.Class.getAnnotation(Class.java:2989)
> at sun.reflect.annotation.AnnotationType.<init>(AnnotationType.java:104)
> at
> sun.reflect.annotation.AnnotationType.getInstance(Annotation Type.java:64)
> at
> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:202)
> at
> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
> at
> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
> at java.lang.reflect.Method.declaredAnnotations(Method.java:676 )
> at java.lang.reflect.Method.getAnnotation(Method.java:663)
> at
> org.junit.internal.runners.TestIntrospector.getTestMethods(T estIntrospector.java:28)
> at
> org.junit.internal.runners.TestClassMethodsRunner.<init>(TestClassMethodsRunner.java:27)
> at
> org.junit.internal.runners.TestClassRunner.<init>(TestClassRunner.java:20)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
> at
> org.junit.internal.requests.ClassRequest.buildRunner(ClassRe quest.java:33)
> at
> org.junit.internal.requests.ClassRequest.getRunner(ClassRequ est.java:28)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init >(JUnit4TestReference.java:26)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassRefere nce. <init>(JUnit4TestClassReference.java:24)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.crea teTest(JUnit4TestLoader.java:40)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.load Tests(JUnit4TestLoader.java:30)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:445)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>
>
>
|
|
|
| CBE instrumentation error: fails on RMI [message #115830 is a reply to message #115817] |
Wed, 17 October 2007 15:19 |
| Eclipse User |
|
|
|
Originally posted by: wrobinson.gsu.edu
I believe that I have narrowed the problem to the CBE Instrument Collector.
It appears that the CBE Instrument Collector does not work well with RMI. I
have used filters to attempt to prevent CBE from tracing all methods except
those in my local client. However, when the client uses RMI to call a server
to get a result, CBE also traces that call
(org.reqmon.junit3.Test.countPevals below) and then throws an error.
java.lang.ClassCastException: java.lang.Integer
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateObjectToString(Instrume ntEventHelpers.java:221)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateArrayToStringArray(Inst rumentEventHelpers.java:235)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.setSimpleValue(InstrumentEventHelp ers.java:172)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.appendChildExtendedDataElement(Ins trumentEventHelpers.java:103)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertObjectsToExtenedDataElement (InstrumentEventHelpers.java:82)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleEvent(CbeInstrument.java:189)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleMethodEntryEvent(CbeInstrument.java:1 00)
at CbeProbe_probe$Probe_0._entry(CbeProbe_probe.java:29)
at $Proxy0.countQueryResults(Unknown Source)
at org.reqmon.junit3.Test.countPevals(Test.java:37)
at org.reqmon.junit3.Test.assertFalsePevalsEquals(Test.java:18)
at
org.reqmon.samples.tptp.simple.OCLTestExample.testFalsePrope rty(OCLTestExample.java:24)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestRefer ence.run(JUnit3TestReference.java:130)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(Test Execution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
<wrobinson@gsu.edu> wrote in message news:ff56i5$13r$1@build.eclipse.org...
> After converting the test to JUnit 3.8, the JMX and ARM Instrument
> Collector options run within out error. So, Profiling a Junit 3.8 test
> works! (I didn't notice that JUnit 4 will be supported in a later
> release.)
> However, using the CBE Instrument Collector option generates a (new)
> error:
>
> java.lang.NullPointerException
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.getMethodParamInfo(InstrumentEvent Helpers.java:42)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeDataMapping. <init>(CbeDataMapping.java:43)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleEvent(CbeInstrument.java:169)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleMethodEntryEvent(CbeInstrument.java:1 00)
> at CbeProbe_probe$Probe_0._entry(CbeProbe_probe.java:29)
> at org.reqmon.samples.tptp.simple.Test.assertFalsePevalsEquals( Test.java)
> at
> org.reqmon.samples.tptp.simple.OCLTestExample.testFalsePrope rty(OCLTestExample.java:22)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestRefer ence.run(JUnit3TestReference.java:130)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(Test Execution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:460)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>
>
> <wrobinson@gsu.edu> wrote in message
> news:ff4uh1$3em$1@build.eclipse.org...
>>I am unable to Profile a JUnit 4 test. I read through the other posts on
>>this kind of problem, and it seems the error I have is a bit different.
>>I'm using the latest TPTP to date, 4.3.x.
>>
>> I can run JUnit or Profile without any problem. However, when I Profile a
>> JUnit test, I get a NoClassDefFoundError for the probe class
>> CbeProbe_probe$Probe_0.
>>
>> Select Open Profile Dialog and select a JUnit test with the JUnit 4 test
>> runner.
>> Under the Monitor tab, select one of the three Instrument Collectors
>> (JME, CBE, ARM). Selecting any one the produces the same kind of error: a
>> NoClassDefFoundError related to the probe class (from one of the 3 jar
>> files)
>> I did find the missing probe class in a TPTP plugin
>> (org.eclipse.tptp.monitoring.instrumentation_4.3.0). However, including
>> the jar in the class or build paths does not change the error message.
>>
>> Here's the stacktace for the CBE error:
>>
>> java.lang.NoClassDefFoundError: CbeProbe_probe$Probe_0
>> at $Proxy0.<clinit>(Unknown Source)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
>> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588)
>> at
>> sun.reflect.annotation.AnnotationParser.annotationForMap(Ann otationParser.java:239)
>> at
>> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:229)
>> at
>> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
>> at
>> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
>> at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
>> at java.lang.Class.getAnnotation(Class.java:2989)
>> at sun.reflect.annotation.AnnotationType.<init>(AnnotationType.java:104)
>> at
>> sun.reflect.annotation.AnnotationType.getInstance(Annotation Type.java:64)
>> at
>> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:202)
>> at
>> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
>> at
>> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
>> at java.lang.reflect.Method.declaredAnnotations(Method.java:676 )
>> at java.lang.reflect.Method.getAnnotation(Method.java:663)
>> at
>> org.junit.internal.runners.TestIntrospector.getTestMethods(T estIntrospector.java:28)
>> at
>> org.junit.internal.runners.TestClassMethodsRunner.<init>(TestClassMethodsRunner.java:27)
>> at
>> org.junit.internal.runners.TestClassRunner.<init>(TestClassRunner.java:20)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
>> at
>> org.junit.internal.requests.ClassRequest.buildRunner(ClassRe quest.java:33)
>> at
>> org.junit.internal.requests.ClassRequest.getRunner(ClassRequ est.java:28)
>> at
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init >(JUnit4TestReference.java:26)
>> at
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassRefere nce. <init>(JUnit4TestClassReference.java:24)
>> at
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.crea teTest(JUnit4TestLoader.java:40)
>> at
>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.load Tests(JUnit4TestLoader.java:30)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:445)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>>
>>
>>
>
|
|
|
| CBE instrumentation error: InstrumentEventHelpers apparently incorrectly applies convertDateArrayToS [message #115843 is a reply to message #115830] |
Wed, 17 October 2007 15:31 |
| Eclipse User |
|
|
|
Originally posted by: wrobinson.gsu.edu
Sorry to go on about this, but someone else may have the same problem.
The error appears to be in InstrumentEventHelpers.java:172. There it
incorrectly applies convertDateArrayToStringArray to the following arg list
of objects (in my method):
public int countQueryResults(String query, Object... args) throws
RemoteException;
I don't know why, but it may be that, by default, it converts object lists
using the convertDateArrayToStringArray method. I have observed this error
for different types of objects passed to countQueryResults(String query,
Object... args).
java.lang.ClassCastException: java.lang.Integer
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateObjectToString(Instrume ntEventHelpers.java:221)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateArrayToStringArray(Inst rumentEventHelpers.java:235)
at
org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.setSimpleValue(InstrumentEventHelp ers.java:172)
<wrobinson@gsu.edu> wrote in message news:ff595k$al5$1@build.eclipse.org...
>I believe that I have narrowed the problem to the CBE Instrument Collector.
>It appears that the CBE Instrument Collector does not work well with RMI. I
>have used filters to attempt to prevent CBE from tracing all methods except
>those in my local client. However, when the client uses RMI to call a
>server to get a result, CBE also traces that call
>(org.reqmon.junit3.Test.countPevals below) and then throws an error.
>
> java.lang.ClassCastException: java.lang.Integer
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateObjectToString(Instrume ntEventHelpers.java:221)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateArrayToStringArray(Inst rumentEventHelpers.java:235)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.setSimpleValue(InstrumentEventHelp ers.java:172)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.appendChildExtendedDataElement(Ins trumentEventHelpers.java:103)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertObjectsToExtenedDataElement (InstrumentEventHelpers.java:82)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleEvent(CbeInstrument.java:189)
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleMethodEntryEvent(CbeInstrument.java:1 00)
> at CbeProbe_probe$Probe_0._entry(CbeProbe_probe.java:29)
> at $Proxy0.countQueryResults(Unknown Source)
> at org.reqmon.junit3.Test.countPevals(Test.java:37)
> at org.reqmon.junit3.Test.assertFalsePevalsEquals(Test.java:18)
> at
> org.reqmon.samples.tptp.simple.OCLTestExample.testFalsePrope rty(OCLTestExample.java:24)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:232)
> at junit.framework.TestSuite.run(TestSuite.java:227)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestRefer ence.run(JUnit3TestReference.java:130)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(Test Execution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:460)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>
>
>
> <wrobinson@gsu.edu> wrote in message
> news:ff56i5$13r$1@build.eclipse.org...
>> After converting the test to JUnit 3.8, the JMX and ARM Instrument
>> Collector options run within out error. So, Profiling a Junit 3.8 test
>> works! (I didn't notice that JUnit 4 will be supported in a later
>> release.)
>> However, using the CBE Instrument Collector option generates a (new)
>> error:
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.getMethodParamInfo(InstrumentEvent Helpers.java:42)
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeDataMapping. <init>(CbeDataMapping.java:43)
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleEvent(CbeInstrument.java:169)
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleMethodEntryEvent(CbeInstrument.java:1 00)
>> at CbeProbe_probe$Probe_0._entry(CbeProbe_probe.java:29)
>> at org.reqmon.samples.tptp.simple.Test.assertFalsePevalsEquals( Test.java)
>> at
>> org.reqmon.samples.tptp.simple.OCLTestExample.testFalsePrope rty(OCLTestExample.java:22)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at junit.framework.TestCase.runTest(TestCase.java:168)
>> at junit.framework.TestCase.runBare(TestCase.java:134)
>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>> at junit.framework.TestResult.run(TestResult.java:113)
>> at junit.framework.TestCase.run(TestCase.java:124)
>> at junit.framework.TestSuite.runTest(TestSuite.java:232)
>> at junit.framework.TestSuite.run(TestSuite.java:227)
>> at
>> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestRefer ence.run(JUnit3TestReference.java:130)
>> at
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(Test Execution.java:38)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:460)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>>
>>
>> <wrobinson@gsu.edu> wrote in message
>> news:ff4uh1$3em$1@build.eclipse.org...
>>>I am unable to Profile a JUnit 4 test. I read through the other posts on
>>>this kind of problem, and it seems the error I have is a bit different.
>>>I'm using the latest TPTP to date, 4.3.x.
>>>
>>> I can run JUnit or Profile without any problem. However, when I Profile
>>> a JUnit test, I get a NoClassDefFoundError for the probe class
>>> CbeProbe_probe$Probe_0.
>>>
>>> Select Open Profile Dialog and select a JUnit test with the JUnit 4 test
>>> runner.
>>> Under the Monitor tab, select one of the three Instrument Collectors
>>> (JME, CBE, ARM). Selecting any one the produces the same kind of error:
>>> a NoClassDefFoundError related to the probe class (from one of the 3 jar
>>> files)
>>> I did find the missing probe class in a TPTP plugin
>>> (org.eclipse.tptp.monitoring.instrumentation_4.3.0). However, including
>>> the jar in the class or build paths does not change the error message.
>>>
>>> Here's the stacktace for the CBE error:
>>>
>>> java.lang.NoClassDefFoundError: CbeProbe_probe$Probe_0
>>> at $Proxy0.<clinit>(Unknown Source)
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
>>> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588)
>>> at
>>> sun.reflect.annotation.AnnotationParser.annotationForMap(Ann otationParser.java:239)
>>> at
>>> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:229)
>>> at
>>> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
>>> at
>>> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
>>> at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
>>> at java.lang.Class.getAnnotation(Class.java:2989)
>>> at sun.reflect.annotation.AnnotationType.<init>(AnnotationType.java:104)
>>> at
>>> sun.reflect.annotation.AnnotationType.getInstance(Annotation Type.java:64)
>>> at
>>> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:202)
>>> at
>>> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
>>> at
>>> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
>>> at java.lang.reflect.Method.declaredAnnotations(Method.java:676 )
>>> at java.lang.reflect.Method.getAnnotation(Method.java:663)
>>> at
>>> org.junit.internal.runners.TestIntrospector.getTestMethods(T estIntrospector.java:28)
>>> at
>>> org.junit.internal.runners.TestClassMethodsRunner.<init>(TestClassMethodsRunner.java:27)
>>> at
>>> org.junit.internal.runners.TestClassRunner.<init>(TestClassRunner.java:20)
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
>>> at
>>> org.junit.internal.requests.ClassRequest.buildRunner(ClassRe quest.java:33)
>>> at
>>> org.junit.internal.requests.ClassRequest.getRunner(ClassRequ est.java:28)
>>> at
>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init >(JUnit4TestReference.java:26)
>>> at
>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassRefere nce. <init>(JUnit4TestClassReference.java:24)
>>> at
>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.crea teTest(JUnit4TestLoader.java:40)
>>> at
>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.load Tests(JUnit4TestLoader.java:30)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:445)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>>>
>>>
>>>
>>
>
|
|
|
| Re: CBE instrumentation error: InstrumentEventHelpers apparently incorrectly applies convertDateArra [message #116154 is a reply to message #115843] |
Mon, 22 October 2007 14:03 |
 Richard Y.S. HUANG
Messages: 18
Registered: July 2009 |
Junior Member |
|
|
Hi wrobinson,
I have opened a defect in Eclipse bugzilla system to trace this problem:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=207054
You can add yourself in the defect's cc list to watch it.
Richard Huang
wrobinson@gsu.edu wrote:
> Sorry to go on about this, but someone else may have the same problem.
>
> The error appears to be in InstrumentEventHelpers.java:172. There it
> incorrectly applies convertDateArrayToStringArray to the following arg
> list of objects (in my method):
>
> public int countQueryResults(String query, Object... args) throws
> RemoteException;
>
> I don't know why, but it may be that, by default, it converts object
> lists using the convertDateArrayToStringArray method. I have observed
> this error for different types of objects passed to
> countQueryResults(String query, Object... args).
>
> java.lang.ClassCastException: java.lang.Integer
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateObjectToString(Instrume ntEventHelpers.java:221)
>
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateArrayToStringArray(Inst rumentEventHelpers.java:235)
>
> at
> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.setSimpleValue(InstrumentEventHelp ers.java:172)
>
>
> <wrobinson@gsu.edu> wrote in message news:ff595k$al5$1@build.eclipse.org...
>> I believe that I have narrowed the problem to the CBE Instrument
>> Collector. It appears that the CBE Instrument Collector does not work
>> well with RMI. I have used filters to attempt to prevent CBE from
>> tracing all methods except those in my local client. However, when the
>> client uses RMI to call a server to get a result, CBE also traces that
>> call (org.reqmon.junit3.Test.countPevals below) and then throws an error.
>>
>> java.lang.ClassCastException: java.lang.Integer
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateObjectToString(Instrume ntEventHelpers.java:221)
>>
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertDateArrayToStringArray(Inst rumentEventHelpers.java:235)
>>
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.setSimpleValue(InstrumentEventHelp ers.java:172)
>>
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.appendChildExtendedDataElement(Ins trumentEventHelpers.java:103)
>>
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.convertObjectsToExtenedDataElement (InstrumentEventHelpers.java:82)
>>
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleEvent(CbeInstrument.java:189)
>>
>> at
>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleMethodEntryEvent(CbeInstrument.java:1 00)
>>
>> at CbeProbe_probe$Probe_0._entry(CbeProbe_probe.java:29)
>> at $Proxy0.countQueryResults(Unknown Source)
>> at org.reqmon.junit3.Test.countPevals(Test.java:37)
>> at org.reqmon.junit3.Test.assertFalsePevalsEquals(Test.java:18)
>> at
>> org.reqmon.samples.tptp.simple.OCLTestExample.testFalsePrope rty(OCLTestExample.java:24)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at junit.framework.TestCase.runTest(TestCase.java:168)
>> at junit.framework.TestCase.runBare(TestCase.java:134)
>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>> at junit.framework.TestResult.run(TestResult.java:113)
>> at junit.framework.TestCase.run(TestCase.java:124)
>> at junit.framework.TestSuite.runTest(TestSuite.java:232)
>> at junit.framework.TestSuite.run(TestSuite.java:227)
>> at
>> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestRefer ence.run(JUnit3TestReference.java:130)
>>
>> at
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(Test Execution.java:38)
>>
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:460)
>>
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
>>
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
>>
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>>
>>
>>
>>
>> <wrobinson@gsu.edu> wrote in message
>> news:ff56i5$13r$1@build.eclipse.org...
>>> After converting the test to JUnit 3.8, the JMX and ARM Instrument
>>> Collector options run within out error. So, Profiling a Junit 3.8
>>> test works! (I didn't notice that JUnit 4 will be supported in a
>>> later release.)
>>> However, using the CBE Instrument Collector option generates a (new)
>>> error:
>>>
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.InstrumentEventHelpers.getMethodParamInfo(InstrumentEvent Helpers.java:42)
>>>
>>> at
>>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeDataMapping. <init>(CbeDataMapping.java:43)
>>>
>>> at
>>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleEvent(CbeInstrument.java:169)
>>>
>>> at
>>> org.eclipse.tptp.monitoring.instrumentation.internal.cbe.mod el.CbeInstrument.handleMethodEntryEvent(CbeInstrument.java:1 00)
>>>
>>> at CbeProbe_probe$Probe_0._entry(CbeProbe_probe.java:29)
>>> at
>>> org.reqmon.samples.tptp.simple.Test.assertFalsePevalsEquals( Test.java)
>>> at
>>> org.reqmon.samples.tptp.simple.OCLTestExample.testFalsePrope rty(OCLTestExample.java:22)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at junit.framework.TestCase.runTest(TestCase.java:168)
>>> at junit.framework.TestCase.runBare(TestCase.java:134)
>>> at junit.framework.TestResult$1.protect(TestResult.java:110)
>>> at junit.framework.TestResult.runProtected(TestResult.java:128)
>>> at junit.framework.TestResult.run(TestResult.java:113)
>>> at junit.framework.TestCase.run(TestCase.java:124)
>>> at junit.framework.TestSuite.runTest(TestSuite.java:232)
>>> at junit.framework.TestSuite.run(TestSuite.java:227)
>>> at
>>> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestRefer ence.run(JUnit3TestReference.java:130)
>>>
>>> at
>>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(Test Execution.java:38)
>>>
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:460)
>>>
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
>>>
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
>>>
>>> at
>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>>>
>>>
>>>
>>> <wrobinson@gsu.edu> wrote in message
>>> news:ff4uh1$3em$1@build.eclipse.org...
>>>> I am unable to Profile a JUnit 4 test. I read through the other
>>>> posts on this kind of problem, and it seems the error I have is a
>>>> bit different. I'm using the latest TPTP to date, 4.3.x.
>>>>
>>>> I can run JUnit or Profile without any problem. However, when I
>>>> Profile a JUnit test, I get a NoClassDefFoundError for the probe
>>>> class CbeProbe_probe$Probe_0.
>>>>
>>>> Select Open Profile Dialog and select a JUnit test with the JUnit 4
>>>> test runner.
>>>> Under the Monitor tab, select one of the three Instrument Collectors
>>>> (JME, CBE, ARM). Selecting any one the produces the same kind of
>>>> error: a NoClassDefFoundError related to the probe class (from one
>>>> of the 3 jar files)
>>>> I did find the missing probe class in a TPTP plugin
>>>> (org.eclipse.tptp.monitoring.instrumentation_4.3.0). However,
>>>> including the jar in the class or build paths does not change the
>>>> error message.
>>>>
>>>> Here's the stacktace for the CBE error:
>>>>
>>>> java.lang.NoClassDefFoundError: CbeProbe_probe$Probe_0
>>>> at $Proxy0.<clinit>(Unknown Source)
>>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e
>>>> Method)
>>>> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
>>>>
>>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
>>>> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588)
>>>> at
>>>> sun.reflect.annotation.AnnotationParser.annotationForMap(Ann otationParser.java:239)
>>>>
>>>> at
>>>> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:229)
>>>>
>>>> at
>>>> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
>>>>
>>>> at
>>>> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
>>>>
>>>> at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
>>>> at java.lang.Class.getAnnotation(Class.java:2989)
>>>> at
>>>> sun.reflect.annotation.AnnotationType.<init>(AnnotationType.java:104)
>>>> at
>>>> sun.reflect.annotation.AnnotationType.getInstance(Annotation Type.java:64)
>>>>
>>>> at
>>>> sun.reflect.annotation.AnnotationParser.parseAnnotation(Anno tationParser.java:202)
>>>>
>>>> at
>>>> sun.reflect.annotation.AnnotationParser.parseAnnotations2(An notationParser.java:69)
>>>>
>>>> at
>>>> sun.reflect.annotation.AnnotationParser.parseAnnotations(Ann otationParser.java:52)
>>>>
>>>> at java.lang.reflect.Method.declaredAnnotations(Method.java:676 )
>>>> at java.lang.reflect.Method.getAnnotation(Method.java:663)
>>>> at
>>>> org.junit.internal.runners.TestIntrospector.getTestMethods(T estIntrospector.java:28)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassMethodsRunner.<init>(TestClassMethodsRunner.java:27)
>>>>
>>>> at
>>>> org.junit.internal.runners.TestClassRunner.<init>(TestClassRunner.java:20)
>>>>
>>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e
>>>> Method)
>>>> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
>>>>
>>>> at
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
>>>>
>>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:4 94)
>>>> at
>>>> org.junit.internal.requests.ClassRequest.buildRunner(ClassRe quest.java:33)
>>>>
>>>> at
>>>> org.junit.internal.requests.ClassRequest.getRunner(ClassRequ est.java:28)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init >(JUnit4TestReference.java:26)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassRefere nce. <init>(JUnit4TestClassReference.java:24)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.crea teTest(JUnit4TestLoader.java:40)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.load Tests(JUnit4TestLoader.java:30)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:445)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTe sts(RemoteTestRunner.java:673)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(R emoteTestRunner.java:386)
>>>>
>>>> at
>>>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main( RemoteTestRunner.java:196)
>>>>
>>>>
|
|
|
Goto Forum:
Current Time: Tue Apr 23 08:05:22 GMT 2024
Powered by FUDForum. Page generated in 0.03456 seconds |
] 
Search
Help
Register
Login
Home
