November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5603) Get data source information

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5603?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5603: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Get data source information > --------------------------- > > Key: WFLY-5603 > URL: https://issues.jboss.org/browse/WFLY-5603 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Jesper Pedersen > Assignee: Lin Gao > Fix For: 11.0.0.Alpha1 > > > Create a DMR operation that returns the available properties for the data source class, and xa data source class for the <driver> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5644) EJB timers should use a different logging category to separate it from other EJB invocations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5644?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5644: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > EJB timers should use a different logging category to separate it from other EJB invocations > -------------------------------------------------------------------------------------------- > > Key: WFLY-5644 > URL: https://issues.jboss.org/browse/WFLY-5644 > Project: WildFly > Issue Type: Feature Request > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Labels: ejb, timer, timers, timerservice > Fix For: 11.0.0.Alpha1 > > > To analyze timer behaviour or track issues related to timers sometimes a log level higher than INFO is needed. > Unfortunately the category "org.jboss.as.ejb3" does not make a differenciation and setting this category to DEBUG or TRACE cause a high amount of log messages, this can have performance impacts and make it dfficult to handle and read the logfiles. > It should be possible to have a separate category for timers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4591) Memory leak inPerThreadTagHandlerPool | Wildfly 8.2.0.Final (Undertow)

by Cosmin Stroe (JIRA)

