[JBoss JIRA] (WFLY-9584) Adding protocol with override definition to fork results in IllegalStateException
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-9584:
----------------------------------
Summary: Adding protocol with override definition to fork results in IllegalStateException
Key: WFLY-9584
URL: https://issues.jboss.org/browse/WFLY-9584
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Paul Ferraro
Assignee: Paul Ferraro
{noformat}
[standalone@embedded /] /subsystem=jgroups/channel=ee/fork=foo/protocol=MPING:add(socket-binding=http)
14:46:40,228 ERROR [org.jboss.as.controller.management-operation] (pool-4-thread-1) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "jgroups"),
("channel" => "ee"),
("fork" => "foo"),
("protocol" => "MPING")
]): java.lang.IllegalStateException: WFLYCTL0221: An override model registration is not allowed for non-wildcard model registrations. This registration is for the non-wildcard name 'MPING'.
at org.jboss.as.controller.registry.AbstractResourceRegistration.registerOverrideModel(AbstractResourceRegistration.java:122)
at org.jboss.as.clustering.jgroups.subsystem.ForkProtocolRuntimeResourceRegistration.register(ForkProtocolRuntimeResourceRegistration.java:127)
at org.jboss.as.clustering.controller.AddStepHandler.lambda$null$2(AddStepHandler.java:117)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
at org.jboss.as.controller.ModelControllerClientFactoryImpl$LocalClient$1$1.lambda$run$0(ModelControllerClientFactoryImpl.java:170)
at org.jboss.as.controller.access.InVmAccess.runInVm(InVmAccess.java:63)
at org.jboss.as.controller.SecurityActions$InVmActions$1.runInVm(SecurityActions.java:149)
at org.jboss.as.controller.SecurityActions.runInVm(SecurityActions.java:49)
at org.jboss.as.controller.ModelControllerClientFactoryImpl$LocalClient$1$1.run(ModelControllerClientFactoryImpl.java:170)
at org.jboss.as.controller.ModelControllerClientFactoryImpl$LocalClient$1$1.run(ModelControllerClientFactoryImpl.java:163)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:198)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:175)
at org.jboss.as.controller.ModelControllerClientFactoryImpl$LocalClient$1.run(ModelControllerClientFactoryImpl.java:163)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalStateException: WFLYCTL0221: An override model registration is not allowed for non-wildcard model registrations. This registration is for the non-wildcard name 'MPING'.",
"rolled-back" => true
}
{noformat}
Normally, protocols register a runtime resource that exposes its properties as runtime attribute to the management model. This is implemented by registering an override model at runtime. However, if the protocol already uses an override model, the registration will fail.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFCORE-3438) trailing whitespace are not removed from input string
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3438:
--------------------------------------------
Summary: trailing whitespace are not removed from input string
Key: WFCORE-3438
URL: https://issues.jboss.org/browse/WFCORE-3438
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
The string received by aesh used to be trimmed prior to be passed down to the CommandContext, that has been forgotten when re-implementing the console with aesh-readline.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFCORE-3415) Cut the time to execute MBeanServerConnection.getMBeanCount()
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3415?page=com.atlassian.jira.plugi... ]
Brian Stansberry reopened WFCORE-3415:
--------------------------------------
Reopening as this fix resulted in a TCK problem.
> Cut the time to execute MBeanServerConnection.getMBeanCount()
> -------------------------------------------------------------
>
> Key: WFCORE-3415
> URL: https://issues.jboss.org/browse/WFCORE-3415
> Project: WildFly Core
> Issue Type: Enhancement
> Components: JMX
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 4.0.0.Alpha3
>
>
> The time it takes to count the mbeans associated with the jboss.as and jboss.as.expr domains is way too high, over a full second when the WildFly full standalone-full-ha.xml config is used, and potentially much higher if complex deployments are installed. See WFLY-9408.
> This enhancement proposes doing two things to mitigate this:
> 1) There is no point doing a full count of both jboss.as and jboss.as.expr as they are just 2 views on the same underlying resources. If both are present, count one and double it.
> 2) Do not use RBAC to exclude from the count mbeans the user won't be allowed to see. They exist whether the user can see them or not. Simply count the resources.
> Looking at the JMX specification (https://docs.oracle.com/javase/8/docs/technotes/guides/jmx/JMX_1_4_specif...) I see nothing directly on the topic of the effect of any security checks on the result of getMBeanCount(). Section 12.1.2.4 "Permission Checking for Queries" clearly states that permission checks should remove mbeans that should not be visible according to the permission scheme from the query result, so definitely queries returning a subset of the entire mbean universe is contemplated. Now, that section is about security manager permissions, not our RBAC scheme, but it's the most on topic thing I see.
> Doing these two things I can get the cost of a getMBeanCount() from around 1 second to under 10 ms. (Note the 1 sec figure is the first call; once the JVM optimizes the existing code it drops to under 500ms.)
> The enhancement will also make it possible for custom Resource implementations to optimize things. For example a resource that represents a possibly large number of dynamic children could ask the system behind those children for a child count, rather that iterating over the children.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFCORE-3437) CLI can't be started on Solaris
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3437?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3437:
-------------------------------------
Priority: Blocker (was: Critical)
> CLI can't be started on Solaris
> -------------------------------
>
> Key: WFCORE-3437
> URL: https://issues.jboss.org/browse/WFCORE-3437
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
> Priority: Blocker
>
> CLI (WildFly master) can't be started on Solaris:
> {noformat}
> [hudson@dev34-02 bin]$ ./jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> java.io.IOException: Error executing 'stty size': unknown mode: size
> : Error executing 'stty size': unknown mode: size
> [hudson@dev34-02 bin]$
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month