May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1523) Removing of non-existent resource finishes with outcome success

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1523?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Śmietanko updated WFCORE-1523: --------------------------------------------- Summary: Removing of non-existent resource finishes with outcome success (was: Removing of non-existent policy-module finishes with outcome success) > Removing of non-existent resource finishes with outcome success > --------------------------------------------------------------- > > Key: WFCORE-1523 > URL: https://issues.jboss.org/browse/WFCORE-1523 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.1.0.Final > Reporter: Ondrej Lukas > Assignee: Bartosz Spyrko-Śmietanko > Priority: Minor > Labels: 2.2 > Fix For: 3.0.0.Alpha1 > > > In case when non-existent policy-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1530) It should be possible to provide a 'per-cpu' value when configuring the task-max-threads attribute of a worker

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1530?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1530: ------------------------------------- [~jamat] David is referring to old threads subsystem which we deprecated and somewhat replaced with IO subsystem but not as direct replacement. https://github.com/wildfly/wildfly/blob/8.x/build/src/main/resources/docs... > It should be possible to provide a 'per-cpu' value when configuring the task-max-threads attribute of a worker > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1530 > URL: https://issues.jboss.org/browse/WFCORE-1530 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 2.1.0.Final > Reporter: Juan AMAT > Assignee: Tomaz Cerar > > We have an application running under JBoss EAP 6.4 and we are in the process to make it also run under Wildfly. > While doing performance testing we noticed that the number of threads that can process the incoming http requests was way lower in Wildfly. > Indeed we were using the 'default' worker and by default the max threads is set to 16 times the cpu count. In Jboss EAP the default configuration is 512 times the cpu count. > We were hitting this max and we did increase it. But then we had to provide an absolute value (and we would need to provide different values per type of servers). > It will be nicer to be able to configure instead a per-cpu value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1538) resource-added notifications contain no data

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1538?page=com.atlassian.jira.plugi... ] Kabir Khan closed WFCORE-1538. ------------------------------ Resolution: Won't Fix Closing as per Brian's comment. I wasn't clear if this was something we wanted to implement or not, but now it has been discussed and recorded. > resource-added notifications contain no data > -------------------------------------------- > > Key: WFCORE-1538 > URL: https://issues.jboss.org/browse/WFCORE-1538 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Kabir Khan > Assignee: Brian Stansberry > > When listening for notifications, I found that the attribute-value-written notifications contain a data field containing the name of the modified attribute and the old and new values. > For resource-added (and presumably resource-removed) the data field is empty, so if someone has registered a notification handler for resource adds, and they want the values of the resource attributes they will have to do a read-resource on the newly created resource. > Should the data for a resource add contain the attribute values? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1538) resource-added notifications contain no data

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1538?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1538: ------------------------------------------ I'm fine with not providing this data. It's not at all trivial to provide it reliably as the kernel can't just get the Resource and call getModel() on it. There is no requirement that such a call produce the value for all attributes. The handling for read-resource illustrates what all has to be done to correctly provide all the values. Basically you have to add read-attribute steps for each attribute. > resource-added notifications contain no data > -------------------------------------------- > > Key: WFCORE-1538 > URL: https://issues.jboss.org/browse/WFCORE-1538 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Kabir Khan > Assignee: Brian Stansberry > > When listening for notifications, I found that the attribute-value-written notifications contain a data field containing the name of the modified attribute and the old and new values. > For resource-added (and presumably resource-removed) the data field is empty, so if someone has registered a notification handler for resource adds, and they want the values of the resource attributes they will have to do a read-resource on the newly created resource. > Should the data for a resource add contain the attribute values? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1538) resource-added notifications contain no data

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1538?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1538: ------------------------------------- Fix Version/s: (was: 3.0.0.Alpha1) > resource-added notifications contain no data > -------------------------------------------- > > Key: WFCORE-1538 > URL: https://issues.jboss.org/browse/WFCORE-1538 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Kabir Khan > Assignee: Brian Stansberry > > When listening for notifications, I found that the attribute-value-written notifications contain a data field containing the name of the modified attribute and the old and new values. > For resource-added (and presumably resource-removed) the data field is empty, so if someone has registered a notification handler for resource adds, and they want the values of the resource attributes they will have to do a read-resource on the newly created resource. > Should the data for a resource add contain the attribute values? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-494) DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-494?page=com.atlassian.jira.plugin.sy... ] Farah Juma reassigned ELY-494: ------------------------------ Assignee: Farah Juma > DigestServerFactory should only use AvailableRealmsCallback to get realms, not the legacy property list > ------------------------------------------------------------------------------------------------------- > > Key: ELY-494 > URL: https://issues.jboss.org/browse/ELY-494 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: David Lloyd > Assignee: Farah Juma > > We use a different delimiter for the {{com.sun.security.sasl.digest.realm}} property than the JDK, which uses commas, spaces, newlines, or tab characters. This makes it impossible to correctly emulate the property to the mechanism while using the callback to acquire the actual list. Since code changes would likely be required to use the new version with only a comma delimiter, it does not serve any compatibility purpose to continue to support this property. > Instead we should do three things: > * Eliminate property support from our DigestSaslServer > * Add a wrapping SaslServerFactory which detects when a mechanism is trying to acquire a realm list by reading the {{com.sun.security.sasl.digest.realm}} property, and uses the AvailableRealmsCallback to populate it -(with a flag to support transformation of spaces, tabs, and newlines to NBSP (0xA0), and remove commas)- > * Add a wrapping SaslServerFactory which allows legacy users to specify a value for {{com.sun.security.sasl.digest.realm}}, and uses it to support AvailableRealmsCallback if that property was set, with programmable delimiters -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6598) Upgrade HAL to 2.8.25.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-6598: --------------------------------- Summary: Upgrade HAL to 2.8.25.Final Key: WFLY-6598 URL: https://issues.jboss.org/browse/WFLY-6598 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Priority: Blocker Fix For: 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6598) Upgrade HAL to 2.8.25.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-6598?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-6598: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/8764) > Upgrade HAL to 2.8.25.Final > --------------------------- > > Key: WFLY-6598 > URL: https://issues.jboss.org/browse/WFLY-6598 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Blocker > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2127) Transaction Timeout doesn't seem to work in AS 6 M3 (using the EJB 3 Annotation)

by Peter Saly (JIRA)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1538) resource-added notifications contain no data

by Kabir Khan (JIRA)

Kabir Khan created WFCORE-1538: ---------------------------------- Summary: resource-added notifications contain no data Key: WFCORE-1538 URL: https://issues.jboss.org/browse/WFCORE-1538 Project: WildFly Core Issue Type: Feature Request Components: Domain Management Affects Versions: 2.1.0.Final Reporter: Kabir Khan Assignee: Brian Stansberry Fix For: 3.0.0.Alpha1 When listening for notifications, I found that the attribute-value-written notifications contain a data field containing the name of the modified attribute and the old and new values. For resource-added (and presumably resource-removed) the data field is empty, so if someone has registered a notification handler for resource adds, and they want the values of the resource attributes they will have to do a read-resource on the newly created resource. Should the data for a resource add contain the attribute values? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016