May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1187) Score corruption (regression) in nurse rostering long_hint01.xml after fix for DROOLS-1174

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1187?page=com.atlassian.jira.plugi... ] Jiri Locker commented on DROOLS-1187: ------------------------------------- Will assign back to Mario when the isolation is completed. > Score corruption (regression) in nurse rostering long_hint01.xml after fix for DROOLS-1174 > ------------------------------------------------------------------------------------------ > > Key: DROOLS-1187 > URL: https://issues.jboss.org/browse/DROOLS-1187 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta1 > Reporter: Geoffrey De Smet > Assignee: Jiri Locker > > the new mole after whacking the mole of DROOLS-1174... > {code} > ava.lang.IllegalStateException: Score corruption: the workingScore (0hard/-85soft) is not the uncorruptedScore (0hard/-86soft) after completedAction ([[2010-01-11/D, 2010-01-12/L, 2010-01-13/L, 2010-01-14/L] {? -> 16}, [2010-01-14/DH, 2010-01-15/E, 2010-01-16/L, 2010-01-17/L] {? -> 29}]): > The corrupted scoreDirector has no ConstraintMatch(s) which are in excess. > The corrupted scoreDirector has 1 ConstraintMatch(s) which are missing: > org.optaplanner.examples.nurserostering.solver/maximumConsecutiveWorkingWeekends/level1/[18 is working the weekend of 2 - 23, 18, 0-CONSECUTIVE_WORKING_WEEKENDS]=-1 > Check your score constraints. > at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertWorkingScoreFromScratch(AbstractScoreDirector.java:418) > at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertWorkingScoreFromScratch(DefaultSolverScope.java:118) > at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertWorkingScoreFromScratch(AbstractPhaseScope.java:167) > at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.processMove(LocalSearchDecider.java:167) > at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.doMove(LocalSearchDecider.java:153) > at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.decideNextStep(LocalSearchDecider.java:125) > at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:63) > at org.optaplanner.core.impl.solver.DefaultSolver.runPhases(DefaultSolver.java:229) > at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:191) > at org.optaplanner.examples.common.app.SolveAllTurtleTest.buildAndSolve(SolveAllTurtleTest.java:75) > at org.optaplanner.examples.common.app.SolveAllTurtleTest.runFastAndFullAssert(SolveAllTurtleTest.java:59) > 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1187) Score corruption (regression) in nurse rostering long_hint01.xml after fix for DROOLS-1174

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1187?page=com.atlassian.jira.plugi... ] Jiri Locker reassigned DROOLS-1187: ----------------------------------- Assignee: Jiri Locker (was: Mario Fusco) > Score corruption (regression) in nurse rostering long_hint01.xml after fix for DROOLS-1174 > ------------------------------------------------------------------------------------------ > > Key: DROOLS-1187 > URL: https://issues.jboss.org/browse/DROOLS-1187 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta1 > Reporter: Geoffrey De Smet > Assignee: Jiri Locker > > the new mole after whacking the mole of DROOLS-1174... > {code} > ava.lang.IllegalStateException: Score corruption: the workingScore (0hard/-85soft) is not the uncorruptedScore (0hard/-86soft) after completedAction ([[2010-01-11/D, 2010-01-12/L, 2010-01-13/L, 2010-01-14/L] {? -> 16}, [2010-01-14/DH, 2010-01-15/E, 2010-01-16/L, 2010-01-17/L] {? -> 29}]): > The corrupted scoreDirector has no ConstraintMatch(s) which are in excess. > The corrupted scoreDirector has 1 ConstraintMatch(s) which are missing: > org.optaplanner.examples.nurserostering.solver/maximumConsecutiveWorkingWeekends/level1/[18 is working the weekend of 2 - 23, 18, 0-CONSECUTIVE_WORKING_WEEKENDS]=-1 > Check your score constraints. > at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertWorkingScoreFromScratch(AbstractScoreDirector.java:418) > at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertWorkingScoreFromScratch(DefaultSolverScope.java:118) > at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertWorkingScoreFromScratch(AbstractPhaseScope.java:167) > at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.processMove(LocalSearchDecider.java:167) > at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.doMove(LocalSearchDecider.java:153) > at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.decideNextStep(LocalSearchDecider.java:125) > at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:63) > at org.optaplanner.core.impl.solver.DefaultSolver.runPhases(DefaultSolver.java:229) > at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:191) > at org.optaplanner.examples.common.app.SolveAllTurtleTest.buildAndSolve(SolveAllTurtleTest.java:75) > at org.optaplanner.examples.common.app.SolveAllTurtleTest.runFastAndFullAssert(SolveAllTurtleTest.java:59) > 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6651) Deprecate servlet 'check-interval' attribute

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6651?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6651: ------------------------------ Fix Version/s: 10.1.0.Final > Deprecate servlet 'check-interval' attribute > -------------------------------------------- > > Key: WFLY-6651 > URL: https://issues.jboss.org/browse/WFLY-6651 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Ingo Weiss > Assignee: Tomaz Cerar > Fix For: 10.1.0.Final > > > This attribute is no longer used in WildFly so should be deprecated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-933) The root cause of login module failures gets lost when multiple login modules are stacked

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/SECURITY-933?page=com.atlassian.jira.plug... ] Tomas Hofman updated SECURITY-933: ---------------------------------- Git Pull Request: https://github.com/wildfly-security/jboss-negotiation/pull/27, https://github.com/picketbox/picketbox/pull/57/ (was: https://github.com/wildfly-security/jboss-negotiation/pull/27) > The root cause of login module failures gets lost when multiple login modules are stacked > ----------------------------------------------------------------------------------------- > > Key: SECURITY-933 > URL: https://issues.jboss.org/browse/SECURITY-933 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: Negotiation_3_0_1_Final > > > https://bugzilla.redhat.com/show_bug.cgi?id=1288668 > The root cause of login module failures gets lost when multiple login modules are stacked and the "flag" attribute is set to "optional". > When the login attempt fails (invalid bindCredential on the LdapExtLoginModule for example) the authentication request will continue to the next login module in the stack. In this situation, the exceptions "cause" attribute is getting overwritten during the processing of the other login modules. This results in the actual cause to get lost during processing. > This makes troubleshooting authentication failures difficult. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6651) Deprecate servlet 'check-interval' attribute

