November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-785) no MVEL debugger registered to handle breakpoint

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-785?page=com.atlassian.jira.plugin... ] Petr Široký commented on DROOLS-785: ------------------------------------ Thanks a lot for looking at this [~tomasdavidorg]! > no MVEL debugger registered to handle breakpoint > ------------------------------------------------ > > Key: DROOLS-785 > URL: https://issues.jboss.org/browse/DROOLS-785 > Project: Drools > Issue Type: Bug > Components: core engine, eclipse plugin > Affects Versions: 6.2.0.Final, 6.3.0.Final > Environment: Win 7 64, JBoss Developer Studio Version: 8.1.0.GA, JBossAS Tools 3.0.3.Final-v20150325-0035-B129, Java 1.7.0_76 > Reporter: Maurice Betzel > Assignee: Petr Široký > > Executing Drools-Examples 6.0.2.Final from github containing MVEL dialect resulted in runtime exception: > 2015-05-16 14:35:28,603 [main] INFO Found kmodule: file:/C:/Users/x3.mbetzel/Development/workspaces/jboss-drools/drools-examples-62/target/classes/META-INF/kmodule.xml > 2015-05-16 14:35:28,999 [main] INFO KieModule was added: FileKieModule[releaseId=org.drools:drools-examples:6.2.0.Final,file=C:\Users\x3.mbetzel\Development\workspaces\jboss-drools\drools-examples-62\target\classes] > Exception in thread "main" java.lang.RuntimeException: no debugger registered to handle breakpoint > at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) > at org.mvel2.MVEL.executeExpression(MVEL.java:930) > at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:481) > at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:77) > at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62) > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230) > at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:504) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:379) > at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:290) > at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:253) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:370) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:289) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1480) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1422) > at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:65) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-739) Coverity static analysis: Dereference null return value in AbstractDigestMechanism (Elytron)

by Josef Cacek (JIRA)

