January 2016 - jboss-jira - Jboss List Archives

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

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6033?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-6033: ------------------------------- Fix Version/s: (was: 10.0.0.Final) > enable JPA entity class transformation if any of the new Hibernate hibernate 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, 5 months

1
0
0 / 0

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

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6033?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-6033: ------------------------------- Affects Version/s: 10.0.0.CR5 > enable JPA entity class transformation if any of the new Hibernate hibernate 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, 5 months

1
0
0 / 0

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

by Scott Marlow (JIRA)

Scott Marlow created WFLY-6033: ---------------------------------- Summary: enable JPA entity class transformation if any of the new Hibernate hibernate properties are enabled Key: WFLY-6033 URL: https://issues.jboss.org/browse/WFLY-6033 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 10.0.0.Final 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6032) Stuck Thread Detection

by Carlton Zachary (JIRA)

Carlton Zachary created WFLY-6032: ------------------------------------- Summary: Stuck Thread Detection Key: WFLY-6032 URL: https://issues.jboss.org/browse/WFLY-6032 Project: WildFly Issue Type: Feature Request Reporter: Carlton Zachary Assignee: Jason Greene Is it possible to add a stuck tread detection in WildFly. It appears this is being added to Tomcat 9 and would be nice feature to have in WFLY (https://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Stuck_Thread_D...). This doesn't have to be a valve as it is in Tomcat, since WildFly doesn't use Valves, but perhaps via some other mechanism. 1. Display in console for the particular server instance that is having a stuck thread issue. 2. Also report this in the server.log. This type of feature also exists in WebLogic currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[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 edited comment on WFLY-5822 at 1/19/16 1:16 PM: -------------------------------------------------------------------- Upon running with the jvmStatisticsInterval, noticed two things: 1. the total memory is not being recorded for EAP7 runs, which use JDK8. It is being reported for the EAP6 runs. The total memory statistics are being reported as null even with jvmStatisticsInterval turned on. {noformat} 2016/01/19 12:24:19:452 EST [DEBUG][Thread-7] HOST perf29.mw.lab.eng.bos.redhat.com:rootProcess:c - Aggregated stats: [perf32.youngGen: 594,perf32.survivorGen: 22,perf32.tenuredGen: 69,perf32.permGen: 686,perf32.memTotal: null,perf33.youngGen: 724,perf33.survivorGen: 20,perf33.tenuredGen: 61,perf33.permGen: 807,perf33.memTotal: null,perf29.count: 1] {noformat} Maybe the plugin for this component needs to be updated for JDK 8? 2. we have this wierdness with the tenured generation heap: 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... Tenured gen is rising without falling on the servers for EAP 7 which doesn't look healthy. was (Author: rachmato): Upon running with the jvmStatisticsInterval, noticed two things: 1. the total memory is not being recorded for EAP7 runs, which use JDK8. It is being reported for the EAP6 runs. The total memory statistics are being reported as null even with jvmStatisticsInterval turned on. Maybe the plugin for this component needs to be updated for JDK 8? 2. we have this wierdness with the tenured generation heap: 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... Tenured gen is rising without falling on the servers for EAP 7 which doesn't look healthy. > 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, 5 months

1
0
0 / 0

