March 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: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

8 years, 2 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: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

8 years, 2 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: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

8 years, 2 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: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7419) Include RESTEasy WADL module

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7419?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7419: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Include RESTEasy WADL module > ---------------------------- > > Key: WFLY-7419 > URL: https://issues.jboss.org/browse/WFLY-7419 > Project: WildFly > Issue Type: Enhancement > Components: REST > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: Frank Langelage > Assignee: Alessio Soldano > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8954: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > Fix For: 13.0.0.Beta1 > > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8858) Remove JPA container check for deprecated hibernate.ejb.use_class_enhancer

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8858?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8858: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Remove JPA container check for deprecated hibernate.ejb.use_class_enhancer > -------------------------------------------------------------------------- > > Key: WFLY-8858 > URL: https://issues.jboss.org/browse/WFLY-8858 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 13.0.0.Beta1 > > > Applications can instead use the jboss.as.jpa.classtransformer property to control whether the application can use entity class rewriting. Starting with Hibernate ORM 5.0+, Hibernate defaults to always rewrite entity classes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 March 2018