Josef Cacek created ELY-739: ------------------------------- Summary: Coverity static analysis: Dereference null return value in AbstractDigestMechanism (Elytron) Key: ELY-739 URL: https://issues.jboss.org/browse/ELY-739 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Coverity static-analysis scan found 3 possible calls on null objects in {{AbstractDigestMechanism}} class: https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57604... Method {{wrapConfidentialityProtectedMessage}} {code} cipheredPart = wrapCipher.update(toCipher); // ... cipheredPart may be null byte[] result = new byte[cipheredPart.length + 6]; {code} https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57604... Method {{createCipher}} {code} // the getTransformationSpec may be null - look at DefaultTransformationMapper ciph = Cipher.getInstance(trans.getTransformationSpec(SaslMechanismInformation.Names.DIGEST_MD5, cipher).getTransformation()); {code} https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57604... Method {{unwrapConfidentialityProtectedMessage}} {code} clearText = unwrapCipher.update(message, offset, len - 6); // the clearText may be null in clearText.length System.arraycopy(clearText, clearText.length - 10, hmac, 0, 10); {code} *Suggested improvement* Add null checks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-737) Coverity static analysis: Operands don't affect result in Elytron

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-737?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reassigned ELY-737: --------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Coverity static analysis: Operands don't affect result in Elytron > ----------------------------------------------------------------- > > Key: ELY-737 > URL: https://issues.jboss.org/browse/ELY-737 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Ilia Vassilev > Priority: Minor > Labels: static_analysis > > Coverity static-analysis scan found unnecessary code in the {{DigestQuote.quoteNeeded()}} method on line 43 (currently). > One part of the condition is {{ch >= 0}}, which is always true, because the {{ch}} parameter has {{char}} type. > https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57601... > *Suggested improvement* > Remove the useless {{ch >= 0}} from the expression. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7176) Review x500-attribute-principal-decoder resource in Elytron subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7176?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7176: ----------------------------- Description: Using OIDs not really convenient. See description of JBEAP-6100 for more details. was:See description of JBEAP-6100 for more details. > Review x500-attribute-principal-decoder resource in Elytron subsystem > --------------------------------------------------------------------- > > Key: WFLY-7176 > URL: https://issues.jboss.org/browse/WFLY-7176 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > > Using OIDs not really convenient. > See description of JBEAP-6100 for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-738) Coverity static analysis: Dereference null return value in SingleSignOnServerMechanismFactory (Elytron)

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-738?page=com.atlassian.jira.plugin.sy... ] Josef Cacek updated ELY-738: ---------------------------- Description: Coverity static-analysis scan found possible call on null object in {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method: {code} getTargetMechanism(mechanismName, singleSignOnSession).evaluateRequest(createHttpServerRequest(request, singleSignOnSession)); {code} https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57602... The problem is the {{getTargetMechanism}} call, which just calls an {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method. The {{createAuthenticationMechanism}} doesn't declare it could return null, nevertheless, the implementations use null as fallback (e.g. look at {{ServerMechanismFactoryImpl.createAuthenticationMechanism()}}) *Suggested improvement* I see 2 possible solutions: 1. Declare in javadoc of {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method, that it can return null and add the null-check into the {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method 2. or throw an exception from {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} implementations instead of returning null was: Coverity static-analysis scan found possible call on null object in {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method: {code} getTargetMechanism(mechanismName, singleSignOnSession).evaluateRequest(createHttpServerRequest(request, singleSignOnSession)); {code} The problem is the {{getTargetMechanism}} call, which just calls an {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method. The {{createAuthenticationMechanism}} doesn't declare it could return null, nevertheless, the implementations use null as fallback (e.g. look at {{ServerMechanismFactoryImpl.createAuthenticationMechanism()}}) *Suggested improvement* I see 2 possible solutions: 1. Declare in javadoc of {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method, that it can return null and add the null-check into the {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method 2. or throw an exception from {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} implementations instead of returning null > Coverity static analysis: Dereference null return value in SingleSignOnServerMechanismFactory (Elytron) > ------------------------------------------------------------------------------------------------------- > > Key: ELY-738 > URL: https://issues.jboss.org/browse/ELY-738 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Labels: static_analysis > > Coverity static-analysis scan found possible call on null object in {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method: > {code} > getTargetMechanism(mechanismName, singleSignOnSession).evaluateRequest(createHttpServerRequest(request, singleSignOnSession)); > {code} > https://scan7.coverity.com/reports.htm#v16159/p11778/fileInstanceId=57602... > The problem is the {{getTargetMechanism}} call, which just calls an {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method. > The {{createAuthenticationMechanism}} doesn't declare it could return null, nevertheless, the implementations use null as fallback (e.g. look at {{ServerMechanismFactoryImpl.createAuthenticationMechanism()}}) > *Suggested improvement* > I see 2 possible solutions: > 1. Declare in javadoc of {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method, that it can return null and add the null-check into the {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method > 2. or throw an exception from {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} implementations instead of returning null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-738) Coverity static analysis: Dereference null return value in SingleSignOnServerMechanismFactory (Elytron)

by Josef Cacek (JIRA)

Josef Cacek created ELY-738: ------------------------------- Summary: Coverity static analysis: Dereference null return value in SingleSignOnServerMechanismFactory (Elytron) Key: ELY-738 URL: https://issues.jboss.org/browse/ELY-738 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Coverity static-analysis scan found possible call on null object in {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method: {code} getTargetMechanism(mechanismName, singleSignOnSession).evaluateRequest(createHttpServerRequest(request, singleSignOnSession)); {code} The problem is the {{getTargetMechanism}} call, which just calls an {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method. The {{createAuthenticationMechanism}} doesn't declare it could return null, nevertheless, the implementations use null as fallback (e.g. look at {{ServerMechanismFactoryImpl.createAuthenticationMechanism()}}) *Suggested improvement* I see 2 possible solutions: 1. Declare in javadoc of {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} method, that it can return null and add the null-check into the {{SingleSignOnServerMechanismFactory.evaluateRequst()}} method 2. or throw an exception from {{HttpServerAuthenticationMechanismFactory.createAuthenticationMechanism()}} implementations instead of returning null -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1971) Command auto-completition does not work properly when start typing param value with parenthesis

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1971?page=com.atlassian.jira.plugi... ] Tomas Hofman updated WFCORE-1971: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1929 > Command auto-completition does not work properly when start typing param value with parenthesis > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-1971 > URL: https://issues.jboss.org/browse/WFCORE-1971 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Alpha12 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Minor > > Autocompletition of command in CLI does not work properly when starts writing quotes {{"}} right after equal sign {{=}} and then pressing {{<TAB>}}. > I write > {{/subsystem=transactions/log-store="}} > and then press {{TAB}} > the autocompletion finishes the name but replaces the fist letter for the existing quotes. That leads to have command like > {{/subsystem=transactions/log-store="og-store}} > which is obviously invalid as {{"og-store}} does not exists. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-785) no MVEL debugger registered to handle breakpoint

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/DROOLS-785?page=com.atlassian.jira.plugin... ] Tomas David closed DROOLS-785. ------------------------------ Resolution: Done I tried to reproduce this issue on Eclipse Neon 4.6 with Drools plugin 6.5.0.Final and I didn't see any problem. I am closing this issue. If you see the problem again, please reopen this issue. > no MVEL debugger registered to handle breakpoint > ------------------------------------------------ > > Key: DROOLS-785 > URL: https://issues.jboss.org/browse/DROOLS-785 > Project: Drools > Issue Type: Bug > Components: core engine, eclipse plugin > Affects Versions: 6.2.0.Final, 6.3.0.Final > Environment: Win 7 64, JBoss Developer Studio Version: 8.1.0.GA, JBossAS Tools 3.0.3.Final-v20150325-0035-B129, Java 1.7.0_76 > Reporter: Maurice Betzel > Assignee: Petr Široký > > Executing Drools-Examples 6.0.2.Final from github containing MVEL dialect resulted in runtime exception: > 2015-05-16 14:35:28,603 [main] INFO Found kmodule: file:/C:/Users/x3.mbetzel/Development/workspaces/jboss-drools/drools-examples-62/target/classes/META-INF/kmodule.xml > 2015-05-16 14:35:28,999 [main] INFO KieModule was added: FileKieModule[releaseId=org.drools:drools-examples:6.2.0.Final,file=C:\Users\x3.mbetzel\Development\workspaces\jboss-drools\drools-examples-62\target\classes] > Exception in thread "main" java.lang.RuntimeException: no debugger registered to handle breakpoint > at org.mvel2.debug.DebuggerContext.checkBreak(DebuggerContext.java:98) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:76) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113) > at org.mvel2.MVEL.executeExpression(MVEL.java:930) > at org.drools.core.util.MVELSafeHelper$RawMVELEvaluator.executeExpression(MVELSafeHelper.java:481) > at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:77) > at org.drools.core.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:62) > at org.drools.core.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:230) > at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:187) > at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:141) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:504) > at org.drools.core.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:379) > at org.drools.core.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:290) > at org.drools.core.reteoo.EntryPointNode.assertObject(EntryPointNode.java:253) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:370) > at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:289) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1480) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1422) > at org.drools.examples.helloworld.HelloWorldExample.main(HelloWorldExample.java:65) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7555) Upgrade Infinispan to 8.2.5.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7555?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7555: --------------------------------- Description: Version including backports in ISPN-7101. (was: Version including backports by ISPN-6751.) > Upgrade Infinispan to 8.2.5.Final > --------------------------------- > > Key: WFLY-7555 > URL: https://issues.jboss.org/browse/WFLY-7555 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > Version including backports in ISPN-7101. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1969) JBoss CLI authentication ctrl+c results in errors

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1969?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1969: ------------------------------------------ I have also seen issues recently in this area with Ctrl+D > JBoss CLI authentication ctrl+c results in errors > ------------------------------------------------- > > Key: WFCORE-1969 > URL: https://issues.jboss.org/browse/WFCORE-1969 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016