January 2018 - jboss-jira - Jboss List Archives

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

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-8858?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-8858: ------------------------------------ Workaround for applications that don't want to wait for this change, is to set persistence unit hint jboss.as.jpa.classtransformer=true > 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: 12.0.0.Alpha1 > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2244) Use of TP.internal_pool can result in classloader leaks

by Paul Ferraro (JIRA)

Paul Ferraro created JGRP-2244: ---------------------------------- Summary: Use of TP.internal_pool can result in classloader leaks Key: JGRP-2244 URL: https://issues.jboss.org/browse/JGRP-2244 Project: JGroups Issue Type: Bug Affects Versions: 4.0 Reporter: Paul Ferraro Assignee: Bela Ban As of JGroups 4.0, the ThreadFactory of the internal thread pool cannot be overridden. Consequently, there is no mechanism to associate newly spawned threads with a specific classloader. If an application thread results in the spawning of an thread in this internal pool [1], the application class loader can leak to other threads used the the JGroups channel. [1] https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9705) Add session operations and details equivalent to JBossWeb's Manager mbeans

by James Perkins (JIRA)

James Perkins created WFLY-9705: ----------------------------------- Summary: Add session operations and details equivalent to JBossWeb's Manager mbeans Key: WFLY-9705 URL: https://issues.jboss.org/browse/WFLY-9705 Project: WildFly Issue Type: Feature Request Reporter: Aaron Ogburn Assignee: Stuart Douglas JBossWeb's session Manager mbeans provide a lot of details and operations for individual sessions (listing all present ids, their creation/access times, checking particular attributes of specific sessions, etc.). It is desired for equivalent functionality to be added to EAP 7/undertow. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9704) Add session operations and details equivalent to JBossWeb's Manager mbeans

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9704?page=com.atlassian.jira.plugin.... ] David Lloyd deleted WFLY-9704: ------------------------------ > Add session operations and details equivalent to JBossWeb's Manager mbeans > -------------------------------------------------------------------------- > > Key: WFLY-9704 > URL: https://issues.jboss.org/browse/WFLY-9704 > Project: WildFly > Issue Type: Feature Request > Reporter: Aaron Ogburn > Assignee: Stuart Douglas > > JBossWeb's session Manager mbeans provide a lot of details and operations for individual sessions (listing all present ids, their creation/access times, checking particular attributes of specific sessions, etc.). It is desired for equivalent functionality to be added to EAP 7/undertow. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9704) Add session operations and details equivalent to JBossWeb's Manager mbeans

by David Lloyd (JIRA)

David Lloyd created WFLY-9704: --------------------------------- Summary: Add session operations and details equivalent to JBossWeb's Manager mbeans Key: WFLY-9704 URL: https://issues.jboss.org/browse/WFLY-9704 Project: WildFly Issue Type: Feature Request Reporter: Aaron Ogburn Assignee: Stuart Douglas JBossWeb's session Manager mbeans provide a lot of details and operations for individual sessions (listing all present ids, their creation/access times, checking particular attributes of specific sessions, etc.). It is desired for equivalent functionality to be added to EAP 7/undertow. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9703) Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions

by Wolfgang Knauf (JIRA)

