May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6173) Classes not unloaded after undeployment

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6173?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6173: ----------------------------------- Priority: Blocker (was: Major) > Classes not unloaded after undeployment > --------------------------------------- > > Key: WFLY-6173 > URL: https://issues.jboss.org/browse/WFLY-6173 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.2.0.Final, 10.0.0.Final > Reporter: Joey Wang > Assignee: Martin Kouba > Priority: Blocker > Fix For: 10.1.0.Final > > Attachments: memory-leak.zip > > > I deployed a small web application with one single JSF and one managed bean, accessed the page and then undeployed the application. I found the classes of this application had never been unloaded via monitoring with Java VistualVM, also using '-XX:+TraceClassUnloading' JVM option proved the classes not unloaded. > Then checking the heap dump of it, I found there were instance for each enum item (the managed bean has one enum type field, which is always initialized when the managed bean constructed) and one array instance including these enum instances. > Please refer to the attachment for the same application. I started to verify the classloader memory leak issue because we found hot redeployment of our real application swallow some memory each time, then after lots of redeployment the server was short of memories. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6173) Classes not unloaded after undeployment

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6173?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-6173: ----------------------------------- Fix Version/s: 10.1.0.Final > Classes not unloaded after undeployment > --------------------------------------- > > Key: WFLY-6173 > URL: https://issues.jboss.org/browse/WFLY-6173 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.2.0.Final, 10.0.0.Final > Reporter: Joey Wang > Assignee: Martin Kouba > Priority: Blocker > Fix For: 10.1.0.Final > > Attachments: memory-leak.zip > > > I deployed a small web application with one single JSF and one managed bean, accessed the page and then undeployed the application. I found the classes of this application had never been unloaded via monitoring with Java VistualVM, also using '-XX:+TraceClassUnloading' JVM option proved the classes not unloaded. > Then checking the heap dump of it, I found there were instance for each enum item (the managed bean has one enum type field, which is always initialized when the managed bean constructed) and one array instance including these enum instances. > Please refer to the attachment for the same application. I started to verify the classloader memory leak issue because we found hot redeployment of our real application swallow some memory each time, then after lots of redeployment the server was short of memories. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5464) JDR report contains reference to AS7

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-5464?page=com.atlassian.jira.plugin.... ] Ingo Weiss updated WFLY-5464: ----------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/8922 (was: https://github.com/wildfly/wildfly/pull/8657/files) > JDR report contains reference to AS7 > ------------------------------------ > > Key: WFLY-5464 > URL: https://issues.jboss.org/browse/WFLY-5464 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 10.0.0.CR2 > Reporter: Marek Kopecký > Assignee: Ingo Weiss > Priority: Minor > > *Description of problem:* > JDR report contains some legacy reference to AS7 > *How reproducible:* > Always > *Steps to Reproduce:* > # Create a JDR report using one of provided scripts (depends on OS) > # Check the created report > ## cd $JDR_LOCATION > ## find | grep as7 > *Actual results:* > {noformat} > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7 > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/configuration.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/tree.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/dump-services.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/deployment-dependencies.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jarcheck.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/cluster-proxies-configuration.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/local-module-dependencies.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/system-properties.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jndi-view.json > {noformat} > *Expected results:* > No references to AS7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5464) JDR report contains reference to AS7

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-5464?page=com.atlassian.jira.plugin.... ] Ingo Weiss reassigned WFLY-5464: -------------------------------- Assignee: Ingo Weiss (was: Bartosz Spyrko-Śmietanko) > JDR report contains reference to AS7 > ------------------------------------ > > Key: WFLY-5464 > URL: https://issues.jboss.org/browse/WFLY-5464 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 10.0.0.CR2 > Reporter: Marek Kopecký > Assignee: Ingo Weiss > Priority: Minor > > *Description of problem:* > JDR report contains some legacy reference to AS7 > *How reproducible:* > Always > *Steps to Reproduce:* > # Create a JDR report using one of provided scripts (depends on OS) > # Check the created report > ## cd $JDR_LOCATION > ## find | grep as7 > *Actual results:* > {noformat} > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7 > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/configuration.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/tree.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/dump-services.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/deployment-dependencies.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jarcheck.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/cluster-proxies-configuration.json > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/local-module-dependencies.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/system-properties.txt > ./jdr_15-10-02_04-28-03_dhcp-10-40-5-38/sos_strings/as7/jndi-view.json > {noformat} > *Expected results:* > No references to AS7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6566) SAR deployer uses wrong MBean class to resolve source Method for property injection

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-6566?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-6566: -------------------------------- Labels: downstream_dependency (was: ) > SAR deployer uses wrong MBean class to resolve source Method for property injection > ----------------------------------------------------------------------------------- > > Key: WFLY-6566 > URL: https://issues.jboss.org/browse/WFLY-6566 > Project: WildFly > Issue Type: Bug > Components: JMX, Server > Affects Versions: 10.0.0.Final > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Labels: downstream_dependency > > If using a <value-factory> or <inject> element with "parameter" attribute in jboss-service.xml to inject a value from one bean to another, a "java.lang.IllegalArgumentException: object is not an instance of declaring class" error is raised during deployment. > jboss-service.xml > {noformat} > <server xmlns="urn:jboss:service:7.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jboss:service:7.0 jboss-service_7_0.xsd"> > <mbean code="com.test.redhat.mbean.OtherValueFactory" name="test:type=OtherValueFactory"> > <attribute name="WelcomeString">Welcome</attribute> > <attribute name="CustName">Other</attribute> > </mbean> > <mbean code="com.test.redhat.mbean.TestValueFactory" name="test:type=SarTestValueFactory"> > <depends>test:type=OtherValueFactory</depends> > <attribute name="WelcomeString">Welcome</attribute> > <attribute name="CustName"> > <value-factory bean="test:type=OtherValueFactory" method="getNameOfCustomer"> > <parameter class="java.lang.String">Foo</parameter> > </value-factory> > </attribute> > </mbean> > </server> > {noformat} > Full error: > {noformat} > 16:54:36,505 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "test.sar" (runtime-name: "test.sar") > 16:54:36,690 WARN [org.jboss.msc.inject] (MSC service thread 1-2) MSC000100: Unexpected failure to uninject public void com.test.redhat.mbean.TestValueFactory.setCustName(java.lang.String): java.lang.NullPointerException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.msc.value.MethodValue.getValue(MethodValue.java:62) > at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54) > at org.jboss.msc.value.Values.getValues(Values.java:68) > at org.jboss.msc.value.Values.getValues(Values.java:82) > at org.jboss.msc.inject.MethodInjector.uninject(MethodInjector.java:119) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1923) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1876) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 16:54:36,691 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.mbean.service.test:type=SarTestValueFactory.create: org.jboss.msc.service.StartException in service jboss.mbean.service.test:type=SarTestValueFactory.create: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.msc.inject.InjectionException: Injection failed > at org.jboss.msc.inject.MethodInjector.inject(MethodInjector.java:102) > at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1672) > at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:51) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1917) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1876) > ... 3 more > Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.msc.value.MethodValue.getValue(MethodValue.java:62) > at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54) > at org.jboss.msc.value.Values.getValues(Values.java:68) > at org.jboss.msc.value.Values.getValues(Values.java:82) > at org.jboss.msc.inject.MethodInjector.inject(MethodInjector.java:92) > ... 7 more > 16:54:36,697 INFO [com.test.redhat.mbean.OtherValueFactory] (ServerService Thread Pool -- 58) >> TestValuFactory.start() invoked > 16:54:36,698 INFO [stdout] (ServerService Thread Pool -- 58) TestValuFactory.start() invoked > 16:54:36,776 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "test.sar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.mbean.service.test:type=SarTestValueFactory.create" => "org.jboss.msc.service.StartException in service jboss.mbean.service.test:type=SarTestValueFactory.create: Failed to start service > Caused by: org.jboss.msc.inject.InjectionException: Injection failed > Caused by: java.lang.IllegalArgumentException: object is not an instance of declaring class"}} > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6569) Vault.sh can create keystore when doesn't exist. But we can't define KEY_SIZE for it.

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-6569?page=com.atlassian.jira.plugin.... ] Lin Gao reassigned WFLY-6569: ----------------------------- Assignee: Darran Lofthouse (was: Lin Gao) > Vault.sh can create keystore when doesn't exist. But we can't define KEY_SIZE for it. > ------------------------------------------------------------------------------------- > > Key: WFLY-6569 > URL: https://issues.jboss.org/browse/WFLY-6569 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > > Vault.sh can create keystore when doesn't exist. But we can't define KEY_SIZE for it. > Vault.sh have -t, --create-keystore parameter for create new keystore when it doesn't exist. > But we need define KEY_SIZE too in other case KEY_SIZE = 128 is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6570) Vault.sh can create keystore when doesn't exist. There has to exist file defined in -k, --keystore parameter.

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-6570?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-6570: -------------------------------- Labels: downstream_dependency (was: ) > Vault.sh can create keystore when doesn't exist. There has to exist file defined in -k, --keystore parameter. > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6570 > URL: https://issues.jboss.org/browse/WFLY-6570 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Lin Gao > Labels: downstream_dependency > > Vault.sh can create keystore when doesn't exist. > But there is a bug. Defined file in -k, --keystore parameter has to exist. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6638) EJB view service allows invocations through before component has started resulting in potential race

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6638?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-6638: ------------------------------------ Component/s: EJB Assignee: Stuart Douglas (was: Jason Greene) > EJB view service allows invocations through before component has started resulting in potential race > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-6638 > URL: https://issues.jboss.org/browse/WFLY-6638 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > The EJB view service does not suspend invocations when a component is not started, but instead forwards to the view interceptor chain. The view interceptors may not be ready yet, which can result in a race. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6638) EJB view service allows invocations through before component has started resulting in potential race

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6638: ------------------------------------ Summary: EJB view service allows invocations through before component has started resulting in potential race Key: WFLY-6638 URL: https://issues.jboss.org/browse/WFLY-6638 Project: WildFly Issue Type: Bug Reporter: Stuart Douglas Assignee: Jason Greene The EJB view service does not suspend invocations when a component is not started, but instead forwards to the view interceptor chain. The view interceptors may not be ready yet, which can result in a race. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6631) EJB 2.1 BMP Entity beans are not synchronized correctly

by Marco Zanker (JIRA)

[ https://issues.jboss.org/browse/WFLY-6631?page=com.atlassian.jira.plugin.... ] Marco Zanker updated WFLY-6631: ------------------------------- Issue Type: Bug (was: Feature Request) > EJB 2.1 BMP Entity beans are not synchronized correctly > ------------------------------------------------------- > > Key: WFLY-6631 > URL: https://issues.jboss.org/browse/WFLY-6631 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Marco Zanker > > This problem was discussed in the following threads and still exists in wildfly 10. > https://developer.jboss.org/message/794417 > https://issues.jboss.org/browse/WFLY-841 > But this is not alone a problem of EJB 2.1 CMP Beans. *EJB 2.1 BMP Beans also affected*. We are running in this problem during migrating to the new wildfly version with several EJB2.1 components. As I know there is no offical statement EJB2.1 BMP Beans are not supported anymore?! > Thanks and best regards > Marco -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016