by Ingo Weiss (JIRA)

Ingo Weiss created WFLY-6651: -------------------------------- Summary: Deprecate servlet 'check-interval' attribute Key: WFLY-6651 URL: https://issues.jboss.org/browse/WFLY-6651 Project: WildFly Issue Type: Enhancement Components: Web (Undertow) Affects Versions: 10.0.0.Final Reporter: Ingo Weiss Assignee: Tomaz Cerar This attribute is no longer used in WildFly so should be deprecated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-938) JBossSecuritySubjectFactory should check the root cause exception when AuthenticationManager.isValid() returns false

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/SECURITY-938?page=com.atlassian.jira.plug... ] Lin Gao commented on SECURITY-938: ---------------------------------- Increase priority to Critical, because it blocks another Critical Issue: https://issues.jboss.org/browse/WFLY-6372 > JBossSecuritySubjectFactory should check the root cause exception when AuthenticationManager.isValid() returns false > -------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-938 > URL: https://issues.jboss.org/browse/SECURITY-938 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > > When some login-modules failed, JBossSecuritySubjectFactory will swallow the root cause of the LoginException, which will hide the message of the root cause. > The suspicious code is at: [JBossSecuritySubjectFactory.createSubject()|https://github.com/jbossas/re...] method, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-938) JBossSecuritySubjectFactory should check the root cause exception when AuthenticationManager.isValid() returns false

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/SECURITY-938?page=com.atlassian.jira.plug... ] Lin Gao updated SECURITY-938: ----------------------------- Priority: Critical (was: Major) > JBossSecuritySubjectFactory should check the root cause exception when AuthenticationManager.isValid() returns false > -------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-938 > URL: https://issues.jboss.org/browse/SECURITY-938 > Project: PicketBox > Issue Type: Bug > Components: PicketBox > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Critical > > When some login-modules failed, JBossSecuritySubjectFactory will swallow the root cause of the LoginException, which will hide the message of the root cause. > The suspicious code is at: [JBossSecuritySubjectFactory.createSubject()|https://github.com/jbossas/re...] method, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6639) Upgrade IronJacamar from 1.3.3.Final to 1.3.4.Final

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-6639?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-6639: -------------------------------- Priority: Blocker (was: Major) > Upgrade IronJacamar from 1.3.3.Final to 1.3.4.Final > --------------------------------------------------- > > Key: WFLY-6639 > URL: https://issues.jboss.org/browse/WFLY-6639 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Blocker > Labels: downstream_dependency > > If the password for any datasource is invalid, and there are multiple datasources defined, it is difficult to identify the problematic datasource from the the console log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6650) Cannot enable infinispan batching

by Julien Guillot (JIRA)

Julien Guillot created WFLY-6650: ------------------------------------ Summary: Cannot enable infinispan batching Key: WFLY-6650 URL: https://issues.jboss.org/browse/WFLY-6650 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.Final Reporter: Julien Guillot Assignee: Paul Ferraro Priority: Minor Creating a TreeCache from a cache configured in standalone.xml fails with error:"invocationBatching is not enabled", whereas cache is configured with transaction mode BATCH. I'm not sure this configuration is right, [documentation|https://docs.jboss.org/author/display/WFLY10/Infinispan+Sub...] seems outdated. Cache configuration is: {noformat} <cache-container name="testContainer" jndi-name="java:jboss/infinispan/container/testContainer"> <local-cache name="testCache"> <transaction mode="BATCH"/> <eviction strategy="LRU" max-entries="43210"/> </local-cache> </cache-container> {noformat} Tree cache creation code: {code:java} @Resource(lookup = "java:jboss/infinispan/cache/testContainer/testCache") private Cache<String, String> testBaseCache; @PostConstruct public void onStartup() { debugInfo(); new TreeCacheFactory().createTreeCache(this.testBaseCache); } {code} Error: {noformat} ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 64) MSC000001: Failed to start service jboss.deployment.subunit."test-wfy10-cache-tree.ear-0.0.0-SNAPSHOT.ear"."test-wfy10-cache-tree.jar.jar".component.TreeCacheBean.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."test-wfy10-cache-tree.ear-0.0.0-SNAPSHOT.ear"."test-wfy10-cache-tree.jar.jar".component.TreeCacheBean.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6632) Unable to create replicated cache

by Vinay Lodha (JIRA)

[ https://issues.jboss.org/browse/WFLY-6632?page=com.atlassian.jira.plugin.... ] Vinay Lodha updated WFLY-6632: ------------------------------ Attachment: setp 5 server.log > Unable to create replicated cache > ---------------------------------- > > Key: WFLY-6632 > URL: https://issues.jboss.org/browse/WFLY-6632 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.2.Final > Reporter: Vinay Lodha > Assignee: Paul Ferraro > Attachments: server.log, setp 5 server.log, spring2-mvc-xml-hello-world-1.0-SNAPSHOT.war, spring2-mvc-xml.zip, standalone.xml > > > servers is unable to create replicated or distributed infinispan cache, -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016