[JBoss JIRA] (AS7-4939) CLONE - CLI: unable to specify command arguments to echo-dmr command
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-4939?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky moved JBPAPP-9219 to AS7-4939:
------------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-4939 (was: JBPAPP-9219)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: EAP 6.0.0 ER 8)
Security: (was: Public)
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
> CLONE - CLI: unable to specify command arguments to echo-dmr command
> --------------------------------------------------------------------
>
> Key: AS7-4939
> URL: https://issues.jboss.org/browse/AS7-4939
> Project: Application Server 7
> Issue Type: Bug
> Reporter: Dominik Pospisil
> Assignee: Alexey Loubyansky
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> It seems to be impossible to specify command arguments to echo-dmr command beginning with double-dash.
> While e.g. this works:
> [domain@localhost:9999 /] echo-dmr undeploy deployment0.war
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [{
> "operation" => "remove",
> "address" => [("deployment" => "deployment0.war")]
> }]
> }
> This does not:
> [domain@localhost:9999 /] echo-dmr deploy /home/dpospisi/deploy/deployment1.war --all-server-groups
> Unrecognized arguments: [--all-server-groups]
> Putting requested command in quotes does not work as well.
--
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
13 years, 11 months
[JBoss JIRA] (AS7-4872) Linkage error when doing remote JNDI lookup from messaging subsystem
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-4872:
--------------------------------
Summary: Linkage error when doing remote JNDI lookup from messaging subsystem
Key: AS7-4872
URL: https://issues.jboss.org/browse/AS7-4872
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jeff Mesnil
Assignee: John Bailey
Priority: Minor
Working on AS7-4626 to add JMS bridge, the messaging subsystem now need to perform remote JNDI lookup on another AS7 instances.
I added the org.jboss.remote-naming to the org.jboss.as.messaging to be able to load org.jboss.naming.remote.client.InitialContextFactory.
However this creates a Linkage error:
09:45:42,100 WARN [org.jboss.modules] (MSC service thread 1-4) Failed to define class org.jboss.naming.remote.client.ejb.RemoteNamingEjbClientContextSelector in Module "org.jboss.remote-naming:main" from local module loader @a94884d (roots: /home/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules): java.lang.LinkageError: Failed to link org/jboss/naming/remote/client/ejb/RemoteNamingEjbClientContextSelector (Module "org.jboss.remote-naming:main" from local module loader @a94884d (roots: /home/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules))
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73)
at org.jboss.modules.Module.loadModuleClass(Module.java:527)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
at org.jboss.naming.remote.client.InitialContextFactory.<clinit>(InitialContextFactory.java:118) [jboss-remote-naming-1.0.3.Final.jar:1.0.3.Final]
at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_24]
at java.lang.Class.forName(Class.java:264) [rt.jar:1.6.0_24]
at org.jboss.as.naming.InitialContextFactoryBuilder.createInitialContextFactory(InitialContextFactoryBuilder.java:61) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:681) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.init(InitialContext.java:240) [rt.jar:1.6.0_24]
at javax.naming.InitialContext.<init>(InitialContext.java:214) [rt.jar:1.6.0_24]
at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55) [hornetq-jms-2.2.16.Final.jar:2.2.16.Final (HQ_2_2_16_FINAL, 122)]
at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40) [hornetq-jms-2.2.16.Final.jar:2.2.16.Final (HQ_2_2_16_FINAL, 122)]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1083) [hornetq-jms-2.2.16.Final.jar:2.2.16.Final (HQ_2_2_16_FINAL, 122)]
at org.hornetq.jms.bridge.impl.JMSBridgeImpl.start(JMSBridgeImpl.java:348) [hornetq-jms-2.2.16.Final.jar:2.2.16.Final (HQ_2_2_16_FINAL, 122)]
at org.jboss.as.messaging.jms.bridge.JMSBridgeService.start(JMSBridgeService.java:57) [jboss-as-messaging-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
Caused by: java.lang.NoClassDefFoundError: org/jboss/ejb/client/ContextSelector
at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_24]
at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [rt.jar:1.6.0_24]
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [rt.jar:1.6.0_24]
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391)
... 26 more
Caused by: java.lang.ClassNotFoundException: org.jboss.ejb.client.ContextSelector from [Module "org.jboss.remote-naming:main" from local module loader @a94884d (roots: /home/jmesnil/Developer/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
... 31 more
This error does not prevent doing remote lookups but looks ugly when starting the JMS bridge...
org.jboss.naming.remote.client.InitialContextFactory is trying to load org.jboss.naming.remote.client.ejb.RemoteNamingEjbClientContextSelector
in its static initialization block.
This class depends on org.jboss.ejb.client.ContextSelector which is in the org.jboss.ejb-client module.
I don't want to add a dependency from org.jboss.as.messaging to org.jboss.ejb-client if I can avoid it.
The org.jboss.naming.remote.client.InitialContextFactory defines a SETUP_EJB_CONTEXT property that I could set to false but this property is checked after trying to load the ejb-client class in the static block. afaict, loading the class only after checking the property would be enough to prevent having this error being displayed
--
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
13 years, 11 months
[JBoss JIRA] (LOGMGR-44) IllegalArgumentException: nodeName is empty, or just whitespace when getLogger
by Amos Feng (JIRA)
Amos Feng created LOGMGR-44:
-------------------------------
Summary: IllegalArgumentException: nodeName is empty, or just whitespace when getLogger
Key: LOGMGR-44
URL: https://issues.jboss.org/browse/LOGMGR-44
Project: JBoss Log Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core
Affects Versions: 1.3.1.Final
Reporter: Amos Feng
Assignee: David Lloyd
our context name is [/../service/target/txbridge-demo-service], it throws IllegalArgumentException when getLogger.
the stack trace:
{code}
16:33:00,202 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Context [/../service/target/txbridge-demo-service] startup failed due to previous errors: java.lang.IllegalArgumentException: nodeName is empty, or just whitespace
at org.jboss.logmanager.LoggerNode.<init>(LoggerNode.java:127) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:154) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LogContext.getLogger(LogContext.java:126) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LogManager.getLogger(LogManager.java:401) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logmanager.LogManager.getLogger(LogManager.java:45) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at java.util.logging.LogManager.demandLogger(LogManager.java:389) [rt.jar:1.6.0_30]
at java.util.logging.Logger.getLogger(Logger.java:288) [rt.jar:1.6.0_30]
at org.jboss.logmanager.Logger.getLogger(Logger.java:59) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final]
at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:56) [jboss-logging-3.1.1.GA.jar:3.1.1.GA]
at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47) [jboss-logging-3.1.1.GA.jar:3.1.1.GA]
at org.jboss.logging.Logger.getLogger(Logger.java:2163) [jboss-logging-3.1.1.GA.jar:3.1.1.GA]
at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:409)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3765)
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
{code}
--
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
13 years, 11 months
[JBoss JIRA] (JBRULES-3302) Unwanted type coersion of String to float values when using "in" keyword LHS
by Troy Parrish (Created) (JIRA)
Unwanted type coersion of String to float values when using "in" keyword LHS
----------------------------------------------------------------------------
Key: JBRULES-3302
URL: https://issues.jboss.org/browse/JBRULES-3302
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.3.0.Final, 5.2.0.Final
Environment: Windows 7, Rational Application Developer 7.5, Eclipse Helios Service Release 2
Reporter: Troy Parrish
Assignee: Mark Proctor
String values get treated as float values even when fact declares the property as a String when using the "in" keyword to evaluate a String value against a set of values in the lhs of the rule.
Example:
input into session : "10.5"
will match against all of the following values "10.5", "10.50", "10.500" etc when in this format:
when
Fact(string in ("11.5", "10.50", "11.500"))
then
This problem behavior occurs in 5.3.0Final, 5.2.0.Final but not in 5.1.0Final, this is when Expert went from using mvel 2.0.16 to mvel 2.1.0
--
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
13 years, 11 months
[JBoss JIRA] (JBRULES-3377) drools modify command mvel exception
by Mario Fusco (JIRA)
Mario Fusco created JBRULES-3377:
------------------------------------
Summary: drools modify command mvel exception
Key: JBRULES-3377
URL: https://issues.jboss.org/browse/JBRULES-3377
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
Following exception occurs when trying to execute modify command on stateful
session:
{ with (this) {
age = 30
,name = Frank
,id = 0
,likes = nobody
} }
Exception in thread "main" [Error: unable to resolve method:
com.redhat.modifyreproducer.Person.Frank() [arglength=0]]
[Near : {... ,name = Frank ....}]
^
[Line: 5, Column: 1]
at org.mvel2.PropertyAccessor.getMethod(PropertyAccessor.java:977)
at org.mvel2.PropertyAccessor.getBeanProperty(PropertyAccessor.java:687)
at org.mvel2.PropertyAccessor.getNormal(PropertyAccessor.java:202)
at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:171)
at org.mvel2.PropertyAccessor.get(PropertyAccessor.java:151)
at org.mvel2.ast.ASTNode.getReducedValue(ASTNode.java:185)
at
org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:106)
at org.mvel2.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:49)
at org.mvel2.MVEL.eval(MVEL.java:408)
at org.mvel2.util.ParseTools.parseWithExpressions(ParseTools.java:1591)
at org.mvel2.ast.WithNode.getReducedValue(WithNode.java:75)
at
org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:106)
at org.mvel2.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:49)
at org.mvel2.MVEL.eval(MVEL.java:109)
at
org.drools.command.runtime.rule.ModifyCommand.execute(ModifyCommand.java:79)
at
org.drools.impl.StatefulKnowledgeSessionImpl.execute(StatefulKnowledgeSessionImpl.java:798)
at
org.drools.impl.StatefulKnowledgeSessionImpl.execute(StatefulKnowledgeSessionImpl.java:781)
at com.redhat.modifyreproducer.Main.test(Main.java:52)
at com.redhat.modifyreproducer.Main.main(Main.java:30)
------------------------------------------------------------------------------
First, fact is inserted into the session, next step is creating Modify command
with setter list:
Person p1 = new Person("John", "nobody", 25);
session.execute(CommandFactory.newInsert(p1));
FactHandle fh = session.getFactHandle(p1);
Person p = new Person("Frank", "nobody", 30);
List<Setter> setterList = new ArrayList<Setter>();
setterList.add(CommandFactory.newSetter("age",
String.valueOf(p.getAge())));
setterList.add(CommandFactory.newSetter("name", p.getName()));
setterList.add(CommandFactory.newSetter("likes", p.getLikes()));
setterList.add(CommandFactory.newSetter("id",
String.valueOf(p.getId())));
session.execute(CommandFactory.newModify(fh, setterList));
See an attachment for the details, just build as maven project and run.
--
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
13 years, 11 months
[JBoss JIRA] (JBRULES-3390) Drools java.lang.NullPointerException at org.drools.reteoo.RuleTerminalNode
by Alberto Rugnone (JIRA)
Alberto Rugnone created JBRULES-3390:
----------------------------------------
Summary: Drools java.lang.NullPointerException at org.drools.reteoo.RuleTerminalNode
Key: JBRULES-3390
URL: https://issues.jboss.org/browse/JBRULES-3390
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.3.0.Final
Environment: eclipse 3.6, Drools 5.3, jdk1.6.0_25_x64
Reporter: Alberto Rugnone
Assignee: Mark Proctor
My application has to monitor when a magnetic contact is activated and when it is contact released event has to be retracted. And viceversa. Here is my rule and the big null pointer I have. Any helps will be very appreciated! Thank you a lot!!
rule "contact activated vs contact released" salience 0 no-loop true
when
$contact_activated : Event(type == EventType.CONTACT_ACTIVATED) ||
$contact_released : Event(type == EventType.CONTACT_RELEASED)
then
if($contact_activated!= null) {
retract($contact_activated);
} else {
retract($contact_released);
}
end
and
I have
java.lang.NullPointerException
at org.drools.reteoo.RuleTerminalNode$SortDeclarations.compare(RuleTerminalNode.java:477)
at org.drools.reteoo.RuleTerminalNode$SortDeclarations.compare(RuleTerminalNode.java:473)
at java.util.Arrays.mergeSort(Arrays.java:1270)
at java.util.Arrays.sort(Arrays.java:1210)
at org.drools.reteoo.RuleTerminalNode.<init>(RuleTerminalNode.java:119)
at org.drools.RuleActivationListenerFactory.createActivationListener(RuleActivationListenerFactory.java:21)
at org.drools.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:157)
at org.drools.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:123)
at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:110)
at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:441)
at org.drools.common.AbstractRuleBase.addRule(AbstractRuleBase.java:821)
at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:555)
at org.drools.reteoo.ReteooRuleBase.addPackages(ReteooRuleBase.java:458)
at org.drools.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:150)
at it.ipiu.pch.sel.RuleTest.before(RuleTest.java:1272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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.RunBefores.evaluate(RunBefores.java:27)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
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:49)
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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months