[ https://issues.jboss.org/browse/WFLY-4591?page=com.atlassian.jira.plugin.... ] Cosmin Stroe commented on WFLY-4591: ------------------------------------ We have ran into the same memory leak in Wildfly 8.2.0.Final, but we are not able to use your attached Jastow JAR, as there are incompatible changes: {code:java} ^[[0m^[[31m14:27:38,793 ERROR MSC service thread 1-1 [fail] MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host/syncstorer.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./syncstorer.UndertowDeploymentInfoService: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoSuchMethodError: io.undertow.jsp.JspServletBuilder.setupDeployment(Lio/undertow/servlet/api/DeploymentInfo;Ljava/util/HashMap;Ljava/util/HashMap;Lorg/apache/tomcat/InstanceManager;)V at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:577) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:256) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) ... 3 more {code} How were you able to fix this memory leak? Is there a workaround? > Memory leak inPerThreadTagHandlerPool | Wildfly 8.2.0.Final (Undertow) > ---------------------------------------------------------------------- > > Key: WFLY-4591 > URL: https://issues.jboss.org/browse/WFLY-4591 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Environment: CentOS release 6.5 (Final), java version "1.7.0_71" 64 bit VM, Wildfly 8.2.0.Final, Min heap and Max heap 1536m > > Reporter: Srivathsan Agaram Venkatavaradhan > Assignee: Tomaz Cerar > Labels: garbage, jastow, undertow, wildfly > Fix For: 10.0.0.Alpha3 > > Attachments: jastow-2.0.0-SNAPSHOT.jar > > > We upgraded from Jboss 7.1.1.Final to Wildfly 8.2.0.Final. After the upgrade we are seeing full frequent garbage collection (happening every 2 mins) during load test. This was not the case in Jboss 7.1.1.Final. Our heap dumps suggested that there is huge memory leak with > org.apache.jasper.runtime.BodyContentImpl. This is part of JSP runtime (jastow). On analysis we found that undertow uses default as PerThreadTagHanlderPool. By changing this to TagHanlderPool, this issue seems to vanish. > diff --git a/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java b/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java > index eaa8560..c6c785f 100644 > --- a/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java > +++ b/src/main/java/org/apache/jasper/runtime/TagHandlerPool.java > @@ -53,7 +53,7 @@ public class TagHandlerPool { > result = null; > } > } > - if( result==null ) result=new PerThreadTagHandlerPool(); > + if( result==null ) result=new TagHandlerPool(); > result.init(config); > > return result; > - See more at: https://developer.jboss.org/message/927538#927538 > I think this issue may be related to https://issues.jboss.org/browse/WFLY-4617 as there were huge garbage created and most of the contents were char array (rendered html). May be TagHanlderPool is creating more char instead of reusing from pool. Please provide thoughts. I can share, heapdump or MAT screenshots if needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1174) Management Model not refreshed on changes

by Guillermo González de Agüero (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1174?page=com.atlassian.jira.plugi... ] Guillermo González de Agüero closed WFCORE-1174. ------------------------------------------------ Resolution: Done Sorry, I wanted to open this issue on the HAL project. > Management Model not refreshed on changes > ----------------------------------------- > > Key: WFCORE-1174 > URL: https://issues.jboss.org/browse/WFCORE-1174 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Guillermo González de Agüero > > It seems to make only one request per resource. Would be really nice if it can be updated on configuration changes, as it does on the console when changes are done via the model. > Extended steps: > - Start WildFly > - Go to Configuration and create a new interface: "new-interface". > - Open the Management Model and click on "interfaces". It issues a request and "new-interface" interface is present. > - Now create another interface: "newer-interface". > - Go again to the Management Model. "newer-interface" is not there. You have to manually refresh the model in order to see it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1174) Management Model not refreshed on changes

by Guillermo González de Agüero (JIRA)

Guillermo González de Agüero created WFCORE-1174: ---------------------------------------------------- Summary: Management Model not refreshed on changes Key: WFCORE-1174 URL: https://issues.jboss.org/browse/WFCORE-1174 Project: WildFly Core Issue Type: Enhancement Reporter: Guillermo González de Agüero It seems to make only one request per resource. Would be really nice if it can be updated on configuration changes, as it does on the console when changes are done via the model. Extended steps: - Start WildFly - Go to Configuration and create a new interface: "new-interface". - Open the Management Model and click on "interfaces". It issues a request and "new-interface" interface is present. - Now create another interface: "newer-interface". - Go again to the Management Model. "newer-interface" is not there. You have to manually refresh the model in order to see it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1161) Simplification of setCapabilityReference where resource only exposes a single capability.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1161?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1161: ------------------------------------- Fix Version/s: 3.0.0.Alpha1 > Simplification of setCapabilityReference where resource only exposes a single capability. > ----------------------------------------------------------------------------------------- > > Key: WFCORE-1161 > URL: https://issues.jboss.org/browse/WFCORE-1161 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Labels: affects_elytron > Fix For: 3.0.0.Alpha1 > > > Currently we need to use the following method to specify that one of our attributes is a reference to another capability: - > {code} > public BUILDER setCapabilityReference(String referencedCapability, String dependentCapability, boolean dynamicDependent) { > referenceRecorder = new CapabilityReferenceRecorder.DefaultCapabilityReferenceRecorder(referencedCapability, dependentCapability, dynamicDependent); > return (BUILDER) this; > } > {code} > However the resource has already indicated the capability it provides and indicated whether it is dynamic so the last two parameters duplicate this information. > This makes it much harder to re-use attribute definitions across different resources as even though they may reference the same time they now contain information about the resource they are used within. > As discussed previously there is still the case that a single resource could provide multiple capabilities and this additional information may be required to clarify which capability it is in relation to but in general if a resource only provides a single capability we should be able to detect that without the additional information on the attribute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1168) Incorrect null check in SimpleResourceDefinition.Parameter.setDeprecatedSince

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1168?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1168: ------------------------------------- Description: The null check checks the field being assigned instead of the param passed in: {code} public Parameters setDeprecatedSince(ModelVersion deprecatedSince) { if (deprecationData == null) { // <-- OOPS! throw ControllerLogger.ROOT_LOGGER.nullVar("deprecatedSince"); } this.deprecationData = new DeprecationData(deprecatedSince); {code} The field will always be null, making this method useless. was: The null check checks the field being assigned instead of the param passed in: {code} public Parameters setDeprecatedSince(ModelVersion deprecatedSince) { if (deprecationData == null) { // <-- OOPS! throw ControllerLogger.ROOT_LOGGER.nullVar("deprecatedSince"); } this.deprecationData = new DeprecationData(deprecatedSince); {code} > Incorrect null check in SimpleResourceDefinition.Parameter.setDeprecatedSince > ----------------------------------------------------------------------------- > > Key: WFCORE-1168 > URL: https://issues.jboss.org/browse/WFCORE-1168 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.3.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.4.Final > > > The null check checks the field being assigned instead of the param passed in: > > {code} > public Parameters setDeprecatedSince(ModelVersion deprecatedSince) { > if (deprecationData == null) { // <-- OOPS! > throw ControllerLogger.ROOT_LOGGER.nullVar("deprecatedSince"); > } > this.deprecationData = new DeprecationData(deprecatedSince); > {code} > The field will always be null, making this method useless. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1173) Incorrect null check in SimpleResourceDefinition.Parameter.setDeprecatedSince

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1173: ---------------------------------------- Summary: Incorrect null check in SimpleResourceDefinition.Parameter.setDeprecatedSince Key: WFCORE-1173 URL: https://issues.jboss.org/browse/WFCORE-1173 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.0.3.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 2.0.4.Final The null check checks the field being assigned instead of the param passed in: {code} public Parameters setDeprecatedSince(ModelVersion deprecatedSince) { if (deprecationData == null) { // <-- OOPS! throw ControllerLogger.ROOT_LOGGER.nullVar("deprecatedSince"); } this.deprecationData = new DeprecationData(deprecatedSince); {code} The field will always be null, making this method useless. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1172) SimpleResourceDefinition.Parameters should support setting access constraints

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1172: ---------------------------------------- Summary: SimpleResourceDefinition.Parameters should support setting access constraints Key: WFCORE-1172 URL: https://issues.jboss.org/browse/WFCORE-1172 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Assignee: Tomaz Cerar Fix For: 3.0.0.Beta1 There are a lot of SimpleResourceDefinition impls that are overriding getAccessConstraints. We should support passing in the constraints via the Parameters object passed to the constructor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5750) Hibernate 5 hibernate-java8 jar is missing

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-5750?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-5750: ------------------------------- Fix Version/s: 10.0.0.CR5 > Hibernate 5 hibernate-java8 jar is missing > ------------------------------------------ > > Key: WFLY-5750 > URL: https://issues.jboss.org/browse/WFLY-5750 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.CR4 > Reporter: Juergen Zimmermann > Assignee: Scott Marlow > Fix For: 10.0.0.CR5 > > > In $JBOSS_HOME/modules/system/layers/base/org/hibernate/main are these JARs: > * hibernate-core > * hibernate-entitymanager > * hibernate-envers > However, org.hibernate:hibernate-java8 is missing. This JAR enables the use of Instant, LocalDate, LocalDateTime LocalTime, ... being part of the new time API in JDK 8. -- 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 November 2015