[JBoss JIRA] (AS7-6419) Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/AS7-6419?page=com.atlassian.jira.plugin.s... ]
Stefano Maestri commented on AS7-6419:
--------------------------------------
you need much more deps:
<dependencies>
<module name="javax.api"/>
<module name="javax.resource.api"/>
<module name="javax.validation.api"/>
<module name="org.hibernate.validator"/>
<module name="org.jboss.as.naming"/>
<module name="org.jboss.as.transactions"/>
<module name="org.jboss.common-core"/>
<module name="org.jboss.jboss-transaction-spi"/>
<module name="org.jboss.ironjacamar.api"/>
<module name="org.jboss.logging"/>
<module name="org.jboss.threads"/>
<module name="javax.xml.stream.api"/>
<module name="javax.jms.api" />
</dependencies>
> Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
> -----------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6419
> URL: https://issues.jboss.org/browse/AS7-6419
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.2.0.Alpha1
> Environment: Configuration:
> JDK-Version: 1.6.0_33
> Operating System: Windows 7 (32 Bit)
> JBoss Application Server jboss-as-7.2.0.Alpha1-SNAPSHOT (build Dec. 19th 2012)
> JDK-Version: 1.6.0_33
> Resource Adapter: BeanConnect 3.0 developed by our Company (Fujitsu)
> Reporter: Martin Keller
> Assignee: Stefano Maestri
>
> Tbis Problem was reported before see https://issues.jboss.org/browse/AS7-6384, but now the components to reproduce it is included.
> Starting an application using our JCA 1.6 resource adapter fails with
> java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> It works ok in the JBoss JCA 1.5 environment and on other application servers with JCA1.6 environment:
> GlassFish OS Edition 3, IBM WebSphere 8.0 and WebLogic 12.
> Questions:
> What could be the cause for this exception?
> Can we switch off the validation?
> What is missing to run the validation successful?
> Details:
> The full stack is:
> 15:04:02,128 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 64) MSC00001: Failed to start service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:177)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> ... 7 more
> Caused by: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:147)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:175)
> ... 8 more
> Caused by: javax.validation.ValidationException: Unable to find a default provider
> at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:264) [validation-api-1.0.0.GA.jar:]
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidatorFactory(BeanValidationUtil.java:51)
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidator(BeanValidationUtil.java:63)
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:135)
> ... 9 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori edited comment on AS7-6420 at 1/30/13 9:24 AM:
-----------------------------------------------------------------
Deploying this jar in this folder that I'm experiencing the issue, causes it to first say "success", and adding it to standalone-osgi.xml, but it doesn't add it to UI. After that, all activities related to that jar (=redeployments) fail, but .jar doesn't appear in the ui either. If I remove previously tried spring-ws (that had been failing), spring-xml appears again in the UI. Interesting.
was (Author: jrantav):
Deploying this jar in this folder that I'm experiencing the issue, causes it to first say "success", and adding it to standalone-osgi.xml, but it doesn't add it to UI. After that, all activities related to that jar (=redeployments) fail, but .jar doesn't appear in the ui either. If I copy the server installation to another folder, everything starts to work. Interesting.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori updated AS7-6420:
-----------------------------------
Environment: Windows 7, 64-bit
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Environment: Windows 7, 64-bit
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6420:
----------------------------------------
Deploying this jar in this folder that I'm experiencing the issue, causes it to first say "success", and adding it to standalone-osgi.xml, but it doesn't add it to UI. After that, all activities related to that jar (=redeployments) fail, but .jar doesn't appear in the ui either. If I copy the server installation to another folder, everything starts to work. Interesting.
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6420) spring-xml deployment fails without any error message given in latest snapshot
by jarkko rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6420?page=com.atlassian.jira.plugin.s... ]
jarkko rantavuori commented on AS7-6420:
----------------------------------------
Um, copied the whole server installation to another folder, and this now works...
> spring-xml deployment fails without any error message given in latest snapshot
> ------------------------------------------------------------------------------
>
> Key: AS7-6420
> URL: https://issues.jboss.org/browse/AS7-6420
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi, Server
> Affects Versions: 7.2.0.Alpha1
> Reporter: jarkko rantavuori
> Assignee: Thomas Diesler
> Attachments: org.springframework.xml-2.1.0.RELEASE.jar
>
>
> Today, 30.1.2013, I just got the latest snapshot from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/... and tried to deploy my Spring framework on it. Spring-xml 2.10 component fails without any error message given, whereas the same jar deployed without issues in 18.12.2012 snapshot.
> I tried to set set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false" to get an error message, but that did not help.
> Jar is from Spring enterprise repository, containing OSGi metadata, so this might be OSGi related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6419) Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
by Martin Keller (JIRA)
[ https://issues.jboss.org/browse/AS7-6419?page=com.atlassian.jira.plugin.s... ]
Martin Keller commented on AS7-6419:
------------------------------------
Here is the module.xml:
<?xml version="1.0" encoding="UTF-8" ?>
<!-- -->
<!-- Represents the BeanConnect 3.0 module -->
<module xmlns="urn:jboss:module:1.1" name="net.fsc.beanconnect">
<resources>
<resource-root path="BeanConnectBas.jar" />
<resource-root path="BeanConnectCob2Xml.jar" />
<resource-root path="BeanConnectCommonsBeanUtil.jar" />
<resource-root path="BeanConnectEncoding.jar" />
<resource-root path="BeanConnectI18N.jar" />
<resource-root path="BeanConnectI18Nmsgs.jar" />
<resource-root path="BeanConnectJConnect.jar" />
<resource-root path="BeanConnectLog4j.jar" />
<resource-root path="BeanConnectLogging.jar" />
<resource-root path="BeanConnectModeler.jar" />
<resource-root path="BeanConnectOltpMsg.jar" />
<resource-root path="BeanConnectStub.jar" />
<resource-root path="BeanConnectUI.jar" />
<resource-root path="RainersEncoding.jar" />
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="javax.api" />
<module name="javax.resource.api" />
</dependencies>
</module>
> Failed to start service jboss.deployment.subunit javax.resource.ResourceException: IJ000852: Validation exception
> -----------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6419
> URL: https://issues.jboss.org/browse/AS7-6419
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.2.0.Alpha1
> Environment: Configuration:
> JDK-Version: 1.6.0_33
> Operating System: Windows 7 (32 Bit)
> JBoss Application Server jboss-as-7.2.0.Alpha1-SNAPSHOT (build Dec. 19th 2012)
> JDK-Version: 1.6.0_33
> Resource Adapter: BeanConnect 3.0 developed by our Company (Fujitsu)
> Reporter: Martin Keller
> Assignee: Stefano Maestri
>
> Tbis Problem was reported before see https://issues.jboss.org/browse/AS7-6384, but now the components to reproduce it is included.
> Starting an application using our JCA 1.6 resource adapter fails with
> java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> It works ok in the JBoss JCA 1.5 environment and on other application servers with JCA1.6 environment:
> GlassFish OS Edition 3, IBM WebSphere 8.0 and WebLogic 12.
> Questions:
> What could be the cause for this exception?
> Can we switch off the validation?
> What is missing to run the validation successful?
> Details:
> The full stack is:
> 15:04:02,128 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool – 64) MSC00001: Failed to start service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."BCSamplePfa.ear"."1stBCEJBs.jar".component.CallEISOltpMdb.START: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_33]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Caused by: java.lang.RuntimeException: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:177)
> at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [jboss-as-ee-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> ... 7 more
> Caused by: javax.resource.ResourceException: IJ000852: Validation exception
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:147)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:175)
> ... 8 more
> Caused by: javax.validation.ValidationException: Unable to find a default provider
> at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:264) [validation-api-1.0.0.GA.jar:]
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidatorFactory(BeanValidationUtil.java:51)
> at org.jboss.jca.core.bv.BeanValidationUtil.createValidator(BeanValidationUtil.java:63)
> at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:135)
> ... 9 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (DROOLS-18) [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-18?page=com.atlassian.jira.plugin.... ]
Mario Fusco commented on DROOLS-18:
-----------------------------------
Ok, cool. So can I close this ticket?
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-18
> URL: https://issues.jboss.org/browse/DROOLS-18
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Windows 7 64Bit
> Java 1.7.0
> Drools-core 5.5.0.Final
> Drools-compiler 5.5.0.Final
> Mvel2 2.1.3.Final
> Reporter: Michiel Vermandel
> Assignee: Mario Fusco
> Priority: Critical
>
> In about one out of ten JUnit runs, I get a crash with stack trace.
> The process terminates immediately.
> Unit test output is 100% the same on successful runs.
> Stack trace:
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> [Near : {... this == lead ....}]
> ^
> [Line: 1, Column: 1]
> at org.mvel2.ast.BinaryOperation.<init>(BinaryOperation.java:84)
> at org.mvel2.util.CompilerTools.finalizePayload(CompilerTools.java:118)
> at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:287)
> at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:62)
> at org.mvel2.MVEL.compileExpression(MVEL.java:810)
> at org.drools.base.mvel.MVELCompilationUnit.compile(MVELCompilationUnit.java:435)
> at org.drools.base.mvel.MVELCompilationUnit.getCompiledExpression(MVELCompilationUnit.java:238)
> at org.drools.rule.constraint.MvelConstraint.createMvelConditionEvaluator(MvelConstraint.java:206)
> at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:190)
> at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:157)
> at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:137)
> at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:497)
> at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:382)
> at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:235)
> at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:240)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:350)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:311)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:903)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:847)
> at org.drools.planner.core.score.director.drools.DroolsScoreDirector.afterEntityAdded(DroolsScoreDirector.java:103)
> at org.drools.planner.core.heuristic.selector.variable.PlanningVariableWalker.moveIterator(PlanningVariableWalker.java:145)
> at org.drools.planner.core.constructionheuristic.greedyFit.decider.DefaultGreedyDecider.decideNextStep(DefaultGreedyDecider.java:74)
> at org.drools.planner.core.constructionheuristic.greedyFit.DefaultGreedyFitSolverPhase.solve(DefaultGreedyFitSolverPhase.java:65)
> at org.drools.planner.core.solver.DefaultSolver.runSolverPhases(DefaultSolver.java:190)
> at org.drools.planner.core.solver.DefaultSolver.solve(DefaultSolver.java:155)
> at be.axi.planner.app.InspectionSchedule.solve(InspectionSchedule.java:192)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:288)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:298)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:315)
> at be.axi.planner.TaskGroupingTest.communitySuccess02(TaskGroupingTest.java:289)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months