November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2590) Zero Timeout Stateful EJB Leak

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2590?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-2590: ---------------------------------- Issue Type: Bug (was: Feature Request) > Zero Timeout Stateful EJB Leak > ------------------------------ > > Key: WFLY-2590 > URL: https://issues.jboss.org/browse/WFLY-2590 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Stateful EJB instances are not removed from cache upon release, if the timeout is zero. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2590) Zero Timeout Stateful EJB Leak

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-2590: ------------------------------------- Summary: Zero Timeout Stateful EJB Leak Key: WFLY-2590 URL: https://issues.jboss.org/browse/WFLY-2590 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB Reporter: Eduardo Martins Assignee: Eduardo Martins Stateful EJB instances are not removed from cache upon release, if the timeout is zero. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Jeff Mesnil edited comment on WFLY-2589 at 11/29/13 2:35 AM: ------------------------------------------------------------- I remember mentioning that when I refactored the messaging subsystem transformers. The new attributes that I added were reaching the legacy version with the default value set. At first, I thought about setting include-defaults to false when :read-resource is called by ReadTransformedResourceOperation but changed my mind on further notice. The resources are resolving every attributes and uses the default value if they are not set. If we do not include the default values when transforming the resources, we let the legacy versions resolve the attribute based on its own default value, not the one from the current version. That could lead to issues if such a value change between versions. I preferred to handle that explicitly when transforming the resources. For example, for new attributes, I discard them if they are undefined or set to the default value and reject them if they have any other value. was (Author: jmesnil): I remember mentioning that when I refactored the messaging subsystem transformers. The new attributes that I added were reaching the legacy version with the default value set. At first, I thought about setting include-defaults to false when :read-resource is called by ReadTransformedResourceOperation but changed my mind on further notice. The resources are resolving every attributes and uses the default value if they are not set. If we do not include the default values when transforming the resources, we let the legacy versions resolve the attribute based on its own default value, not the one from the current version. That could lead to issues if such a value change between versions. I preferred to handle tha > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-2589: ----------------------------------- I remember mentioning that when I refactored the messaging subsystem transformers. The new attributes that I added were reaching the legacy version with the default value set. At first, I thought about setting include-defaults to false when :read-resource is called by ReadTransformedResourceOperation but changed my mind on further notice. The resources are resolving every attributes and uses the default value if they are not set. If we do not include the default values when transforming the resources, we let the legacy versions resolve the attribute based on its own default value, not the one from the current version. That could lead to issues if such a value change between versions. I preferred to handle tha > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2571) Make wildfly-mod_cluster-undertow module a separate subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2571?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-2571: -------------------------------------- Closed https://github.com/wildfly/wildfly/pull/5164 to take this approach instead. > Make wildfly-mod_cluster-undertow module a separate subsystem > ------------------------------------------------------------- > > Key: WFLY-2571 > URL: https://issues.jboss.org/browse/WFLY-2571 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2579) Aesh has problems on JDK8

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-2579?page=com.atlassian.jira.plugin.... ] Ståle Pedersen commented on WFLY-2579: -------------------------------------- hi, sorry for the delay. ive pushed version 0.33.11 which should work with jdk8 > Aesh has problems on JDK8 > ------------------------- > > Key: WFLY-2579 > URL: https://issues.jboss.org/browse/WFLY-2579 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI > Reporter: Tomaz Cerar > Assignee: Ståle Pedersen > Fix For: 8.0.0.CR1 > > > Fix is already available in snapshot but it requires relase. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1085) No audit feature for security-realm

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1085?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1085: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 912233|https://bugzilla.redhat.com/show_bug.cgi?id=912233] from NEW to ON_QA > No audit feature for security-realm > ----------------------------------- > > Key: WFLY-1085 > URL: https://issues.jboss.org/browse/WFLY-1085 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Logging > Environment: EAP 6.0.x > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > There is no auditing feature for security-realm. Need the feature like audit provider for security-domain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SECURITY-750) Database*LoginModules should use the transactionManagerJndiName module option

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-750?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-750: -------------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 901477|https://bugzilla.redhat.com/show_bug.cgi?id=901477] from POST to VERIFIED > Database*LoginModules should use the transactionManagerJndiName module option > ----------------------------------------------------------------------------- > > Key: SECURITY-750 > URL: https://issues.jboss.org/browse/SECURITY-750 > Project: PicketBox > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: PicketBox > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > Fix For: PicketBox_4_0_19.Final > > > The DatabaseCertLoginModule and DatabaseServerLoginModule use for role search a routine from a class org.jboss.security.auth.spi.DbUtil. But there is a hardcoded reference to JNDI name for Transaction Manager lookup "java:/TransactionManager" - which is not valid in the EAP 6. The JNDI name should be provided as a parameter. > The login module option "transactionManagerJndiName" is already implemented in the DatabaseServerLoginModule, but it should be also added to the DatabaseCertLoginModule. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2589: ----------------------------- Description: This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing was:This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2589: ----------------------------- Issue Type: Bug (was: Feature Request) Affects Version/s: 8.0.0.Beta1 Component/s: Domain Management > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming things that should be undefined get passed through with the default value instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013