February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9552) Enable JBTM-2955

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/WFLY-9552?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on WFLY-9552: --------------------------------------- [~tomjenkinson] I'm not sure (I could be missing something) but isn't this duplicate of https://issues.jboss.org/browse/WFLY-9670, isn't the orphan filter already configured https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... ? > Enable JBTM-2955 > ---------------- > > Key: WFLY-9552 > URL: https://issues.jboss.org/browse/WFLY-9552 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 12.0.0.CR1 > > > Enable the new SubordinationManager orphan detection check added in JBTM-2955 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2326) [Project Oriented] Organizational unit should be called Team in documentation

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2326: ------------------------------------ Summary: [Project Oriented] Organizational unit should be called Team in documentation Key: DROOLS-2326 URL: https://issues.jboss.org/browse/DROOLS-2326 Project: Drools Issue Type: Bug Components: docs Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2325) [Project Oriented] REST Documentation needs an update

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2325: ------------------------------------ Summary: [Project Oriented] REST Documentation needs an update Key: DROOLS-2325 URL: https://issues.jboss.org/browse/DROOLS-2325 Project: Drools Issue Type: Bug Components: docs Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8494) Sharply increased memory consumption (+ ~50 MB) in full profile

by nilesh ratta (JIRA)

[ https://issues.jboss.org/browse/WFLY-8494?page=com.atlassian.jira.plugin.... ] nilesh ratta commented on WFLY-8494: ------------------------------------ Hi, i am still facing performance issues in Wildfly 11 Note : *I am facing some performance issues in WildFly11 as my 90% gets increased for same set of run as it was in Jboss. And minor GC gets increased to 7 times as it was in jboss. And there is no application level code changes in wildfly11.* Please refer issue : WFLY-9835 > Sharply increased memory consumption (+ ~50 MB) in full profile > --------------------------------------------------------------- > > Key: WFLY-8494 > URL: https://issues.jboss.org/browse/WFLY-8494 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 11.0.0.Beta1 > > > Memory footprint of full profile after server start jumped 50 megabytes compared to EAP 7.1.0.DR11. Heap dump shows a few huge byte[] arrays referenced by {{io.netty.buffer.PoolChunk}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9843) EJB HTTP client 1.0.10.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9843: ------------------------------------ Summary: EJB HTTP client 1.0.10.Final Key: WFLY-9843 URL: https://issues.jboss.org/browse/WFLY-9843 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9739) JPA / Hibernate: There is already an object named 'x' in the database

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9739?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9739: ------------------------------------ Thanks Gail, yes, I will close this as a duplicate of [https://hibernate.atlassian.net/browse/HHH-12259]. > JPA / Hibernate: There is already an object named 'x' in the database > --------------------------------------------------------------------- > > Key: WFLY-9739 > URL: https://issues.jboss.org/browse/WFLY-9739 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 11.0.0.Final > Environment: Windows 10 64 bits / Windows Server 2012 R2 64 bits > Java version: 1.8.0_151 > SQL Server 2014 > Reporter: Eric SantAnna > Assignee: Scott Marlow > Attachments: sqljdbc4.jar, wildfly11-migration.zip > > > I'm getting an Exception as a warning in the server.log when a database object already exists an my persistence.xml has the property "hibernate.hbm2ddl.auto" set to "update". > This doesn't happen in my tests with 10.1.0.Final. > Appearently, despite these Exceptions, all my applications are running ok. > I saw this behaviour while I was migrating my application from JBoss 7.1.1.Final to Wildfly. I'm deciding between Wildfly 10.1 and 11. > This behaviour isn't good cause, I'm flooding the logs and it doesn't seem reliable for my manager. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9739) JPA / Hibernate: There is already an object named 'x' in the database

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9739?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-9739. ------------------------------ Resolution: Duplicate Issue > JPA / Hibernate: There is already an object named 'x' in the database > --------------------------------------------------------------------- > > Key: WFLY-9739 > URL: https://issues.jboss.org/browse/WFLY-9739 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 11.0.0.Final > Environment: Windows 10 64 bits / Windows Server 2012 R2 64 bits > Java version: 1.8.0_151 > SQL Server 2014 > Reporter: Eric SantAnna > Assignee: Scott Marlow > Attachments: sqljdbc4.jar, wildfly11-migration.zip > > > I'm getting an Exception as a warning in the server.log when a database object already exists an my persistence.xml has the property "hibernate.hbm2ddl.auto" set to "update". > This doesn't happen in my tests with 10.1.0.Final. > Appearently, despite these Exceptions, all my applications are running ok. > I saw this behaviour while I was migrating my application from JBoss 7.1.1.Final to Wildfly. I'm deciding between Wildfly 10.1 and 11. > This behaviour isn't good cause, I'm flooding the logs and it doesn't seem reliable for my manager. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9567) Setting 'eclipselink.archive.factory' property should NOT depend on 'eclipselink.target-server' being set

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9567?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9567: ------------------------------------ Thanks for reporting this [~jlukas]! > Setting 'eclipselink.archive.factory' property should NOT depend on 'eclipselink.target-server' being set > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-9567 > URL: https://issues.jboss.org/browse/WFLY-9567 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Lukas Jungmann > Assignee: Scott Marlow > Fix For: 13.0.0.Beta1 > > > After applying patch from https://bugs.eclipse.org/bugs/show_bug.cgi?id=414974 on EclipseLink side and removing 'eclipselink.archive.factory' from WildFly's JVM options, 99,9% of tests started to fail on the server. > Problem is that majority of our PU's do have set 'eclipselink.target-server' property (for various reasons) - in this case container as of[1] won't pass its 'eclipselink.archive.factory' to EclipseLink and deployments fail with: > {noformat} > [EL Severe]: 2017-11-23 13:14:31.974--ServerSession(1652754085)--Local Exception Stack: > Exception [EclipseLink-28014] (Eclipse Persistence Services - 2.7.1.qualifier): org.eclipse.persistence.exceptions.EntityManagerSetupException > Exception Description: Exception was thrown while processing property [eclipselink.descriptor.customizer.Project] with value [org.eclipse.persistence.testing.models.jpa.advanced.Customizer]. > Internal Exception: java.lang.ClassNotFoundException: Project from [Module "deployment.eclipselink-advanced-model.ear.eclipselink-advanced-model_ejb.jar" from Service Module Loader] > at org.eclipse.persistence.exceptions.EntityManagerSetupException.failedWhileProcessingProperty(EntityManagerSetupException.java:199) > at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.processDescriptorCustomizers(EntityManagerSetupImpl.java:2941) > ... > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.ClassNotFoundException: Project from [Module "deployment.eclipselink-advanced-model.ear.eclipselink-advanced-model_ejb.jar" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at org.eclipse.persistence.internal.security.PrivilegedAccessHelper.getClassForName(PrivilegedAccessHelper.java:165) > at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.findClass(EntityManagerSetupImpl.java:1321) > at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.processDescriptorCustomizers(EntityManagerSetupImpl.java:2938) > ... 82 more > {noformat} > [1]: https://github.com/wildfly/wildfly/blob/a10034a/jpa/eclipselink/src/main/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9567) Setting 'eclipselink.archive.factory' property should NOT depend on 'eclipselink.target-server' being set

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9567?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-9567: ------------------------------- Fix Version/s: 13.0.0.Beta1 > Setting 'eclipselink.archive.factory' property should NOT depend on 'eclipselink.target-server' being set > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-9567 > URL: https://issues.jboss.org/browse/WFLY-9567 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Lukas Jungmann > Assignee: Scott Marlow > Fix For: 13.0.0.Beta1 > > > After applying patch from https://bugs.eclipse.org/bugs/show_bug.cgi?id=414974 on EclipseLink side and removing 'eclipselink.archive.factory' from WildFly's JVM options, 99,9% of tests started to fail on the server. > Problem is that majority of our PU's do have set 'eclipselink.target-server' property (for various reasons) - in this case container as of[1] won't pass its 'eclipselink.archive.factory' to EclipseLink and deployments fail with: > {noformat} > [EL Severe]: 2017-11-23 13:14:31.974--ServerSession(1652754085)--Local Exception Stack: > Exception [EclipseLink-28014] (Eclipse Persistence Services - 2.7.1.qualifier): org.eclipse.persistence.exceptions.EntityManagerSetupException > Exception Description: Exception was thrown while processing property [eclipselink.descriptor.customizer.Project] with value [org.eclipse.persistence.testing.models.jpa.advanced.Customizer]. > Internal Exception: java.lang.ClassNotFoundException: Project from [Module "deployment.eclipselink-advanced-model.ear.eclipselink-advanced-model_ejb.jar" from Service Module Loader] > at org.eclipse.persistence.exceptions.EntityManagerSetupException.failedWhileProcessingProperty(EntityManagerSetupException.java:199) > at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.processDescriptorCustomizers(EntityManagerSetupImpl.java:2941) > ... > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.ClassNotFoundException: Project from [Module "deployment.eclipselink-advanced-model.ear.eclipselink-advanced-model_ejb.jar" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at org.eclipse.persistence.internal.security.PrivilegedAccessHelper.getClassForName(PrivilegedAccessHelper.java:165) > at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.findClass(EntityManagerSetupImpl.java:1321) > at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.processDescriptorCustomizers(EntityManagerSetupImpl.java:2938) > ... 82 more > {noformat} > [1]: https://github.com/wildfly/wildfly/blob/a10034a/jpa/eclipselink/src/main/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9842) Enhance CommandDispatcher's async methods to return CompletableFutures

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9842?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9842: ------------------------------- Description: This allows consumers of CommandDispatcher to implement non-blocking handling of dispatched commands. The submitOnNode(...) method can just be modified to return the more specific return value. However, the submitOnCluster(...) will need a different method name (or signature). The MessageDispatcher in JGroups 4 now returns CompletableFutures natively, which means we can easily support this without the addition of yet another thread pool. was: This allows consumers of CommandDispatcher to implement non-blocking handling of dispatched commands. The submitOnNode(...) method can just be modified to return the more specific return value. However, the submitOnCluster(...) will need a different method name (or signature). > Enhance CommandDispatcher's async methods to return CompletableFutures > ---------------------------------------------------------------------- > > Key: WFLY-9842 > URL: https://issues.jboss.org/browse/WFLY-9842 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > This allows consumers of CommandDispatcher to implement non-blocking handling of dispatched commands. > The submitOnNode(...) method can just be modified to return the more specific return value. However, the submitOnCluster(...) will need a different method name (or signature). > The MessageDispatcher in JGroups 4 now returns CompletableFutures natively, which means we can easily support this without the addition of yet another thread pool. -- 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 February 2018