January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-5822: ------------------------------------------- I did a run of two ejbservlet-repl-sync jobs with verbose GC turned on: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-stre... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-6x-stre... The servers are perf32 and perf33. The tenured generation on perf33 rises and falls as would be expected. The tenuted geneation on perf32 however does not rise and fall, but just rises continuously until the end of the job. > Clustering performance regression in ejbremote-dist-sync scenario > ------------------------------------------------------------------ > > Key: WFLY-5822 > URL: https://issues.jboss.org/browse/WFLY-5822 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Priority: Critical > > Compared to EAP 6, all SYNC scenarios have the same/better performance except of this one, wonder why? > Compare these results: > stress-ejbremote-dist-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > --------------------------------------- > Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand: > stress-ejbremote-repl-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1311) WFCORE-893 Fix breaks mixed-domain

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1311: ---------------------------------------- Summary: WFCORE-893 Fix breaks mixed-domain Key: WFCORE-1311 URL: https://issues.jboss.org/browse/WFCORE-1311 Project: WildFly Core Issue Type: Bug Components: Domain Management, Remoting Affects Versions: 2.0.7.Final Reporter: Brian Stansberry Priority: Critical Fix For: 2.0.8.Final The WFCORE-893 fix breaks mixed-domain use cases by adding subsystem=io if its not present. That's ok for standalone, but in a domain it means a subsystem not understood by legacy slaves will get added into profiles used by those slaves. Which will fail. I've considered doing some sort of transformer trick to discard this subsystem if its config is default, but I suspect it's better to just not do the WFCORE-893 thing on the DC. Discarding might be ok if we just do a resource transformer discard but reject all ops thereafter. Idea being that if the io config is default, matching what legacy slaves did, then we let the slave boot. Then any subsequent op must be either pointless or moving away from default, and must be rejected. But still, just not doing the WFCORE-893 thing on the DC is probably better. Or at least simpler right now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1312) WFCORE-893 Fix breaks mixed-domain

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1312: ---------------------------------------- Summary: WFCORE-893 Fix breaks mixed-domain Key: WFCORE-1312 URL: https://issues.jboss.org/browse/WFCORE-1312 Project: WildFly Core Issue Type: Bug Components: Domain Management, Remoting Affects Versions: 2.0.7.Final Reporter: Brian Stansberry Priority: Critical Fix For: 2.0.8.Final The WFCORE-893 fix breaks mixed-domain use cases by adding subsystem=io if its not present. That's ok for standalone, but in a domain it means a subsystem not understood by legacy slaves will get added into profiles used by those slaves. Which will fail. I've considered doing some sort of transformer trick to discard this subsystem if its config is default, but I suspect it's better to just not do the WFCORE-893 thing on the DC. Discarding might be ok if we just do a resource transformer discard but reject all ops thereafter. Idea being that if the io config is default, matching what legacy slaves did, then we let the slave boot. Then any subsequent op must be either pointless or moving away from default, and must be rejected. But still, just not doing the WFCORE-893 thing on the DC is probably better. Or at least simpler right now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6033) enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6033?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-6033: ------------------------------------ This change ensures that Hibernate 5.0 class transformation will be allowed. Current workaround is for application to set persistence unit property jboss.as.jpa.classtransformer="true" > enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled > -------------------------------------------------------------------------------------------------- > > Key: WFLY-6033 > URL: https://issues.jboss.org/browse/WFLY-6033 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.CR5 > Reporter: Scott Marlow > Assignee: Scott Marlow > > See new Hibernate properties at [https://github.com/hibernate/hibernate-orm/commit/809e3cf4b9eda5c8922bb8a...]. > New properties that influence entity class transformation are: > {quote} > hibernate.enhancer.enableDirtyTracking > hibernate.enhancer.enableLazyInitialization > hibernate.enhancer.enableAssociationManagement > {quote} > If any of the above properties are true, it is the same as the application setting jboss.as.jpa.classtransformer=true. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-74) Add ability to generate formatted files of logging id's for documentation purposes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-74?page=com.atlassian.jira.plugin... ] James Perkins updated LOGTOOL-74: --------------------------------- Description: Generate files that can be used for documentation purposes with the log id, message, log level (if available) and return type (for message bundles). (was: Generate files that can be used for documentation purposes with the log id, message, log level (if available) and return type (for message bundles). Options could be to leave off messages with no id or specify included/excluded interfaces.) > Add ability to generate formatted files of logging id's for documentation purposes > ---------------------------------------------------------------------------------- > > Key: LOGTOOL-74 > URL: https://issues.jboss.org/browse/LOGTOOL-74 > Project: Log Tool > Issue Type: Feature Request > Reporter: James Perkins > Assignee: James Perkins > Priority: Optional > Fix For: 2.1.0.Alpha1 > > > Generate files that can be used for documentation purposes with the log id, message, log level (if available) and return type (for message bundles). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-74) Add ability to generate formatted files of logging id's for documentation purposes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-74?page=com.atlassian.jira.plugin... ] James Perkins updated LOGTOOL-74: --------------------------------- Description: Generate files that can be used for documentation purposes with the log id, message, log level (if available) and return type (for message bundles). Options could be to leave off messages with no id or specify included/excluded interfaces. was: Possibly use something like JSON to generate the logging id's with the message. Options could be to leave off messages with no id or specify included/excluded interfaces. > Add ability to generate formatted files of logging id's for documentation purposes > ---------------------------------------------------------------------------------- > > Key: LOGTOOL-74 > URL: https://issues.jboss.org/browse/LOGTOOL-74 > Project: Log Tool > Issue Type: Feature Request > Reporter: James Perkins > Assignee: James Perkins > Priority: Optional > Fix For: 2.1.0.Alpha1 > > > Generate files that can be used for documentation purposes with the log id, message, log level (if available) and return type (for message bundles). > Options could be to leave off messages with no id or specify included/excluded interfaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-74) Add ability to generate formatted files of logging id's for documentation purposes

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGTOOL-74?page=com.atlassian.jira.plugin... ] James Perkins updated LOGTOOL-74: --------------------------------- Fix Version/s: 2.1.0.Alpha1 > Add ability to generate formatted files of logging id's for documentation purposes > ---------------------------------------------------------------------------------- > > Key: LOGTOOL-74 > URL: https://issues.jboss.org/browse/LOGTOOL-74 > Project: Log Tool > Issue Type: Feature Request > Reporter: James Perkins > Assignee: James Perkins > Priority: Optional > Fix For: 2.1.0.Alpha1 > > > Generate files that can be used for documentation purposes with the log id, message, log level (if available) and return type (for message bundles). > Options could be to leave off messages with no id or specify included/excluded interfaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5874) EclipseLink tests fail with security manager

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-5874?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-5874. ------------------------------ Resolution: Done > EclipseLink tests fail with security manager > -------------------------------------------- > > Key: WFLY-5874 > URL: https://issues.jboss.org/browse/WFLY-5874 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate, Test Suite > Reporter: Ondrej Kotek > Assignee: Scott Marlow > > *EclipseLinkSharedModuleProviderTestCase#testSimpleCreateAndLoadEntities* > {{./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -DfailIfNoTests=false -Dsecurity.manager -Dts.compat -Dts.noSmoke -Dtest=org.jboss.as.test.compat.jpa.eclipselink.EclipseLinkSharedModuleProviderTestCase#testSimpleCreateAndLoadEntities}} > fails with: > {noformat} > javax.ejb.EJBException: javax.persistence.PersistenceException: Exception [EclipseLink-28019] (Eclipse Persistence Services - 2.6.0.v20150309-bf26070): org.eclipse.persistence.exceptions.EntityManagerSetupException > Exception Description: Deployment of PersistenceUnit [hibernate3_pc] failed. Close all factories for this PersistenceUnit. > Internal Exception: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "accessDeclaredMembers")" in code source "(vfs:/content/toplink_module_test.ear/beans.jar <no signer certificates>)" of "null") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:273) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.Class.checkMemberAccess(Class.java:2348) > at java.lang.Class.getDeclaredMethods(Class.java:1974) > at org.eclipse.persistence.internal.security.PrivilegedAccessHelper.getDeclaredMethods(PrivilegedAccessHelper.java:339) > at org.eclipse.persistence.internal.jpa.metadata.listeners.EntityListenerMetadata.getDeclaredMethods(EntityListenerMetadata.java:249) > at org.eclipse.persistence.internal.jpa.metadata.listeners.EntityClassListenerMetadata.process(EntityClassListenerMetadata.java:89) > at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.processListeners(EntityAccessor.java:1226) > at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.addEntityListeners(MetadataProcessor.java:140) > at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:634) > at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getAbstractSession(EntityManagerFactoryDelegate.java:205) > at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:305) > at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:337) > at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:303) > at org.jboss.as.jpa.container.TransactionScopedEntityManager.createEntityManager(TransactionScopedEntityManager.java:186) > at org.jboss.as.jpa.container.TransactionScopedEntityManager.getOrCreateTransactionScopedEntityManager(TransactionScopedEntityManager.java:157) > at org.jboss.as.jpa.container.TransactionScopedEntityManager.getEntityManager(TransactionScopedEntityManager.java:87) > at org.jboss.as.jpa.container.AbstractEntityManager.persist(AbstractEntityManager.java:580) > at org.jboss.as.test.compat.jpa.eclipselink.SFSB1.createEmployee(SFSB1.java:44) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6033) enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6033?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-6033: ------------------------------- Description: See new Hibernate properties at [https://github.com/hibernate/hibernate-orm/commit/809e3cf4b9eda5c8922bb8a...]. New properties that influence entity class transformation are: {quote} hibernate.enhancer.enableDirtyTracking hibernate.enhancer.enableLazyInitialization hibernate.enhancer.enableAssociationManagement {quote} If any of the above properties are true, it is the same as the application setting jboss.as.jpa.classtransformer=true. was: See new Hibernate properties at [https://github.com/hibernate/hibernate-orm/commit/809e3cf4b9eda5c8922bb8a...]. New properties that influence entity class transformation are: {quote} hibernate.enhancer.enableDirtyTracking hibernate.enhancer.enableLazyInitialization hibernate.enhancer.enableAssociationManagement {quote} > enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled > -------------------------------------------------------------------------------------------------- > > Key: WFLY-6033 > URL: https://issues.jboss.org/browse/WFLY-6033 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.CR5 > Reporter: Scott Marlow > Assignee: Scott Marlow > > See new Hibernate properties at [https://github.com/hibernate/hibernate-orm/commit/809e3cf4b9eda5c8922bb8a...]. > New properties that influence entity class transformation are: > {quote} > hibernate.enhancer.enableDirtyTracking > hibernate.enhancer.enableLazyInitialization > hibernate.enhancer.enableAssociationManagement > {quote} > If any of the above properties are true, it is the same as the application setting jboss.as.jpa.classtransformer=true. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6033) enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6033?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-6033: ------------------------------- Summary: enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled (was: enable JPA entity class transformation if any of the new Hibernate hibernate properties are enabled) > enable JPA entity class transformation if any of the new Hibernate enhancer properties are enabled > -------------------------------------------------------------------------------------------------- > > Key: WFLY-6033 > URL: https://issues.jboss.org/browse/WFLY-6033 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.CR5 > Reporter: Scott Marlow > Assignee: Scott Marlow > > See new Hibernate properties at [https://github.com/hibernate/hibernate-orm/commit/809e3cf4b9eda5c8922bb8a...]. > New properties that influence entity class transformation are: > {quote} > hibernate.enhancer.enableDirtyTracking > hibernate.enhancer.enableLazyInitialization > hibernate.enhancer.enableAssociationManagement > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016