[JBoss JIRA] (WFLY-5888) Add journal-pool-file attribute
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-5888:
---------------------------------
Summary: Add journal-pool-file attribute
Key: WFLY-5888
URL: https://issues.jboss.org/browse/WFLY-5888
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 10.0.0.CR5
Artemis 1.1.0.wildfly-010 has a new attribute journal-pool-files that must be added to the server resource definition
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-1009) lambda expressions cannot be parsed by ecj/janino
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1009?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1009.
---------------------------------
Fix Version/s: 6.4.x
Resolution: Done
Drools 6.4.x will use ECJ 4.4.2 that supports Java 8 syntax.
Fixed by https://github.com/droolsjbpm/drools/commit/5e88d07b7
> lambda expressions cannot be parsed by ecj/janino
> -------------------------------------------------
>
> Key: DROOLS-1009
> URL: https://issues.jboss.org/browse/DROOLS-1009
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.3.0.Final
> Reporter: Malte Brunnlieb
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
>
> Using Java8 lambda expression in the decision template like
> bean1.call(() -> $param);
> you will run into compiler issues with ejc as well as the currently supported version of JANINO (2.5.16). I tried to manually upgrade the JANINO compiler version, but got stuck in compatibility issues as the Scanner seems to have been changed regarding exception handling.
> Can you suggest to fix the incompatibility with JANINO > 2.5.16 such that lambda expressions can be parsed by the newest parsers? Would be nice :)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-1009) lambda expressions cannot be parsed by ecj/janino
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1009?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on DROOLS-1009:
-------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1199965|https://bugzilla.redhat.com/show_bug.cgi?id=1199965] from NEW to MODIFIED
> lambda expressions cannot be parsed by ecj/janino
> -------------------------------------------------
>
> Key: DROOLS-1009
> URL: https://issues.jboss.org/browse/DROOLS-1009
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.3.0.Final
> Reporter: Malte Brunnlieb
> Assignee: Mario Fusco
>
> Using Java8 lambda expression in the decision template like
> bean1.call(() -> $param);
> you will run into compiler issues with ejc as well as the currently supported version of JANINO (2.5.16). I tried to manually upgrade the JANINO compiler version, but got stuck in compatibility issues as the Scanner seems to have been changed regarding exception handling.
> Can you suggest to fix the incompatibility with JANINO > 2.5.16 such that lambda expressions can be parsed by the newest parsers? Would be nice :)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBEE-161) BeanELResolver does not support methods that use varargs
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBEE-161?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar moved WFLY-5882 to JBEE-161:
----------------------------------------
Project: JBoss JavaEE Spec APIs (was: WildFly)
Key: JBEE-161 (was: WFLY-5882)
Workflow: classic default workflow (was: GIT Pull Request workflow )
Component/s: jboss-el-api
(was: EE)
> BeanELResolver does not support methods that use varargs
> --------------------------------------------------------
>
> Key: JBEE-161
> URL: https://issues.jboss.org/browse/JBEE-161
> Project: JBoss JavaEE Spec APIs
> Issue Type: Bug
> Components: jboss-el-api
> Environment: jboss-el-api_2.2_spec-1.0.4.Final-redhat-1
> Reporter: Ingo Weiss
> Assignee: Carlo de Wolf
> Labels: el
> Attachments: beanELResolver4VarArgs.zip
>
>
> When passing BeanELResolver a method that uses varargs, BeanELResolver throws the following exception:
> {code}
> java.lang.IllegalArgumentException: wrong number of arguments
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at javax.el.BeanELResolver.invokeMethod(BeanELResolver.java:834)
> at javax.el.BeanELResolver.invoke(BeanELResolver.java:527)
> at org.apache.el.parser.AstValue.getValue(AstValue.java:156)
> at BeanELResolverTest.readExpressionValue(BeanELResolverTest.java:32)
> at BeanELResolverTest.testMethodWithFixArgumentList(BeanELResolverTest.java:21)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-1012) kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-1012:
-----------------------------------
Summary: kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
Key: DROOLS-1012
URL: https://issues.jboss.org/browse/DROOLS-1012
Project: Drools
Issue Type: Bug
Reporter: Mario Fusco
Assignee: Mario Fusco
Attachments: brms-fuse-integration-master.tgz
kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry. This implies that when the KieContainer is created in a OSGi environment it is not able to get an instance of the MavenClassLoaderResolver and then cannot create a ClassLoader including all the transitive dependencies of the kjar to be compiled.
The attached project reproduces this issue. In order to run it, it's enough to do a mvn clean install of the project and issue the following commands in fuse:
features:addurl mvn:com.redhat/brms-fuse-integration-features/0.0.1-SNAPSHOT/xml/features
features:install brms-integration-bundle
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5760) Hibernate Validator test-cases fails due to missing accessDeclaredMembers RuntimePermission
by Ivo Studensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-5760?page=com.atlassian.jira.plugin.... ]
Ivo Studensky resolved WFLY-5760.
---------------------------------
Fix Version/s: 10.0.0.CR5
Resolution: Done
> Hibernate Validator test-cases fails due to missing accessDeclaredMembers RuntimePermission
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-5760
> URL: https://issues.jboss.org/browse/WFLY-5760
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Test Suite
> Affects Versions: 10.0.0.CR4
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Fix For: 10.0.0.CR5
>
>
> Hibernate Validator test-cases calling a validator from an in-container class (e.g. a test-class deployed to the server by Arquillian) need RuntimePermission("accessDeclaredMembers") in order to pass.
> It is a question if it should be handled by a doPrivileged block in Hibernate Validator project or if the affected test-cases need to be provided by additional permissions.
> Here is the stack-trace of one of the affected tests:
> {noformat}
> javax.validation.ValidationException: HV000041: Call to TraversableResolver.isReachable() threw an exception.
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175)
> at java.lang.Class.checkMemberAccess(Class.java:2348)
> at java.lang.Class.getDeclaredField(Class.java:2067)
> at org.hibernate.jpa.internal.util.PersistenceUtilHelper$ClassMetadataCache.buildAttributeAccess(PersistenceUtilHelper.java:348)
> at org.hibernate.jpa.internal.util.PersistenceUtilHelper$ClassMetadataCache.getAttributeAccess(PersistenceUtilHelper.java:339)
> at org.hibernate.jpa.internal.util.PersistenceUtilHelper.isLoadedWithReference(PersistenceUtilHelper.java:202)
> at org.hibernate.jpa.HibernatePersistenceProvider$1.isLoadedWithReference(HibernatePersistenceProvider.java:175)
> at javax.persistence.Persistence$1.isLoaded(Persistence.java:116)
> at org.hibernate.validator.internal.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:46)
> at org.hibernate.validator.internal.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableResolver.java:128)
> at org.hibernate.validator.internal.engine.resolver.CachingTraversableResolverForSingleValidation.isReachable(CachingTraversableResolverForSingleValidation.java:36)
> at org.hibernate.validator.internal.engine.ValidatorImpl.isReachable(ValidatorImpl.java:1522)
> at org.hibernate.validator.internal.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:1507)
> at org.hibernate.validator.internal.engine.ValidatorImpl.validateMetaConstraint(ValidatorImpl.java:584)
> at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:555)
> at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForDefaultGroup(ValidatorImpl.java:490)
> at org.hibernate.validator.internal.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:454)
> at org.hibernate.validator.internal.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:406)
> at org.hibernate.validator.internal.engine.ValidatorImpl.validate(ValidatorImpl.java:204)
> at org.jboss.as.test.integration.beanvalidation.hibernate.validator.MessageInterpolationValidationTestCase.testCustomMessageInterpolation(MessageInterpolationValidationTestCase.java:56)
> {noformat}
> Tests affected by this are located at org.jboss.as.test.integration.beanvalidation.hibernate.validator package.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-926) Missing synchronization in PackageClassLoader causes a LinkageError: duplicate class definition
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-926?page=com.atlassian.jira.plugin... ]
Mario Fusco commented on DROOLS-926:
------------------------------------
For what I can see that fix has been cherry-picked to our branch 6.3.x on the 22nd of Sep ( https://github.com/droolsjbpm/drools/commit/0dfb362e96e10bfb3d6c45a9b445c... ) and Drools 6.3 has been released on the 25th, so I'm assuming that the fix should be there. I'll double check the code.
> Missing synchronization in PackageClassLoader causes a LinkageError: duplicate class definition
> -----------------------------------------------------------------------------------------------
>
> Key: DROOLS-926
> URL: https://issues.jboss.org/browse/DROOLS-926
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.3.0.Final
>
>
> Creating multiple KieSessions from a KieBase with a function and using them concurrently from different threads may lead to the following error
> java.util.concurrent.ExecutionException: java.lang.LinkageError: loader (instance of org/drools/core/rule/JavaDialectRuntimeData$PackageClassLoader): attempted duplicate class definition for name: "defaultpkg/IsEven"
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at org.drools.compiler.integrationtests.Misc2Test.testFunctionInvokingFunction(Misc2Test.java:8191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:78)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:212)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: java.lang.LinkageError: loader (instance of org/drools/core/rule/JavaDialectRuntimeData$PackageClassLoader): attempted duplicate class definition for name: "defaultpkg/IsEven"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.fastFindClass(JavaDialectRuntimeData.java:673)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.loadClass(JavaDialectRuntimeData.java:639)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at org.drools.core.rule.MVELDialectRuntimeData.getParserConfiguration(MVELDialectRuntimeData.java:299)
> at org.drools.core.base.mvel.MVELCompilationUnit.getCompiledExpression(MVELCompilationUnit.java:214)
> at org.drools.core.rule.constraint.MvelConstraint.createMvelConditionEvaluator(MvelConstraint.java:254)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:238)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:204)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:298)
> at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:93)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:96)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:69)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:1993)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1289)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260)
> at org.drools.compiler.integrationtests.Misc2Test$11.call(Misc2Test.java:8180)
> at org.drools.compiler.integrationtests.Misc2Test$11.call(Misc2Test.java:8170)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (DROOLS-926) Missing synchronization in PackageClassLoader causes a LinkageError: duplicate class definition
by René Zanner (JIRA)
[ https://issues.jboss.org/browse/DROOLS-926?page=com.atlassian.jira.plugin... ]
René Zanner commented on DROOLS-926:
------------------------------------
[~mfusco], shall I clone this issue or will you change the "Fix version/s"?
> Missing synchronization in PackageClassLoader causes a LinkageError: duplicate class definition
> -----------------------------------------------------------------------------------------------
>
> Key: DROOLS-926
> URL: https://issues.jboss.org/browse/DROOLS-926
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.3.0.Final
>
>
> Creating multiple KieSessions from a KieBase with a function and using them concurrently from different threads may lead to the following error
> java.util.concurrent.ExecutionException: java.lang.LinkageError: loader (instance of org/drools/core/rule/JavaDialectRuntimeData$PackageClassLoader): attempted duplicate class definition for name: "defaultpkg/IsEven"
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at org.drools.compiler.integrationtests.Misc2Test.testFunctionInvokingFunction(Misc2Test.java:8191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:78)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:212)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: java.lang.LinkageError: loader (instance of org/drools/core/rule/JavaDialectRuntimeData$PackageClassLoader): attempted duplicate class definition for name: "defaultpkg/IsEven"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.fastFindClass(JavaDialectRuntimeData.java:673)
> at org.drools.core.rule.JavaDialectRuntimeData$PackageClassLoader.loadClass(JavaDialectRuntimeData.java:639)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at org.drools.core.rule.MVELDialectRuntimeData.getParserConfiguration(MVELDialectRuntimeData.java:299)
> at org.drools.core.base.mvel.MVELCompilationUnit.getCompiledExpression(MVELCompilationUnit.java:214)
> at org.drools.core.rule.constraint.MvelConstraint.createMvelConditionEvaluator(MvelConstraint.java:254)
> at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:238)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:204)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:298)
> at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:93)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:96)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:69)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:1993)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1289)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1294)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1260)
> at org.drools.compiler.integrationtests.Misc2Test$11.call(Misc2Test.java:8180)
> at org.drools.compiler.integrationtests.Misc2Test$11.call(Misc2Test.java:8170)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months