[JBoss JIRA] (WFCORE-1921) Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1921?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-1921:
-------------------------------------
Problem is on client already as CLI sends operation to server without leading zeros.
I've managed to boil down problem to ModelNode.fromString(value)
which in case you pass "[001,111]" which is a list returns back
ModelNode with contents:
[
1,
111
]
> Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1921
> URL: https://issues.jboss.org/browse/WFCORE-1921
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Reporter: Hynek Švábek
> Assignee: Tomaz Cerar
>
> Problem with resources which name contains only NUMBERS.
> Particularly the number which beginning with ZERO(s).
> *Scenario*
> * I have resources which name contains only numbers with ZERO(s) prefix
> * I want set capability-reference to it
> * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111])
> *Actual result*
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.",
> "rolled-back" => true
> }
> {code}
> *Expected result*
> {code}
> Success
> {code}
> *NOTE*
> In my opinion is this global problem.
> I tried it with another subsystem and problem is there too.
> {code}
> /subsystem=datasources/data-source=001:add(connection-url="url", jndi-name="java:jboss/datasources/001", driver-name=h2)
> /subsystem=infinispan/cache-container=server/local-cache=default/store=string-jdbc:add(data-source=001)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-1921) Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1921?page=com.atlassian.jira.plugi... ]
Tomaz Cerar updated WFCORE-1921:
--------------------------------
Component/s: Domain Management
> Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1921
> URL: https://issues.jboss.org/browse/WFCORE-1921
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Reporter: Hynek Švábek
> Assignee: Tomaz Cerar
>
> Problem with resources which name contains only NUMBERS.
> Particularly the number which beginning with ZERO(s).
> *Scenario*
> * I have resources which name contains only numbers with ZERO(s) prefix
> * I want set capability-reference to it
> * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111])
> *Actual result*
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.",
> "rolled-back" => true
> }
> {code}
> *Expected result*
> {code}
> Success
> {code}
> *NOTE*
> In my opinion is this global problem.
> I tried it with another subsystem and problem is there too.
> {code}
> /subsystem=datasources/data-source=001:add(connection-url="url", jndi-name="java:jboss/datasources/001", driver-name=h2)
> /subsystem=infinispan/cache-container=server/local-cache=default/store=string-jdbc:add(data-source=001)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-1921) Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1921?page=com.atlassian.jira.plugi... ]
Tomaz Cerar updated WFCORE-1921:
--------------------------------
Component/s: CLI
(was: Domain Management)
> Problem with capability-reference to resource whose name is number with ZERO(s) prefix.
> ---------------------------------------------------------------------------------------
>
> Key: WFCORE-1921
> URL: https://issues.jboss.org/browse/WFCORE-1921
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Hynek Švábek
> Assignee: Tomaz Cerar
>
> Problem with resources which name contains only NUMBERS.
> Particularly the number which beginning with ZERO(s).
> *Scenario*
> * I have resources which name contains only numbers with ZERO(s) prefix
> * I want set capability-reference to it
> * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111])
> *Actual result*
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0369: Required capabilities are not available:
> org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.",
> "rolled-back" => true
> }
> {code}
> *Expected result*
> {code}
> Success
> {code}
> *NOTE*
> In my opinion is this global problem.
> I tried it with another subsystem and problem is there too.
> {code}
> /subsystem=datasources/data-source=001:add(connection-url="url", jndi-name="java:jboss/datasources/001", driver-name=h2)
> /subsystem=infinispan/cache-container=server/local-cache=default/store=string-jdbc:add(data-source=001)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (ELY-813) CredentialStore operations can be slow
by David Lloyd (JIRA)
David Lloyd created ELY-813:
-------------------------------
Summary: CredentialStore operations can be slow
Key: ELY-813
URL: https://issues.jboss.org/browse/ELY-813
Project: WildFly Elytron
Issue Type: Bug
Components: Credential Store
Reporter: David Lloyd
Credential store operations can be slow, as they generally flush the updated store to disk after every operation making multiple changes undergo many pointless flushes. We can solve this a number of different possible ways:
* Make CredentialStore use the same access pattern as KeyStore, where the user is responsible for flushing changes when they are complete, putting the user in charge of storage details (user is responsible for concurrency control)
* Make CredentialStore implement a {{flush()}} method (and {{hasUnflushedChanges()}} method) which performs the persistence step separately at a time of the user's choosing (user is responsible for concurrency control) (memory-backed stores always return {{false}} for {{hasUnflushedChanges()}}) (this is my preferred approach)
* Implement a transaction API in CredentialStore to allow concurrent non-conflicting updates with lock protection, isolation, atomicity, and consistency properties (credential store manages concurrency control via lock/transaction objects)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JGRP-2140) Replace Table with RingBuffer in UNICAST3 and NAKACK2
by Bela Ban (JIRA)
Bela Ban created JGRP-2140:
------------------------------
Summary: Replace Table with RingBuffer in UNICAST3 and NAKACK2
Key: JGRP-2140
URL: https://issues.jboss.org/browse/JGRP-2140
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.1
Table does allocate memory on resizing or compaction; whereas RingBuffer doesn't. Replacing Table with RingBuffer might bring memory allocation rates even further down.
However, using RingBuffer as message store means that the capacity is fixed; when the RingBuffer is full, messages would get dropped. This should not be a big issue as they will get retransmitted anyway, and flow control should actually kick in to throttle senders (this is done now, to prevent Table from growing out of bounds).
Measure the impact on performance. Table is a critical class used by NAKACK2 and UNICAST3, and is battle tested. Do this only if the benefits trump the risk.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7730) Problem in undertow application-security-domain removing
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7730?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-7730:
-----------------------------
Affects Version/s: 11.0.0.Alpha1
> Problem in undertow application-security-domain removing
> --------------------------------------------------------
>
> Key: WFLY-7730
> URL: https://issues.jboss.org/browse/WFLY-7730
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> Following error when try to remove *undertow.application-security-domain*:
> java.lang.IllegalArgumentException: WFLYCTL0394: Capability 'org.wildfly.extension.undertow.application-security-domain.ejb3-tests' does not provide services of type 'class org.wildfly.security.auth.server.HttpAuthenticationFactory'
> Problem is wrong type in obtaining service in RemoveHandler.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7730) Problem in undertow application-security-domain removing
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7730?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-7730:
-----------------------------
Component/s: Web (Undertow)
> Problem in undertow application-security-domain removing
> --------------------------------------------------------
>
> Key: WFLY-7730
> URL: https://issues.jboss.org/browse/WFLY-7730
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 11.0.0.Alpha1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> Following error when try to remove *undertow.application-security-domain*:
> java.lang.IllegalArgumentException: WFLYCTL0394: Capability 'org.wildfly.extension.undertow.application-security-domain.ejb3-tests' does not provide services of type 'class org.wildfly.security.auth.server.HttpAuthenticationFactory'
> Problem is wrong type in obtaining service in RemoveHandler.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7731) Lots of clustering builder instances are left in memory after objects are "built"
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-7731?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-7731.
------------------------------
Resolution: Rejected
[~ctomc] In every instance, the Builder object additionally implements either Service<?> or (Value<?> from which a ValueService<?> is created) - so your premise, that the objects are no longer needed, is not true.
> Lots of clustering builder instances are left in memory after objects are "built"
> ---------------------------------------------------------------------------------
>
> Key: WFLY-7731
> URL: https://issues.jboss.org/browse/WFLY-7731
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Alpha1
> Reporter: Tomaz Cerar
> Assignee: Paul Ferraro
>
> There are lots of instances of org.wildfly.clustering.service.Builder hanging round in memory even after server was booted and builders are no longer needed.
> Example of yourkit memory profile
> {noformat}
> +--------------------------------------------------------------------------------------+-------------+----------------+-----------------+
> | Class | Objects | Shallow Size | Retained Size |
> +--------------------------------------------------------------------------------------+-------------+----------------+-----------------+
> | org.jboss.as.clustering.infinispan.subsystem.EvictionBuilder | 7 2 % | 168 2 % | 84,344 11 % |
> | org.jboss.as.clustering.infinispan.subsystem.LockingBuilder | 7 2 % | 112 1 % | 84,288 11 % |
> | org.jboss.as.clustering.infinispan.subsystem.ExpirationBuilder | 7 2 % | 112 1 % | 84,232 11 % |
> | org.jboss.as.clustering.infinispan.subsystem.TransactionBuilder | 7 2 % | 224 2 % | 84,192 11 % |
> | org.jboss.as.clustering.infinispan.subsystem.BackupForBuilder | 5 1 % | 80 1 % | 60,192 8 % |
> | org.jboss.as.clustering.infinispan.subsystem.StateTransferBuilder | 5 1 % | 80 1 % | 60,152 8 % |
> | org.jboss.as.clustering.infinispan.subsystem.PartitionHandlingBuilder | 5 1 % | 80 1 % | 60,112 8 % |
> | org.wildfly.clustering.service.AsynchronousServiceBuilder | 53 15 % | 1,272 13 % | 59,992 8 % |
> | org.wildfly.clustering.infinispan.spi.service.ConfigurationBuilder | 15 4 % | 480 5 % | 45,576 6 % |
> | org.jboss.as.clustering.infinispan.subsystem.FileStoreBuilder | 3 1 % | 144 1 % | 41,048 5 % |
> | org.wildfly.clustering.server.registry.CacheRegistryFactoryBuilder | 14 4 % | 448 4 % | 23,304 3 % |
> | org.wildfly.clustering.server.provider.CacheServiceProviderRegistryBuilder | 14 4 % | 448 4 % | 18,712 2 % |
> | org.jboss.as.clustering.infinispan.subsystem.DistributedCacheBuilder | 3 1 % | 312 3 % | 17,544 2 % |
> | org.wildfly.clustering.server.group.CacheGroupBuilder | 14 4 % | 448 4 % | 16,216 2 % |
> | org.wildfly.clustering.infinispan.spi.service.CacheBuilder | 15 4 % | 480 5 % | 15,368 2 % |
> | org.jboss.as.clustering.infinispan.subsystem.ThreadPoolBuilder | 24 7 % | 576 6 % | 12,288 2 % |
> | org.wildfly.clustering.server.registry.RegistryBuilder | 15 4 % | 480 5 % | 11,672 2 % |
> | org.jboss.as.clustering.jgroups.subsystem.ProtocolConfigurationBuilder | 23 7 % | 920 9 % | 8,720 1 % |
> | org.jboss.as.clustering.infinispan.subsystem.SharedStateCacheBuilder | 2 1 % | 176 2 % | 8,160 1 % |
> | org.jboss.as.clustering.jgroups.subsystem.TransportConfigurationBuilder | 2 1 % | 96 1 % | 7,360 1 % |
> | org.wildfly.clustering.server.group.CacheNodeFactoryBuilder | 15 4 % | 360 4 % | 6,576 1 % |
> | org.jboss.as.clustering.jgroups.subsystem.ProtocolDefaultsBuilder | 1 0 % | 16 0 % | 4,880 1 % |
> | org.jboss.as.clustering.infinispan.subsystem.BackupsBuilder | 5 1 % | 120 1 % | 4,272 1 % |
> | org.jboss.as.clustering.infinispan.subsystem.InvalidationCacheBuilder | 1 0 % | 64 1 % | 4,056 1 % |
> | org.wildfly.clustering.infinispan.spi.service.TemplateConfigurationBuilder | 8 2 % | 192 2 % | 4,048 1 % |
> | org.wildfly.clustering.server.singleton.CacheSingletonServiceBuilderFactoryBuilder | 14 4 % | 448 4 % | 3,328 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.NoStoreBuilder | 4 1 % | 64 1 % | 2,232 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.ScheduledThreadPoolBuilder | 4 1 % | 96 1 % | 2,048 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.JGroupsTransportBuilder | 4 1 % | 128 1 % | 1,984 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.SiteBuilder | 4 1 % | 64 1 % | 1,920 0 % |
> | org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactoryBuilder | 1 0 % | 48 0 % | 1,736 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.GlobalConfigurationBuilder | 4 1 % | 192 2 % | 1,688 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.StoreWriteThroughBuilder | 3 1 % | 48 0 % | 1,640 0 % |
> | org.jboss.as.clustering.jgroups.subsystem.JChannelFactoryBuilder | 2 1 % | 80 1 % | 1,600 0 % |
> | org.jboss.as.clustering.controller.ModuleBuilder | 5 1 % | 160 2 % | 1,128 0 % |
> | org.wildfly.clustering.server.provider.LocalServiceProviderRegistryBuilder | 1 0 % | 24 0 % | 1,064 0 % |
> | org.wildfly.clustering.server.registry.LocalRegistryFactoryBuilder | 1 0 % | 24 0 % | 1,048 0 % |
> | org.wildfly.clustering.server.singleton.AsynchronousSingletonServiceBuilder | 1 0 % | 32 0 % | 1,040 0 % |
> | org.wildfly.clustering.server.group.LocalCacheGroupBuilder | 1 0 % | 24 0 % | 896 0 % |
> | org.wildfly.clustering.server.group.ChannelNodeFactoryBuilder | 1 0 % | 24 0 % | 768 0 % |
> | org.wildfly.clustering.server.group.ChannelGroupBuilder | 1 0 % | 24 0 % | 712 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.LocalCacheBuilder | 1 0 % | 72 1 % | 568 0 % |
> | org.jboss.as.clustering.jgroups.subsystem.ForkChannelFactoryBuilder | 1 0 % | 32 0 % | 496 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder | 4 1 % | 128 1 % | 392 0 % |
> | org.wildfly.extension.clustering.singleton.SimpleElectionPolicyBuilder | 1 0 % | 24 0 % | 384 0 % |
> | org.wildfly.clustering.server.group.LocalGroupBuilder | 1 0 % | 24 0 % | 344 0 % |
> | org.wildfly.clustering.server.group.LocalNodeFactoryBuilder | 1 0 % | 24 0 % | 336 0 % |
> | org.wildfly.extension.clustering.singleton.SingletonPolicyBuilder | 1 0 % | 24 0 % | 208 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.XAResourceRecoveryBuilder | 7 2 % | 168 2 % | 168 0 % |
> | org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder | 1 0 % | 40 0 % | 112 0 % |
> | org.jboss.as.clustering.infinispan.subsystem.KeyAffinityServiceFactoryBuilder | 4 1 % | 64 1 % | 64 0 % |
> | org.jboss.as.ejb3.remote.EJBRemotingConnectorClientMappingsEntryProviderService | 1 0 % | 32 0 % | 56 0 % |
> | org.jboss.as.ejb3.remote.RegistryInstallerService | 1 0 % | 24 0 % | 48 0 % |
> | org.wildfly.clustering.server.dispatcher.LocalCommandDispatcherFactoryBuilder | 1 0 % | 24 0 % | 48 0 % |
> | org.wildfly.clustering.web.infinispan.session.RouteRegistryEntryProviderBuilder | 1 0 % | 16 0 % | 16 0 % |
> +--------------------------------------------------------------------------------------+-------------+----------------+-----------------+
> {noformat}
> Some of them are probably probably fine, but not all of them.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months