[JBoss JIRA] (ELY-724) Add support for matching by abstract type
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-724?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-724:
----------------------------
Description: Match by abstract type, which is a logical supplement to a URI that indicates the encompassingx service type (for example, ejb, jmx, jndi,
> Add support for matching by abstract type
> -----------------------------------------
>
> Key: ELY-724
> URL: https://issues.jboss.org/browse/ELY-724
> Project: WildFly Elytron
> Issue Type: Task
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.Beta13
>
>
> Match by abstract type, which is a logical supplement to a URI that indicates the encompassingx service type (for example, ejb, jmx, jndi,
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7462) Do not log common CLI failures for Elytron to server log
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7462?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-7462:
----------------------------------------
For this one - yes I think we should be able to detect the path not being set at stage Model.
Some of the other ones however such as modules not being found or classes not being found will only be detected at stage Runtime.
> Do not log common CLI failures for Elytron to server log
> --------------------------------------------------------
>
> Key: WFLY-7462
> URL: https://issues.jboss.org/browse/WFLY-7462
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: user_experience
>
> Almost every common CLI command failure from Elytron subsystem is logged as ERROR to server log. For example this means:
> * trying to add duplicate service -> ERROR in server log
> * missing required attribute of any resource attribute in CLI command -> ERROR in server log
> * missing capability -> ERROR in server log
> * ...
> Some reasons why these logs should not be logged to server log:
> * Adding useless messages to server log.
> * This is inconsistent with other subsystems (e.g. PicketBox). It can be confusing.
> These common CLI command failures should be removed from the log, or logged on low level (i.e. DEBUG)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (JGRP-2125) Bits: reading ints and longs is allocating unnecessary memory
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2125?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2125.
----------------------------
Resolution: Done
> Bits: reading ints and longs is allocating unnecessary memory
> -------------------------------------------------------------
>
> Key: JGRP-2125
> URL: https://issues.jboss.org/browse/JGRP-2125
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 4.0
>
>
> Some readXXX() methods in Bits such as readLong(), readInt(), readLongSequence(), readLongCompressed() etc read the length byte first, then create a byte[] array based on it, read the required bytes into that array and finally call makeInt()/makeLong() etc.
> The creation of the temp byte[] array is unnecessary and leads to unneeded memory allocation, especially as quite a number of frequently used headers (e.g. NakAckHeader2, UnicastHeader3 etc) do this.
> SOLUTION: read the required bytes directly from the input (e.g. java.nio.ByteBuffer or DataInput) and apply them to the result one-by-one, then return the result.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7462) Do not log common CLI failures for Elytron to server log
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7462?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-7462:
----------------------------------------
Thanks [~dlofthouse]. Perhaps that and the other issues Ondrej reports have the same underlying cause. It smells like Stage.MODEL checks are not occurring, so then things fail in Stage.RUNTIME. For example, this should only be logged in the server.log if it is caught in Stage.RUNTIME:
{code}
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("properties-realm" => "realm")
]) - failure description: "WFLYCTL0155: path may not be null"
{code}
The fact it's logged tells me it wasn't caught in MODEL like it should have been. A capability conflict should also be caught in MODEL.
I looked at the code for the property-realm add though yesterday and didn't see anything that would have caused that.
> Do not log common CLI failures for Elytron to server log
> --------------------------------------------------------
>
> Key: WFLY-7462
> URL: https://issues.jboss.org/browse/WFLY-7462
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: user_experience
>
> Almost every common CLI command failure from Elytron subsystem is logged as ERROR to server log. For example this means:
> * trying to add duplicate service -> ERROR in server log
> * missing required attribute of any resource attribute in CLI command -> ERROR in server log
> * missing capability -> ERROR in server log
> * ...
> Some reasons why these logs should not be logged to server log:
> * Adding useless messages to server log.
> * This is inconsistent with other subsystems (e.g. PicketBox). It can be confusing.
> These common CLI command failures should be removed from the log, or logged on low level (i.e. DEBUG)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1939) Tabulator in CLI could suggest actual values for attributes for operations
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1939?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1939:
------------------------------------------
This is a request for a general facility so it goes in core. It requires the ability to associate with the definition of a parameter information about what resources in the model can satisfy that value. We have this for capability reference attributes but this is something else.
This is unlikely to happen any time soon
> Tabulator in CLI could suggest actual values for attributes for operations
> --------------------------------------------------------------------------
>
> Key: WFCORE-1939
> URL: https://issues.jboss.org/browse/WFCORE-1939
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Domain Management
> Reporter: Miroslav Novak
> Labels: user_experience
>
> There are number of cases where is necessary to execute CLI operation to actually get value for attribute to another CLI operation. For example I want to list all messages for subscription on the topic then it's necessary to get names of all subscriptions by:
> {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-all-subscriptions
> {
> "outcome" => "success",
> "result" => [
> {
> "durable" => true,
> "queueName" => "172\\.16\\.10\\.15_VM1_SPAgent55_0.SP_CallForOffersEH_55_EHID_1PF4",
> "clientID" => "172.16.10.15_VM1_SPAgent55_0",
> "messageCount" => 0,
> "deliveringCount" => 0,
> "name" => "SP_CallForOffersEH_55_EHID_1PF4",
> "consumers" => [{
> "creationTime" => 1478261489444L,
> "consumerID" => 4,
> "browseOnly" => false,
> "connectionID" => "-1638816479",
> "sessionID" => "d1149360-a287-11e6-bb34-97e27f67b29e"
> }]
> },
> {
> "durable" => true,
> "queueName" => "172\\.16\\.10\\.18_VM1_SPAgent23_0.SP_CallForOffersEH_23_EHID_1PF0",
> "clientID" => "172.16.10.18_VM1_SPAgent23_0",
> "messageCount" => 0,
> "deliveringCount" => 0,
> "name" => "SP_CallForOffersEH_23_EHID_1PF0",
> "consumers" => [{
> "creationTime" => 1478261516648L,
> "consumerID" => 0,
> "browseOnly" => false,
> "connectionID" => "-1794279882",
> "sessionID" => "e14e5343-a287-11e6-9311-4d8e66b2ef14"
> }]
> }
> ]
> }
> {code}
>
> so name of subscription {{SP_CallForOffersEH_55_EHID_1PF4}} could be used in: {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=SP_CallForOffersEH_55_EHID_1PF4){code}
> The improvement would allow to just press tab in: {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=... <-- tab here would suggest which queues are available {code}
> and it would suggest queue names of available subscriptions.
> There are more places like this - for example :
> {code}
> /subsystem=messaging-activemq/server=default:rollback-prepared-transaction(transaction-as-base-64=... <-- tab here
> {code}
> would provide available prepared transactions which can be commit.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1939) Tabulator in CLI could suggest actual values for attributes for operations
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1939?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFLY-7484 to WFCORE-1939:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1939 (was: WFLY-7484)
Component/s: CLI
Domain Management
(was: CLI)
(was: Domain Management)
Affects Version/s: (was: 10.1.0.Final)
> Tabulator in CLI could suggest actual values for attributes for operations
> --------------------------------------------------------------------------
>
> Key: WFCORE-1939
> URL: https://issues.jboss.org/browse/WFCORE-1939
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI, Domain Management
> Reporter: Miroslav Novak
> Labels: user_experience
>
> There are number of cases where is necessary to execute CLI operation to actually get value for attribute to another CLI operation. For example I want to list all messages for subscription on the topic then it's necessary to get names of all subscriptions by:
> {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-all-subscriptions
> {
> "outcome" => "success",
> "result" => [
> {
> "durable" => true,
> "queueName" => "172\\.16\\.10\\.15_VM1_SPAgent55_0.SP_CallForOffersEH_55_EHID_1PF4",
> "clientID" => "172.16.10.15_VM1_SPAgent55_0",
> "messageCount" => 0,
> "deliveringCount" => 0,
> "name" => "SP_CallForOffersEH_55_EHID_1PF4",
> "consumers" => [{
> "creationTime" => 1478261489444L,
> "consumerID" => 4,
> "browseOnly" => false,
> "connectionID" => "-1638816479",
> "sessionID" => "d1149360-a287-11e6-bb34-97e27f67b29e"
> }]
> },
> {
> "durable" => true,
> "queueName" => "172\\.16\\.10\\.18_VM1_SPAgent23_0.SP_CallForOffersEH_23_EHID_1PF0",
> "clientID" => "172.16.10.18_VM1_SPAgent23_0",
> "messageCount" => 0,
> "deliveringCount" => 0,
> "name" => "SP_CallForOffersEH_23_EHID_1PF0",
> "consumers" => [{
> "creationTime" => 1478261516648L,
> "consumerID" => 0,
> "browseOnly" => false,
> "connectionID" => "-1794279882",
> "sessionID" => "e14e5343-a287-11e6-9311-4d8e66b2ef14"
> }]
> }
> ]
> }
> {code}
>
> so name of subscription {{SP_CallForOffersEH_55_EHID_1PF4}} could be used in: {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=SP_CallForOffersEH_55_EHID_1PF4){code}
> The improvement would allow to just press tab in: {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=... <-- tab here would suggest which queues are available {code}
> and it would suggest queue names of available subscriptions.
> There are more places like this - for example :
> {code}
> /subsystem=messaging-activemq/server=default:rollback-prepared-transaction(transaction-as-base-64=... <-- tab here
> {code}
> would provide available prepared transactions which can be commit.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7484) Tabulator in CLI could suggest actual values for attributes for operations
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7484?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-7484:
--------------------------------------
Component/s: Domain Management
(was: JMS)
(was: Server)
Assignee: (was: Jeff Mesnil)
> Tabulator in CLI could suggest actual values for attributes for operations
> --------------------------------------------------------------------------
>
> Key: WFLY-7484
> URL: https://issues.jboss.org/browse/WFLY-7484
> Project: WildFly
> Issue Type: Feature Request
> Components: CLI, Domain Management
> Affects Versions: 10.1.0.Final
> Reporter: Miroslav Novak
> Labels: user_experience
>
> There are number of cases where is necessary to execute CLI operation to actually get value for attribute to another CLI operation. For example I want to list all messages for subscription on the topic then it's necessary to get names of all subscriptions by:
> {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-all-subscriptions
> {
> "outcome" => "success",
> "result" => [
> {
> "durable" => true,
> "queueName" => "172\\.16\\.10\\.15_VM1_SPAgent55_0.SP_CallForOffersEH_55_EHID_1PF4",
> "clientID" => "172.16.10.15_VM1_SPAgent55_0",
> "messageCount" => 0,
> "deliveringCount" => 0,
> "name" => "SP_CallForOffersEH_55_EHID_1PF4",
> "consumers" => [{
> "creationTime" => 1478261489444L,
> "consumerID" => 4,
> "browseOnly" => false,
> "connectionID" => "-1638816479",
> "sessionID" => "d1149360-a287-11e6-bb34-97e27f67b29e"
> }]
> },
> {
> "durable" => true,
> "queueName" => "172\\.16\\.10\\.18_VM1_SPAgent23_0.SP_CallForOffersEH_23_EHID_1PF0",
> "clientID" => "172.16.10.18_VM1_SPAgent23_0",
> "messageCount" => 0,
> "deliveringCount" => 0,
> "name" => "SP_CallForOffersEH_23_EHID_1PF0",
> "consumers" => [{
> "creationTime" => 1478261516648L,
> "consumerID" => 0,
> "browseOnly" => false,
> "connectionID" => "-1794279882",
> "sessionID" => "e14e5343-a287-11e6-9311-4d8e66b2ef14"
> }]
> }
> ]
> }
> {code}
>
> so name of subscription {{SP_CallForOffersEH_55_EHID_1PF4}} could be used in: {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=SP_CallForOffersEH_55_EHID_1PF4){code}
> The improvement would allow to just press tab in: {code}
> [standalone@172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=... <-- tab here would suggest which queues are available {code}
> and it would suggest queue names of available subscriptions.
> There are more places like this - for example :
> {code}
> /subsystem=messaging-activemq/server=default:rollback-prepared-transaction(transaction-as-base-64=... <-- tab here
> {code}
> would provide available prepared transactions which can be commit.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1936) Value of parameters "restart-required" for fixed-*port attributes does not match reality for socket-binding and *-destination-outbound-socket-binding in CLI
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1936?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1936:
-------------------------------------
Component/s: Domain Management
(was: Server)
> Value of parameters "restart-required" for fixed-*port attributes does not match reality for socket-binding and *-destination-outbound-socket-binding in CLI
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1936
> URL: https://issues.jboss.org/browse/WFCORE-1936
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha11
> Reporter: Ondrej Kotek
> Assignee: Chao Wang
> Labels: user_experience
>
> {{fixed-port}} attribute of {{socket-binding}} and {{fixed-source-port}} attributes of {{*-destination-outbound-socket-binding}} define in its description that there is not necessary to do {{reload}} or {{restart}} for any of them. But reality is different. If you tries to change such attributes you are informed that {{reload}} is necessary.
> The attributes are defined as {{"restart-required" => "no-services"}}, see {{/socket-binding-group=standard-sockets:read-resource-description(recursive=true)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months