February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7116) High CPU usage during high concurrency of distributed @Stateful EJB creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7116?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7116: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > High CPU usage during high concurrency of distributed @Stateful EJB creation > ---------------------------------------------------------------------------- > > Key: WFLY-7116 > URL: https://issues.jboss.org/browse/WFLY-7116 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7115) High CPU usage during high concurrency of distributed web session creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7115?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7115: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > High CPU usage during high concurrency of distributed web session creation > -------------------------------------------------------------------------- > > Key: WFLY-7115 > URL: https://issues.jboss.org/browse/WFLY-7115 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7100) Add JGroups-based SingletonServiceBuilderFactory implementation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7100?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7100: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Add JGroups-based SingletonServiceBuilderFactory implementation > --------------------------------------------------------------- > > Key: WFLY-7100 > URL: https://issues.jboss.org/browse/WFLY-7100 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > The singleton subsystem currently requires the Infinispan subsystem. To minimize the requirements for using the singleton subsystem within the context of the host-controller, we should reimplement singleton service using JGroups directly, instead of requiring an Infinispan cache. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6958) Use more intuitive values for consistent-hash-strategy

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6958?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6958: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Use more intuitive values for consistent-hash-strategy > ------------------------------------------------------ > > Key: WFLY-6958 > URL: https://issues.jboss.org/browse/WFLY-6958 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Final > > > Currently consistent-hash-strategy can have on of 2 values: INTRA_CACHE vs INTER_CACHE. > This was initially meant to describe a consistent hash that would be consistent within a cache vs across multiple caches within a cache container. In retrospect, these value are not very descriptive. > Better would be consistent-hash-strategy="AGE|ADDRESS" or "AGE|NAME", where the strategy uses the cache view sorted by either age, or name/address. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6779) Add WISE for Web console access

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6779?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6779: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Add WISE for Web console access > ------------------------------- > > Key: WFLY-6779 > URL: https://issues.jboss.org/browse/WFLY-6779 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: R Searls > Assignee: R Searls > Priority: Minor > Fix For: 12.0.0.Final > > > Wise is a Java framework for easily invoking webservices, which can be used as base for zero-code webservice invocation applications. (see http://wise.jboss.org/) > Based upon Brian Stansberry's advise WISE is added to wfly using the "Mixed-Approach" > for adding a feature. > Once this is available in wfly. HAL can provide a link to it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8449: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: downstream_dependency, ejb > Fix For: 12.0.0.Final > > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8390) Correct RemotingLoginModule test failures.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8390?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8390: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Correct RemotingLoginModule test failures. > ------------------------------------------ > > Key: WFLY-8390 > URL: https://issues.jboss.org/browse/WFLY-8390 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 12.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7822) The default-security-domain attribute in the Undertow subsystem should not support expressions.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7822?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7822: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > The default-security-domain attribute in the Undertow subsystem should not support expressions. > ----------------------------------------------------------------------------------------------- > > Key: WFLY-7822 > URL: https://issues.jboss.org/browse/WFLY-7822 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Stuart Douglas > Fix For: 12.0.0.Final > > > This attribute may be deprecated and removed at some point when we start to transition off PicketBox but for now it leads to a service dependency being set based on the value so should not support expressions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7795) org.jboss.sasl classes still making it into jboss-client.jar

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7795?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7795: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > org.jboss.sasl classes still making it into jboss-client.jar > ------------------------------------------------------------ > > Key: WFLY-7795 > URL: https://issues.jboss.org/browse/WFLY-7795 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 12.0.0.Final > > > The dependencies should have been removed but maybe this is still coming in as a transitive dependency from elsewhere. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7537) Review NamingContext.check() method

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7537?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7537: ------------------------------- Fix Version/s: 12.0.0.Final (was: 12.0.0.CR1) > Review NamingContext.check() method > ----------------------------------- > > Key: WFLY-7537 > URL: https://issues.jboss.org/browse/WFLY-7537 > Project: WildFly > Issue Type: Task > Components: Naming > Reporter: Darran Lofthouse > Assignee: Farah Juma > Fix For: 12.0.0.Final > > > The new naming client is sending in a SimpleName where the lookup was performed using a String. > When a SecurityManager is installed the check() method of NamingContext is called and results in the following error: - > {noformat} > javax.naming.InvalidNameException: Not a composite name: jms > at javax.naming.CompositeName.addAll(CompositeName.java:472) > at org.jboss.as.naming.NamingContext.check(NamingContext.java:592) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) > at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) > at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > A fix has been applied to convert the incoming name to a CompositeName but as we deliberately have a SimpleName to avoid CompositeName I wonder if that is completely correct. > Some other options I think of: - > 1. Stick with current fix. > 2 The client should convert to CompositeName before sending. > 3. Manually iterate the segments if not a CompositeName > 4. Check if the NamingStore really needs to use a CompositeName -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018