May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9569) Class loading issue with the openjdk-orb on the JDK9

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-9569?page=com.atlassian.jira.plugin.... ] Tomasz Adamski closed WFLY-9569. -------------------------------- Resolution: Explained > Class loading issue with the openjdk-orb on the JDK9 > ---------------------------------------------------- > > Key: WFLY-9569 > URL: https://issues.jboss.org/browse/WFLY-9569 > Project: WildFly > Issue Type: Bug > Components: IIOP > Reporter: Amos Feng > Assignee: Tomasz Adamski > Labels: jdk9 > > I had this issue when using the PortableInterceptor at the ORB ORBInitializer. > The root cause is https://github.com/jboss/openjdk-orb/blob/master/src/share/classes/com/su... > And the jigsaw classloader in the jdk9 might be investigated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9569) Class loading issue with the openjdk-orb on the JDK9

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-9569?page=com.atlassian.jira.plugin.... ] Tomasz Adamski commented on WFLY-9569: -------------------------------------- I looked at the reproducer and it seems to me that our ORB is used to the problem is that its dependencies (f.e. Narayana) are not provided. IMO this has nothing to do with Java 9 classloading as running equivalent example on Java 8 (== standalone code with only openjdk-orb on the classpath) would lead to the same result. IMO this is not a bug and I'm closing it. [~zhfeng] if you need to run standalone ORB in Java 9 environment please contact me - I believe for that purpose the proper module configuration would have to be created, but again is config issue not a bug. > Class loading issue with the openjdk-orb on the JDK9 > ---------------------------------------------------- > > Key: WFLY-9569 > URL: https://issues.jboss.org/browse/WFLY-9569 > Project: WildFly > Issue Type: Bug > Components: IIOP > Reporter: Amos Feng > Assignee: Tomasz Adamski > Labels: jdk9 > > I had this issue when using the PortableInterceptor at the ORB ORBInitializer. > The root cause is https://github.com/jboss/openjdk-orb/blob/master/src/share/classes/com/su... > And the jigsaw classloader in the jdk9 might be investigated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2264) JGRP000012 with SAP Hybris default config

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2264?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2264: -------------------------------- Excellent! > JGRP000012 with SAP Hybris default config > ----------------------------------------- > > Key: JGRP-2264 > URL: https://issues.jboss.org/browse/JGRP-2264 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.11 > Reporter: Diana Haase > Assignee: Bela Ban > > A lot of discarted messages in console.log of Hybris Clusters > [UDP] | JGRP000012: discarded message from different cluster ... > [UDP] | JGRP000012: discarded message from different cluster dev-hybris-broadcast (our cluster is con-hybris-broadcast). Sender was xxxxx (received 724 identical messages from xxxx in the last 60347 ms) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2352) Executable model test coverage: run the optaplanner turtleTests with the executable model turned on and see if it survives the ordeal

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2352?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-2352: --------------------------------------- Issue https://issues.jboss.org/browse/DROOLS-2537 fixed and merged. Tests retriggered. > Executable model test coverage: run the optaplanner turtleTests with the executable model turned on and see if it survives the ordeal > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2352 > URL: https://issues.jboss.org/browse/DROOLS-2352 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Tibor Zimányi > > For now, we're looking for a one time test. Later I presume the exe model will be come the default, so these tests would just run? > To run the optaplanner turtle tests, run all tests in optaplanner-examples with the VM parameter `-DrunTurtleTests=true`. They take 48 hours to run. You can also just run one, for example NurseRosteringSolveAllTurtleTest, but don't forget that VM parameter. > Mario Fusco says you can do this to turn on the executable model: > {code} > kieBuilder.buildAll( ExecutableModelProject.class ); > {code} > I presume you 'd need to hack that in `ScoreDirectorFactoryConfig.buildDroolsScoreDirectorFactory()`. > Note: I have no idea if this even make sense: those turtle tests use a drl file input and don't use the kie-maven-plugin. We're looking for a switch to just turn it on and see if they are all still green. Mario thinks it's possible, if I understand it correctly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tibor Digana closed WFLY-7841. ------------------------------ Resolution: Explained I think this is not a bug because the Managed theread pools in Java EE are supposed to be managed in the sense of Thread lifecycle and not in the sense of CDI managed beans. After experience with it I found that the RequestScoped job has no end and EntityManager or Hibernate's Session is not closed which is quite useless for me. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2555) Broken welcome page layout in IE11

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2555?page=com.atlassian.jira.plugi... ] Toni Rikkola moved RHPAM-1025 to DROOLS-2555: --------------------------------------------- Project: Drools (was: Red Hat Process Automation Manager) Key: DROOLS-2555 (was: RHPAM-1025) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: (was: Business Central) Affects Build: (was: ER2) Affects Version/s: (was: 7.0.0.GA) QE Status: NEW Fix Version/s: (was: 7.0.0.GA) > Broken welcome page layout in IE11 > ---------------------------------- > > Key: DROOLS-2555 > URL: https://issues.jboss.org/browse/DROOLS-2555 > Project: Drools > Issue Type: Bug > Environment: Windows with IE 11 > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Labels: proposed-for-7-ga > > Welcome page layout is broken and background image is not resized to the entire width. Business Automation logo is hidden. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10376) ModuleJndiBindingProcessor has trace logging in wrong place

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10376?page=com.atlassian.jira.plugin... ] Stuart Douglas resolved WFLY-10376. ----------------------------------- Fix Version/s: 13.0.0.Beta1 Resolution: Done > ModuleJndiBindingProcessor has trace logging in wrong place > ----------------------------------------------------------- > > Key: WFLY-10376 > URL: https://issues.jboss.org/browse/WFLY-10376 > Project: WildFly > Issue Type: Bug > Components: Naming > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Trivial > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2554) variance accumulate never escapes NaN

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2554?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2554: ------------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > variance accumulate never escapes NaN > ------------------------------------- > > Key: DROOLS-2554 > URL: https://issues.jboss.org/browse/DROOLS-2554 > Project: Drools > Issue Type: Bug > Reporter: Justin Goldsmith > Assignee: Mario Fusco > > If you accumulate a single fact, then it gets reversed, this result never escapes being NaN. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2548) java.lang.IllegalStateException: Unknown PartType: dialect

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2548?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2548: ------------------------------------- Assignee: Toni Rikkola (was: Edson Tirelli) > java.lang.IllegalStateException: Unknown PartType: dialect > ---------------------------------------------------------- > > Key: DROOLS-2548 > URL: https://issues.jboss.org/browse/DROOLS-2548 > Project: Drools > Issue Type: Bug > Reporter: chandra vudumula > Assignee: Toni Rikkola > > org.kie.workbench.common.services.refactoring.backend.server.indexing.AbstractFileIndexer.toKObject Unable to index 'default://master@Repo/rules/src/main/resources/rules/*****.template'. > java.lang.IllegalStateException: Unknown PartType: dialect > at org.kie.workbench.common.services.refactoring.service.PartType.getPartTypeFromAttribueDescrName(PartType.java:164) > at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visitRuleAttribute(GuidedRuleTemplateIndexVisitor.java:104) > at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visit(GuidedRuleTemplateIndexVisitor.java:75) > at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visitRuleModel(GuidedRuleTemplateIndexVisitor.java:194) > at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visit(GuidedRuleTemplateIndexVisitor.java:73) > at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateIndexVisitor.visit(GuidedRuleTemplateIndexVisitor.java:67) > at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateFileIndexer.fillIndexBuilder(GuidedRuleTemplateFileIndexer.java:55) > at org.kie.workbench.common.services.refactoring.backend.server.indexing.AbstractFileIndexer.toKObject(AbstractFileIndexer.java:78) > at org.drools.workbench.screens.guided.template.server.indexing.GuidedRuleTemplateFileIndexer$Proxy$_$$_WeldClientProxy.toKObject(Unknown Source) > at org.uberfire.ext.metadata.io.BatchIndex$3.visitFile(BatchIndex.java:178) > at org.uberfire.ext.metadata.io.BatchIndex$3.visitFile(BatchIndex.java:144) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:71) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:96) > at org.uberfire.java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:48) > at org.uberfire.java.nio.file.Files.walkFileTree(Files.java:1031) > at org.uberfire.java.nio.file.Files.walkFileTree(Files.java:1052) > at org.uberfire.ext.metadata.io.BatchIndex.run(BatchIndex.java:142) > at org.uberfire.ext.metadata.io.BatchIndex.run(BatchIndex.java:127) > at org.uberfire.ext.metadata.io.BatchIndex$1.run(BatchIndex.java:98) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2542) KieHelper.getKieContainer() is not thread-safe

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2542?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2542: ------------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > KieHelper.getKieContainer() is not thread-safe > ---------------------------------------------- > > Key: DROOLS-2542 > URL: https://issues.jboss.org/browse/DROOLS-2542 > Project: Drools > Issue Type: Bug > Affects Versions: 7.7.0.Final > Reporter: Nils Meyer > Assignee: Mario Fusco > > Calling org.kie.api.KieServices.newKieContainer(ReleaseId, ClassLoader), in the way it is done in org.kie.internal.utils.KieHelper.getKieContainer() can cause problems in situations where concurrent threads are in action. newKieContainer reads the latest KieModule from the repository that was written by a builder. If multiple builders for different rules are running in parallel, it's not predictable, which rules will be used when creating a new session (see my sample below). > I'm aware that I can work around this issue by using ReleaseIds, but nevertheless this behavior is cumbersome if you'd like to understand the relation between the KieFileSystem and the KieContainer in org.kie.internal.utils.KieHelper.getKieContainer() -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2018