[ https://issues.jboss.org/browse/WFLY-9703?page=com.atlassian.jira.plugin.... ] Wolfgang Knauf updated WFLY-9703: --------------------------------- Description: When using this archetype, the "pom.xml" of the root project points to JBoss 8.2.1 / WildFly 9.0.0Alpha1 After changing the versions to WildFly 11, several additional changes are necessary. I suggest to add at least some comments about necessary changes. It would be even better to upgrade the archetype to a more recent WildFly version ;-). In "pom.xml" of the root project: * Dependeny "jboss-javaee-7.0-with-tools" has to be changed to artifactId = "wildfly-javaee7-with-tools". * Dependency "jboss-javaee-7.0-with-hibernate" does not seem to exist any longer So, add a comment to those dependencies about error messages when switching to a new WildFly version and about the necessary changes. This comment should contain the new snippet. In "pom.xml" of the web project: * Dependeny with groupId = "org.jboss.resteasy", artifactId="jaxrs-api" was changed to groupId = "org.jboss.spec.javax.ws.rs", artifactId = "jboss-jaxrs-api_2.0_spec" ([WFLY-4128|https://issues.jboss.org/browse/WFLY-4128]) Additionally, it would be helpful if the web project contains the dependencies with groupId = "org.jboss.spec.javax.ejb" and artifactId = "jboss-ejb-api_3.2_spec" (for use of the "@EJB" annotation in e.g. servlets or JFS components) and groupId = "org.jboss.spec.javax.servlet", artifactId = "jboss-servlet-api_3.1_spec" for being able to code servlets. was: When using this archetype, the "pom.xml" of the root project points to JBoss 8.2.1 / WildFly 9.0.0Alpha1 After changing the versions to WildFly 11, several additional changes are necessary. I suggest to add at least some comments about necessary changes. It would be even better to upgrade the archetype to a more recent WildFly version ;-). In "pom.xml" of the root project: * Dependeny "jboss-javaee-7.0-with-tools" has to be changed to artifactId = "wildfly-javaee7-with-tools". * Dependency "jboss-javaee-7.0-with-hibernate" does not seem to exist any longer So, add a comment to those dependencies about error messages when switching to a new WildFly version and about the necessary changes. This comment should contain the new snippet. In "pom.xml" of the web project: * Dependeny with groupId = "org.jboss.resteasy", artifactId="jaxrs-api" was changed to groupId = "org.jboss.spec.javax.ws.rs", artifactId = "jboss-jaxrs-api_2.0_spec" ([WFLY-4128|https://issues.jboss.org/browse/WFLY-4128] Additionally, it would be helpful if the web project contains the dependencies with groupId = "org.jboss.spec.javax.ejb" and artifactId = "jboss-ejb-api_3.2_spec" (for use of the "@EJB" annotation in e.g. servlets or JFS components) and groupId = "org.jboss.spec.javax.servlet", artifactId = "jboss-servlet-api_3.1_spec" for being able to code servlets. > Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9703 > URL: https://issues.jboss.org/browse/WFLY-9703 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 11.0.0.Final > Reporter: Wolfgang Knauf > Priority: Minor > > When using this archetype, the "pom.xml" of the root project points to JBoss 8.2.1 / WildFly 9.0.0Alpha1 > After changing the versions to WildFly 11, several additional changes are necessary. I suggest to add at least some comments about necessary changes. It would be even better to upgrade the archetype to a more recent WildFly version ;-). > In "pom.xml" of the root project: > * Dependeny "jboss-javaee-7.0-with-tools" has to be changed to artifactId = "wildfly-javaee7-with-tools". > * Dependency "jboss-javaee-7.0-with-hibernate" does not seem to exist any longer > So, add a comment to those dependencies about error messages when switching to a new WildFly version and about the necessary changes. This comment should contain the new snippet. > In "pom.xml" of the web project: > * Dependeny with groupId = "org.jboss.resteasy", artifactId="jaxrs-api" was changed to groupId = "org.jboss.spec.javax.ws.rs", artifactId = "jboss-jaxrs-api_2.0_spec" ([WFLY-4128|https://issues.jboss.org/browse/WFLY-4128]) > Additionally, it would be helpful if the web project contains the dependencies with groupId = "org.jboss.spec.javax.ejb" and artifactId = "jboss-ejb-api_3.2_spec" (for use of the "@EJB" annotation in e.g. servlets or JFS components) and groupId = "org.jboss.spec.javax.servlet", artifactId = "jboss-servlet-api_3.1_spec" for being able to code servlets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9703) Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created WFLY-9703: ------------------------------------ Summary: Improve archetype "wildfly-javaee7-webapp-ear-blank-archetype" to simplify upgrade to recent WildFly versions Key: WFLY-9703 URL: https://issues.jboss.org/browse/WFLY-9703 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 11.0.0.Final Reporter: Wolfgang Knauf Priority: Minor When using this archetype, the "pom.xml" of the root project points to JBoss 8.2.1 / WildFly 9.0.0Alpha1 After changing the versions to WildFly 11, several additional changes are necessary. I suggest to add at least some comments about necessary changes. It would be even better to upgrade the archetype to a more recent WildFly version ;-). In "pom.xml" of the root project: * Dependeny "jboss-javaee-7.0-with-tools" has to be changed to artifactId = "wildfly-javaee7-with-tools". * Dependency "jboss-javaee-7.0-with-hibernate" does not seem to exist any longer So, add a comment to those dependencies about error messages when switching to a new WildFly version and about the necessary changes. This comment should contain the new snippet. In "pom.xml" of the web project: * Dependeny with groupId = "org.jboss.resteasy", artifactId="jaxrs-api" was changed to groupId = "org.jboss.spec.javax.ws.rs", artifactId = "jboss-jaxrs-api_2.0_spec" ([WFLY-4128|https://issues.jboss.org/browse/WFLY-4128] Additionally, it would be helpful if the web project contains the dependencies with groupId = "org.jboss.spec.javax.ejb" and artifactId = "jboss-ejb-api_3.2_spec" (for use of the "@EJB" annotation in e.g. servlets or JFS components) and groupId = "org.jboss.spec.javax.servlet", artifactId = "jboss-servlet-api_3.1_spec" for being able to code servlets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9272) CDI events not clustered

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9272?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-9272: ------------------------------------ Assignee: Radoslav Husar (was: Paul Ferraro) > CDI events not clustered > ------------------------ > > Key: WFLY-9272 > URL: https://issues.jboss.org/browse/WFLY-9272 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, Clustering > Affects Versions: 10.1.0.Final > Reporter: Giovanni Lovato > Assignee: Radoslav Husar > > When an EAR is deployed on a server group in full-ha profile, CDI events ({{javax.enterprise.event.Event}}) fired from a node are notified only to observer threads in the same node. > This limits the use of CDI events in distributed application, when events fired by users balanced on one node are missed by users balanced on other nodes. > In Payara this is already possibile for {{Serializable}} paylaods using annotations (see https://payara.gitbooks.io/payara-server/content/documentation/extended-d...). > It would be really useful to have this in WildFly too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9272) Support clustered CDI events

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9272?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9272: --------------------------------- Summary: Support clustered CDI events (was: CDI events not clustered) > Support clustered CDI events > ---------------------------- > > Key: WFLY-9272 > URL: https://issues.jboss.org/browse/WFLY-9272 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, Clustering > Affects Versions: 10.1.0.Final > Reporter: Giovanni Lovato > Assignee: Radoslav Husar > > When an EAR is deployed on a server group in full-ha profile, CDI events ({{javax.enterprise.event.Event}}) fired from a node are notified only to observer threads in the same node. > This limits the use of CDI events in distributed application, when events fired by users balanced on one node are missed by users balanced on other nodes. > In Payara this is already possibile for {{Serializable}} paylaods using annotations (see https://payara.gitbooks.io/payara-server/content/documentation/extended-d...). > It would be really useful to have this in WildFly too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9272) CDI events not clustered

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9272?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-9272: -------------------------------------- [~kobogianhitis] I can confirm they are not clustered. > CDI events not clustered > ------------------------ > > Key: WFLY-9272 > URL: https://issues.jboss.org/browse/WFLY-9272 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, Clustering > Affects Versions: 10.1.0.Final > Reporter: Giovanni Lovato > > When an EAR is deployed on a server group in full-ha profile, CDI events ({{javax.enterprise.event.Event}}) fired from a node are notified only to observer threads in the same node. > This limits the use of CDI events in distributed application, when events fired by users balanced on one node are missed by users balanced on other nodes. > In Payara this is already possibile for {{Serializable}} paylaods using annotations (see https://payara.gitbooks.io/payara-server/content/documentation/extended-d...). > It would be really useful to have this in WildFly too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018