[JBoss JIRA] (WFCORE-521) setting the local to english in CLI commands on non-english systems does not produce english output
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-521?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3723 to WFCORE-521:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-521 (was: WFLY-3723)
Affects Version/s: 1.0.0.Alpha15
(was: 8.1.0.Final)
Component/s: Domain Management
(was: Localization)
> setting the local to english in CLI commands on non-english systems does not produce english output
> ---------------------------------------------------------------------------------------------------
>
> Key: WFCORE-521
> URL: https://issues.jboss.org/browse/WFCORE-521
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha15
> Environment: Tested on MacOS running in German
> Reporter: Tom Fonteyne
> Assignee: Romain Pelisse
> Priority: Minor
>
> A German (or french etc...) system must be used to reproduce.
> It is likely this is not limited to MacOS, but I do not have a non-english Linux system available
> An out of the box install of wildfly/EAP:
> Without configuration, the log file is in German as expected.
> Using these CLI comands:
> :read-operation-description(name=stop-servers,locale=de_DE) -> german
> :read-operation-description(name=stop-servers,locale=en_US) -> german
> :read-operation-description(name=stop-servers,locale=fr_FR) -> french
> So we cannot get the CLI to produce english output
> when configuring JAVA_OPTS in domain.conf with:
> JAVA_OPTS="$JAVA_OPTS -Duser.language=en -Duser.country=DE -Duser.encoding=utf-8
> The log is now in English -> works as expected; and:
> :read-operation-description(name=stop-servers,locale=de_DE) -> german
> :read-operation-description(name=stop-servers,locale=en_US) -> english
> So it seems we have a bug where the locale set to start the domain takes precedence over the locale set in the CLI command (but only when English is asked)
> I presume this is because English is the default locale.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ]
Rafael Benevides commented on WFLY-4171:
----------------------------------------
I'm waiting QSTools 1.5.3.Final to be released as part of ORG-2396
> Provide an html5 archetype for wildfly
> --------------------------------------
>
> Key: WFLY-4171
> URL: https://issues.jboss.org/browse/WFLY-4171
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Fred Bricon
> Assignee: Rafael Benevides
>
> We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are :
> * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final
> * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (ELY-138) Client timed logout options
by David Lloyd (JIRA)
David Lloyd created ELY-138:
-------------------------------
Summary: Client timed logout options
Key: ELY-138
URL: https://issues.jboss.org/browse/ELY-138
Project: WildFly Elytron
Issue Type: Task
Reporter: David Lloyd
Fix For: 1.0.0.Beta1
It should be possible to configure a client-side authentication to auto-logout after either an absolute duration, or after some amount of idle time, or both.
The client-side authentication cache, whatever form it takes, must be aware of usages to update the logout time, for idle timeouts.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-629) NullPointerException thrown on next call to insert and fireAllRules after stream garbage collection runs
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-629?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-629:
------------------------------------------------
Rajesh Rajasekaran <rrajasek(a)redhat.com> changed the Status of [bug 1181584|https://bugzilla.redhat.com/show_bug.cgi?id=1181584] from MODIFIED to ON_QA
> NullPointerException thrown on next call to insert and fireAllRules after stream garbage collection runs
> --------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-629
> URL: https://issues.jboss.org/browse/DROOLS-629
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final, 6.2.0.Beta3
> Reporter: Mike Wilson
> Assignee: Mario Fusco
> Fix For: 6.2.0.CR1
>
> Attachments: drools-gc-causes-npe-example.zip
>
>
> I have observed that the following NullPointerException (NPE) occurs consistently with a very specific set of rules and a very specific set of inputs into a stream session:
> {code}
> java.lang.NullPointerException
> at org.drools.core.util.AbstractHashTable$SingleIndex.equal(AbstractHashTable.java:491)
> at org.drools.core.util.index.LeftTupleList.matches(LeftTupleList.java:266)
> at org.drools.core.util.index.LeftTupleIndexHashTable.get(LeftTupleIndexHashTable.java:434)
> at org.drools.core.util.index.LeftTupleIndexHashTable.getFirst(LeftTupleIndexHashTable.java:217)
> at org.drools.core.reteoo.BetaNode.getFirstLeftTuple(BetaNode.java:443)
> at org.drools.core.phreak.PhreakJoinNode.doRightInserts(PhreakJoinNode.java:144)
> at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:56)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:548)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:534)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:334)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:229)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:98)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:988)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1274)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1281)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1254)
> ...
> {code}
> The exception always occurs on the next call to "insert" and "fireAllRules" after the following method is invoked within the session: org.drools.core.common.DefaultAgenda$DefaultGarbageCollector.forceGcUnlinkedRules().
> I have attached a maven project that contains a JUnit test, which reproduces this exception using Drools version 6.2.0.Beta3.
> A side effect of this exeption occurring in the middle of fireAllRules is that an extra fact is left over in working memory, which is essentially a memory leak. I assume this is because the evaluation of the LHS of the rules is what causes the NPE to occur, so the fact is not deleted, because the RHS of the rules don't execute.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months