[JBoss JIRA] (JBJCA-1259) Tracer improvements
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1259?page=com.atlassian.jira.plugin... ]
Jesper Pedersen resolved JBJCA-1259.
------------------------------------
Resolution: Done
> Tracer improvements
> -------------------
>
> Key: JBJCA-1259
> URL: https://issues.jboss.org/browse/JBJCA-1259
> Project: IronJacamar
> Issue Type: Task
> Components: Core
> Reporter: Jesper Pedersen
> Assignee: Jesper Pedersen
> Fix For: 1.2.4.Final
>
>
> Add the following events:
> * PUSH_CCM_CONTEXT
> * POP_CCM_CONTEXT
> * REGISTER_CCM_CONNECTION
> * UNREGISTER_CCM_CONNECTION
> * CCM_USER_TRANSACTION
> * UNKNOWN_CCM_CONNECTION
> * CLOSE_CCM_CONNECTION
> * VERSION
> Add 2nd payload field
> Create reports for CCM interaction
> Add -ignore-tracking command line option
> Reference guides for connections, connection listeners and managed connection pools
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-687) Helpful error message for MvelConstraint
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-687?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-687:
------------------------------------------------
Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1182517|https://bugzilla.redhat.com/show_bug.cgi?id=1182517] from ON_QA to VERIFIED
> Helpful error message for MvelConstraint
> ----------------------------------------
>
> Key: DROOLS-687
> URL: https://issues.jboss.org/browse/DROOLS-687
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.2.0.CR4
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 6.2.0.Final
>
>
> When you hit NullPointerException with LHS constraint during runtime, the error message is not very helpful for users to detect the root cause.
> For example,
> {noformat}
> rule 'hello person'
> when
> Person( address.street == 'abbey' )
> then
> end
> {noformat}
> If Person.address is null, the error message is:
> {noformat}
> [Error: null pointer: address.street]
> [Near : {... address.street == "abbey" ....}]
> ^
> [Line: 1, Column: 1]
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:427)
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:140)
> at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159)
> at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115)
> at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:117)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86)
> 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:226)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:183)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:138)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> 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:281)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:241)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1481)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1436)
> at org.drools.compiler.integrationtests.Misc2Test.testMvelConstraintErrorMessage(Misc2Test.java:7086)
> ...
> Caused by: java.lang.NullPointerException
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:393)
> ... 46 more
> {noformat}
> Users cannot identify which rule is associated with the constraint when they have many similar rules. Also users cannot identify which fact (Person) caused the issue when they insert many facts.
> I'm not sure if it's really possible to provide a better message in this case. But I filed this as an enhancement request.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4385) Authentication is not propagated to EJB in the login request
by Paulo Cesar Silva Reis (JIRA)
[ https://issues.jboss.org/browse/WFLY-4385?page=com.atlassian.jira.plugin.... ]
Paulo Cesar Silva Reis commented on WFLY-4385:
----------------------------------------------
Good morning,
Do we have any news about this? Could you reproduce the problem?
I'm still facing this issue with 8.2.0.Final. Let me know if theres anything that I can do to help you out.
Thanks.
> Authentication is not propagated to EJB in the login request
> ------------------------------------------------------------
>
> Key: WFLY-4385
> URL: https://issues.jboss.org/browse/WFLY-4385
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.2.0.Final
> Environment: MAC OSX YOSEMITE
> JAVA ORACLE 1.8
> WILDFLY 8.2.0.FINAL STANDALONE
> Reporter: Paulo Cesar Silva Reis
> Assignee: Darran Lofthouse
> Labels: authentication, ejb, http, login, roles, web
> Attachments: wildfly-4385.zip
>
>
> I'm migrating from glassfish to wildfly and noticed few weird things.
> When you perform login through web container (request.login(user, pwd)), the principal is not propagated to EJB Container, only for web container.
> To test that, this is what I did:
> . BASIC AUTH
> . EJB receives HttpServletRequest with user data and perform login
> . Print request.getUserPrincipal() => ok, logged in
> . Print EJBContext.getCallerPrincipal() => anonymous
> This happens in the same request that user logged in. In the subsequent requests (using Set-Cookie response and cookie with JSESSIONID in request), the EJB is aware of the authentication.
> Is that the right behavior? 'Cause in glassfish is different, the principal is propagated immediately to EJB.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-687) Helpful error message for MvelConstraint
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-687?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-687:
------------------------------------------------
Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1182517|https://bugzilla.redhat.com/show_bug.cgi?id=1182517] from MODIFIED to ON_QA
> Helpful error message for MvelConstraint
> ----------------------------------------
>
> Key: DROOLS-687
> URL: https://issues.jboss.org/browse/DROOLS-687
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.2.0.CR4
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 6.2.0.Final
>
>
> When you hit NullPointerException with LHS constraint during runtime, the error message is not very helpful for users to detect the root cause.
> For example,
> {noformat}
> rule 'hello person'
> when
> Person( address.street == 'abbey' )
> then
> end
> {noformat}
> If Person.address is null, the error message is:
> {noformat}
> [Error: null pointer: address.street]
> [Near : {... address.street == "abbey" ....}]
> ^
> [Line: 1, Column: 1]
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:427)
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:140)
> at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159)
> at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115)
> at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:117)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86)
> 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:226)
> at org.drools.core.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:183)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:138)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:60)
> 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:281)
> at org.drools.core.common.NamedEntryPoint.insert(NamedEntryPoint.java:241)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1481)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:1436)
> at org.drools.compiler.integrationtests.Misc2Test.testMvelConstraintErrorMessage(Misc2Test.java:7086)
> ...
> Caused by: java.lang.NullPointerException
> at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:393)
> ... 46 more
> {noformat}
> Users cannot identify which rule is associated with the constraint when they have many similar rules. Also users cannot identify which fact (Person) caused the issue when they insert many facts.
> I'm not sure if it's really possible to provide a better message in this case. But I filed this as an enhancement request.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months