[JBoss JIRA] (JGRP-2120) Headers.resize() called unnecessarily
by Bela Ban (JIRA)
Bela Ban created JGRP-2120:
------------------------------
Summary: Headers.resize() called unnecessarily
Key: JGRP-2120
URL: https://issues.jboss.org/browse/JGRP-2120
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 4.0
Each message has space for 4 headers. When a 5th header needs to be added, the array needs to be resized. This is something we want to avoid as much as possible.
However, the following scenario can lead to resizing:
* A bundler writes a message list with (say) 3 headers
* A message list always ignores the transport header, as it is only used to carry the cluster name, but that name is available in the batch header, too.
* Therefore, the size of the headers written is 2 and the transport header is not written
* On the receiver side, when reading the batch, we create and read 2 headers
** This is OK, as message batches are matched against the receiver's cluster name using the cluster name shipped in the batch itself and not in the message
** Message batches are therefore passed up without the individual messages carrying a transport header
* However, single messages need to carry a transport header as it will be used to do the cluster name matching
* Now, if a batch contains messages tagged as {{OOB|DONT_BUNDLE}}, they will be removed from the batch and sent up the stack as separate messages, each in a separate thread.
* To do this, each of these messages is added a transport header (created using the batch's cluster name).
* However, this necessitates a resizing as the headers array has a length of only 2, but we now need 3 headers
Note that we don't run into this in 4.0, as Infinispan 9 (which uses 4) doesn't use {{DONT_BUNDLE}} any longer. It is still an unnecessary memory allocation and needs to be optimized.
However, we should fix it in 3.6 as we still use {{DONT_BUNDLE}} in Infinispan 8.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (DROOLS-1337) A FQN inline cast followed by a method invocation causes an ArrayIndexOutOfBoundsException
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1337?page=com.atlassian.jira.plugi... ]
Matteo Mortari reassigned DROOLS-1337:
--------------------------------------
Assignee: Matteo Mortari (was: Mario Fusco)
> A FQN inline cast followed by a method invocation causes an ArrayIndexOutOfBoundsException
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-1337
> URL: https://issues.jboss.org/browse/DROOLS-1337
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Matteo Mortari
>
> An inline cast using a fully qualified name followed by a method invocation causes an ArrayIndexOutOfBoundsException as in the following test case:
> {code}
> @Test
> public void testInlineCastWithFQNAndMethodInvocation() throws Exception {
> String str =
> "import org.drools.compiler.Person;\n" +
> "global java.util.List list;\n" +
> "rule R1 when\n" +
> " Person( name == \"mark\", $x : address#org.drools.compiler.LongAddress.country.substring(1) )\n" +
> "then\n" +
> " list.add($x);" +
> "end\n";
> KnowledgeBase kbase = loadKnowledgeBaseFromString(str);
> StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession();
> List<String> list = new ArrayList<String>();
> ksession.setGlobal( "list", list );
> Person mark1 = new Person("mark");
> mark1.setAddress(new LongAddress("uk"));
> ksession.insert(mark1);
> assertEquals(1, ksession.fireAllRules());
> assertEquals(1, list.size());
> assertEquals("k", list.get(0));
> ksession.dispose();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ELY-676) There isn't possible change value for given alias in Credential Store over CLI.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-676:
--------------------------------
Summary: There isn't possible change value for given alias in Credential Store over CLI.
Key: ELY-676
URL: https://issues.jboss.org/browse/ELY-676
Project: WildFly Elytron
Issue Type: Bug
Components: Credential Store
Affects Versions: 1.1.0.Beta10
Reporter: Hynek Švábek
Assignee: Peter Skopek
There isn't possible change value for given alias in Credential Store over CLI.
I expected something like this
{code}
/subsystem=elytron/credential-store=credStore/alias=entryAlias:update(secret-value=newSecretValue)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ELY-652) There isn't possibility set entry-type for new entry in Credential Store.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-652?page=com.atlassian.jira.plugin.sy... ]
Hynek Švábek updated ELY-652:
-----------------------------
Component/s: Credential Store
> There isn't possibility set entry-type for new entry in Credential Store.
> -------------------------------------------------------------------------
>
> Key: ELY-652
> URL: https://issues.jboss.org/browse/ELY-652
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
>
> There isn't possibility set entry-type for new entry in Credential Store
> This CLI command
> {code}
> /subsystem=elytron/credential-store=testCS/alias=aliasEntryType:add(secret-value=secretVALUE, entry-type=org.wildfly.security.credential.PasswordCredential)
> {code}
> ends with
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: WFLYELY00909: Credential store 'testCS' does not support given credential store entry type 'org.wildfly.security.credential.PasswordCredential'",
> "rolled-back" => true
> }
> {code}
> *Server log:*
> {code}
> 10:30:39,074 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 18) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("credential-store" => "testCS"),
> ("alias" => "aliasEntryType")
> ]): java.lang.IllegalArgumentException: WFLYELY00909: Credential store 'testCS' does not support given credential store entry type 'org.wildfly.security.credential.PasswordCredential'
> at org.wildfly.extension.elytron.CredentialStoreAliasDefinition$AddHandler.performRuntime(CredentialStoreAliasDefinition.java:166)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (WFLY-7357) 'cipher' vs 'cypher' in Undertow attribute description
by Jan Stourac (JIRA)
[ https://issues.jboss.org/browse/WFLY-7357?page=com.atlassian.jira.plugin.... ]
Jan Stourac moved JBEAP-6531 to WFLY-7357:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7357 (was: JBEAP-6531)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Web (Undertow)
(was: Web (Undertow))
Affects Version/s: 10.1.0.Final
(was: 7.1.0.DR6)
> 'cipher' vs 'cypher' in Undertow attribute description
> ------------------------------------------------------
>
> Key: WFLY-7357
> URL: https://issues.jboss.org/browse/WFLY-7357
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final
> Reporter: Jan Stourac
> Assignee: Stuart Douglas
> Priority: Trivial
>
> In Undertow https-listener, there is an attribute 'enabled-cipher-suites' witch description 'Configures Enabled SSL cyphers'. See that attribute contains 'cipher' and description 'cypher'. I believe we should keep those consistent.
> I have grepped source codebase of Undertow, Wildfly and EAP docs and it seems that except this (and related) we prefer 'cipher' spelling. Thus we should reword description of mentioned attribute too.
> Appropriate change needs to be done also in documentation, where https-listener attributes description is mentioned.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months