[JBoss JIRA] (SECURITY-697) Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/SECURITY-697?page=com.atlassian.jira.plug... ]
jaikiran pai moved AS7-5594 to SECURITY-697:
--------------------------------------------
Project: PicketBox (JBoss Security and Identity Management) (was: Application Server 7)
Key: SECURITY-697 (was: AS7-5594)
Issue Type: Enhancement (was: Feature Request)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: (was: 7.1.2.Final (EAP))
Component/s: (was: Security)
Security: Public
> Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
> -------------------------------------------------------------------------------
>
> Key: SECURITY-697
> URL: https://issues.jboss.org/browse/SECURITY-697
> Project: PicketBox (JBoss Security and Identity Management)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Akram Ben Aissi
>
> The error message related to PB00019 must me more explicit.
> A special case is when the keystore URL provided to vault.sh script points to a non existing file.
> In this case, error message must explicitly state that file does not exist, or URL is not correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-5594) Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
by Akram Ben Aissi (JIRA)
[ https://issues.jboss.org/browse/AS7-5594?page=com.atlassian.jira.plugin.s... ]
Akram Ben Aissi moved JBPAPP-9980 to AS7-5594:
----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5594 (was: JBPAPP-9980)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0)
Component/s: Security
(was: Security)
Security: (was: Public)
Docs QE Status: (was: NEW)
> Improve error message for "PB00019: Processing Failed:Unable to get Keystore: "
> -------------------------------------------------------------------------------
>
> Key: AS7-5594
> URL: https://issues.jboss.org/browse/AS7-5594
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Akram Ben Aissi
>
> The error message related to PB00019 must me more explicit.
> A special case is when the keystore URL provided to vault.sh script points to a non existing file.
> In this case, error message must explicitly state that file does not exist, or URL is not correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBRULES-3632) UnsupportedOperationException on an update call
by Michal Bali (JIRA)
Michal Bali created JBRULES-3632:
------------------------------------
Summary: UnsupportedOperationException on an update call
Key: JBRULES-3632
URL: https://issues.jboss.org/browse/JBRULES-3632
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert), drools-core (expert)
Affects Versions: 5.4.0.Final, 5.5.0.Beta1
Reporter: Michal Bali
Assignee: Mark Proctor
Hi,
I am getting the following exception when calling fireAllRules:
Exception executing consequence for rule "ruleThatFails" in indexingproblem.remove.me.anditworks: java.lang.UnsupportedOperationException
at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1287)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1212)
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1446)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:710)
at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:674)
at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:230)
at com.mycompany.app.IndexingProblemMain.main(IndexingProblemMain.java:36)
Caused by: java.lang.UnsupportedOperationException
at org.drools.reteoo.BaseLeftTuple.getPrevious(BaseLeftTuple.java:480)
at org.drools.core.util.index.LeftTupleList.remove(LeftTupleList.java:114)
at org.drools.core.util.index.LeftTupleList.removeAdd(LeftTupleList.java:68)
at org.drools.reteoo.JoinNode.modifyLeftTuple(JoinNode.java:310)
at org.drools.reteoo.LeftTupleSource.doModifyLeftTuple(LeftTupleSource.java:304)
at org.drools.reteoo.LeftTupleSource.modifyLeftTuple(LeftTupleSource.java:278)
at org.drools.reteoo.JoinNode.modifyLeftTuple(JoinNode.java:437)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.doPropagateModifyLeftTuple(SingleLeftTupleSinkAdapter.java:205)
at org.drools.reteoo.SingleLeftTupleSinkAdapter.propagateModifyObject(SingleLeftTupleSinkAdapter.java:235)
at org.drools.reteoo.LeftInputAdapterNode.modifyObject(LeftInputAdapterNode.java:170)
at org.drools.reteoo.SingleObjectSinkAdapter.propagateModifyObject(SingleObjectSinkAdapter.java:68)
at org.drools.reteoo.AlphaNode.modifyObject(AlphaNode.java:157)
at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateModifyObject(CompositeObjectSinkAdapter.java:507)
at org.drools.reteoo.CompositeObjectSinkAdapter.propagateModifyObject(CompositeObjectSinkAdapter.java:421)
at org.drools.reteoo.ObjectTypeNode.modifyObject(ObjectTypeNode.java:314)
at org.drools.reteoo.EntryPointNode.modifyObject(EntryPointNode.java:265)
at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:483)
at org.drools.common.NamedEntryPoint.update(NamedEntryPoint.java:383)
at org.drools.base.DefaultKnowledgeHelper.update(DefaultKnowledgeHelper.java:337)
at indexingproblem.remove.me.anditworks.Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96ca.defaultConsequence(Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96ca.java:9)
at indexingproblem.remove.me.anditworks.Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96caDefaultConsequenceInvokerGenerated.evaluate(Unknown Source)
at indexingproblem.remove.me.anditworks.Rule_ruleThatFails_b159773c7b1a41a2a93044d2816b96caDefaultConsequenceInvoker.evaluate(Unknown Source)
at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1277)
... 6 more
I have tried to create a minimal test case that recreates this issue, here it is:
package indexingproblem.remove.me.anditworks;
declare Criteria
processed : boolean
end
declare CheeseCriteria extends Criteria
end
rule setUp
salience 10000
when
then
insert(new CheeseCriteria());
end
rule aaa
when
CheeseCriteria( )
then
end
rule bbb
when
CheeseCriteria( )
then
end
rule ccc
when
CheeseCriteria( )
then
end
rule eeeFalse
when
Criteria( processed == false )
then
end
declare Filter
end
rule fffTrue
when
Criteria( processed == true )
Filter( )
then
end
rule ruleThatFails
when
$criteria : Criteria( processed == false )
then
modify($criteria) {
setProcessed(true)
}
end
This is working fine with 5.3.0.Final. But it is failing with 5.4.0.Final and also 5.5.0-SNAPSHOT. Note that if you change the rule package to be "package indexingproblem" the exception is not thrown. The code for building the KnowledgeBase is standard, I haven't used any additional options. No fact is inserted only one fireAllRules call.
Thanking you.
Best regards,
Michal
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBRULES-3515) Getting runtime exception while I remove a validation Rule in version 5.4
by Premasis S (JIRA)
Premasis S created JBRULES-3515:
-----------------------------------
Summary: Getting runtime exception while I remove a validation Rule in version 5.4
Key: JBRULES-3515
URL: https://issues.jboss.org/browse/JBRULES-3515
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.4.0.Final
Reporter: Premasis S
Assignee: Mark Proctor
I am getting the following exception while removing/disabling a Drool Validation Rule, using Drools Version 5.4.FINAL
i.e when I call - knowledgeBase.removeRule("pkg.trade", "2.8.I23");
java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:980)
at java.util.HashMap$EntryIterator.next(HashMap.java:1018)
at java.util.HashMap$EntryIterator.next(HashMap.java:1016)
at org.drools.reteoo.EvalConditionNode.doRemove(EvalConditionNode.java:302)
at org.drools.common.BaseNode.remove(BaseNode.java:109)
at org.drools.reteoo.FromNode.doRemove(FromNode.java:440)
at org.drools.common.BaseNode.remove(BaseNode.java:109)
at org.drools.reteoo.RightInputAdapterNode.doRemove(RightInputAdapterNode.java:285)
at org.drools.common.BaseNode.remove(BaseNode.java:109)
at org.drools.reteoo.BetaNode.doRemove(BetaNode.java:499)
at org.drools.common.BaseNode.remove(BaseNode.java:109)
at org.drools.reteoo.RuleTerminalNode.doRemove(RuleTerminalNode.java:358)
at org.drools.common.BaseNode.remove(BaseNode.java:109)
at org.drools.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:261)
at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:460)
at org.drools.common.AbstractRuleBase.removeRule(AbstractRuleBase.java:1107)
at org.drools.common.AbstractRuleBase.removeRule(AbstractRuleBase.java:1085)
at org.drools.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:210)
Here is the Rule:
package pkg.trade;
rule "2.8.I23"
when
$trade : Trade()
$trdDeskId : Id() from mediator.getTradingDeskId($trade)
eval(isPositiveId($trdDeskId))
eval($trdDeskId != null && !mediator.isValidTradingDesk($trdDeskId))
then
raiseException(kcontext, $trade, "tradingDeskId", stringValue($trdDeskId));
end
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-5564) @EJB doesn't work for JSF 1.2
by Stan Silvert (JIRA)
Stan Silvert created AS7-5564:
---------------------------------
Summary: @EJB doesn't work for JSF 1.2
Key: AS7-5564
URL: https://issues.jboss.org/browse/AS7-5564
Project: Application Server 7
Issue Type: Bug
Components: JSF
Affects Versions: 7.1.2.Final (EAP)
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: 7.2.0.Alpha1
If you use the JSF 1.2 implementation that ships with AS, then if you use @EJB with JSF managed beans then the EJB will not be injected. As a workaround you can get a reference via JNDI.
For the fix, we need to break out the injection classes into a separate module. This way, we can make the JSFInjectionProvider link to the interface in the proper JSF impl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-3975) EJB client invocations sometimes hang indefinitely
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3975:
-----------------------------------
Summary: EJB client invocations sometimes hang indefinitely
Key: AS7-3975
URL: https://issues.jboss.org/browse/AS7-3975
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.1.Final
When running a EJB stress test when the test is over some clients hang indefinitely.
This is a positive test, there are no failures being injected in the test.
{noformat}
"Runner - 16" daemon prio=10 tid=0x00007fb7a0025000 nid=0x4d7a in Object.wait() [0x00007fb78b3f2000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:330)
- locked <0x00000006c013ae50> (a java.lang.Object)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:140)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy0.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
{noformat}
I originally filed a feature request to implement a timeout AS7-3811, needless to say this needs to get fixed first.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (LOGMGR-51) Allow any filter type to be specified
by James Perkins (JIRA)
James Perkins created LOGMGR-51:
-----------------------------------
Summary: Allow any filter type to be specified
Key: LOGMGR-51
URL: https://issues.jboss.org/browse/LOGMGR-51
Project: JBoss Log Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: James Perkins
Assignee: James Perkins
Currently handlers only allow for expressions of the JBoss Log Manager's filters. This should allow named filters, e.g. filters defined in the configuration, to be specified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (AS7-5591) Add color mapping property
by James Perkins (JIRA)
James Perkins created AS7-5591:
----------------------------------
Summary: Add color mapping property
Key: AS7-5591
URL: https://issues.jboss.org/browse/AS7-5591
Project: Application Server 7
Issue Type: Feature Request
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
<Nihility> jamezp: hey next time you update the logging management model, could you expose the colormap formatter property?
<Nihility> <pattern-formatter pattern="blah" colormap="error:blue, brightgreen:warn, yellow debug"/>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBBUILD-720) Change modeshape-tools-continuous Jenkins Job Update-Site Output Directory
by Dan Florian (JIRA)
Dan Florian created JBBUILD-720:
-----------------------------------
Summary: Change modeshape-tools-continuous Jenkins Job Update-Site Output Directory
Key: JBBUILD-720
URL: https://issues.jboss.org/browse/JBBUILD-720
Project: JBoss Build System
Issue Type: Task
Components: Maven Builds
Affects Versions: Build Support 2011
Reporter: Dan Florian
Assignee: Nick Boldt
The modeshape-tools-continuous job outputs the ModeShape Tools update-site to here:
/downloads_htdocs/modeshape/builds/staging/modeshape-tools-continuous/all/repo
We would like the path to be (something like) this:
/downloads_htdocs/modeshape/tools/update/{stable|develop}/{helios|indigo|juno|etc}
At a minimum, the path needs to have the "tools" segment as this identifies it from the ModeShape project. What do other projects do as far as stable vs. develop build? Do other project's put the Eclipse release in the path? Please see MODE-1506 for additional questions/discussion.
I was told to get with you on this Nick. Please update this issue's project and component as appropriate as I wasn't sure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years