[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 edited comment on WFLY-5822 at 1/19/16 1:13 PM: -------------------------------------------------------------------- Upon running with the jvmStatisticsInterval, noticed two things: 1. the total memory is not being recorded for EAP7 runs, which use JDK8. It is being reported for the EAP6 runs. The total memory statistics are being reported as null even with jvmStatisticsInterval turned on. Maybe the plugin for this component needs to be updated for JDK 8? 2. we have this wierdness with the tenured generation heap: 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... Tenured gen is rising without falling on the servers for EAP 7 which doesn't look healthy. was (Author: rachmato): Upon running with the jvmStatisticsInterval, noticed two things: 1. the total memory is not being recorded for EAP7 runs, which use JDK8. Also, the total memory statistics are being reported as null even with jvmStatisticsInterval turned on. Maybe the plugin for this component needs to be updated for JDK 8? 2. we have this wierdness with the tenured generation heap: 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... Tenured gen is rising without falling on the servers for EAP 7 which doesn't look healthy. > 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, 5 months

1
0
0 / 0

[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: ------------------------------------------- Upon running with the jvmStatisticsInterval, noticed two things: 1. the total memory is not being recorded for EAP7 runs, which use JDK8. Also, the total memory statistics are being reported as null even with jvmStatisticsInterval turned on. Maybe the plugin for this component needs to be updated for JDK 8? 2. we have this wierdness with the tenured generation heap: 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... Tenured gen is rising without falling on the servers for EAP 7 which doesn't look healthy. > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1310) System allows enabling two applications with same runtime-name

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-1310: ----------------------------------------- Summary: System allows enabling two applications with same runtime-name Key: WFCORE-1310 URL: https://issues.jboss.org/browse/WFCORE-1310 Project: WildFly Core Issue Type: Bug Components: Domain Management Environment: WildFly 10CR4 standalone and domain. Both web management and command line Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet System allows multiple applications with same runtime-name to be enabled at the same time, which shoudl be avoided. It correctly prevents the deployment of an enabled second application, but doesn't complain if deploying disabled and enabling after that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[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 edited comment on WFLY-5822 at 1/19/16 11:41 AM: --------------------------------------------------------------------- All the memory stats collected by the driver node are being reported as null: {noformat} 2016/01/19 09:52:04:632 EST [DEBUG][Thread-7] HOST perf29.mw.lab.eng.bos.redhat.com:rootProcess:c - Aggregated stats: [perf32.youngGen: null,perf32.survivorGen: null,perf32.tenuredGen: null,perf32.permGen: null,perf32.memTotal: null,perf33.youngGen: null,perf33.survivorGen: null,perf33.tenuredGen: null,perf33.permGen: null,perf33.memTotal: null,perf29.count: 4] {noformat} Is this broken? It seems to be as I see the same issue in earlier test runs. This should be fixed as server side memory issues are a potential cause for concern. We (Rado) did a check and found it was disabled, so enabling by adding jvmStatisticsInterval 30000; to the configuration. was (Author: rachmato): All the memory stats collected by the driver node are being reported as null: {noformat} 2016/01/19 09:52:04:632 EST [DEBUG][Thread-7] HOST perf29.mw.lab.eng.bos.redhat.com:rootProcess:c - Aggregated stats: [perf32.youngGen: null,perf32.survivorGen: null,perf32.tenuredGen: null,perf32.permGen: null,perf32.memTotal: null,perf33.youngGen: null,perf33.survivorGen: null,perf33.tenuredGen: null,perf33.permGen: null,perf33.memTotal: null,perf29.count: 4] {noformat} Is this broken? It seems to be as I see the same issue in earlier test runs. This should be fixed as server side memory issues are a potential cause for concern. > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1277) Embed-server from CLI launch shows twice prompt string

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1277?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1277: ------------------------------------- Priority: Blocker (was: Minor) > Embed-server from CLI launch shows twice prompt string > ------------------------------------------------------ > > Key: WFCORE-1277 > URL: https://issues.jboss.org/browse/WFCORE-1277 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Chao Wang > Assignee: Ståle Pedersen > Priority: Blocker > Fix For: 2.0.8.Final > > > {noformat} > When I launch an embed-server from CLI, it displays twice [standalone@embedded /] [standalone@embedded /] for the first time. > [wangc@dhcp-128-40 wildfly-10.0.0.Final-SNAPSHOT]$ sh bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server > [standalone@embedded /] [standalone@embedded /] ls > core-service launch-type=EMBEDDED product-version=undefined > deployment management-major-version=4 profile-name=undefined > deployment-overlay management-micro-version=0 release-codename=Kenny > extension management-minor-version=0 release-version=2.0.5.Final > interface name=dhcp-128-40 running-mode=ADMIN_ONLY > path namespaces=[] schema-locations=[] > socket-binding-group organization=undefined server-state=running > subsystem process-type=Server suspend-state=RUNNING > system-property product-name=undefined uuid=8c4ede2f-8e14-48bf-9eaf-73947e23edcf > [standalone@embedded /] quit > {noformat} > This does not happen in 2.0.4.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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