April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1300) org.jboss.log4j.logmanager module needs a dependency on javax.mail.api

by James Perkins (JIRA)

James Perkins created WFLY-1300: ----------------------------------- Summary: org.jboss.log4j.logmanager module needs a dependency on javax.mail.api Key: WFLY-1300 URL: https://issues.jboss.org/browse/WFLY-1300 Project: WildFly Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 8.0.0.Alpha1 Some appenders, like SMTPAppender, require {{javax.mail.api}}. Should probably verify other appenders don't require other modules too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-976) Multi-JSF doesn't understand new modules structure

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s... ] Stan Silvert commented on WFLY-976: ----------------------------------- You should have nothing in your WEB-INF/lib. I see MyFaces and all the supporting jars. If you installed MyFaces into WildFly using install-myfaces-2.1.11.cli, then everything you need to run MyFaces exists under the server's /modules directory structure. > Multi-JSF doesn't understand new modules structure > -------------------------------------------------- > > Key: WFLY-976 > URL: https://issues.jboss.org/browse/WFLY-976 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Stan Silvert > Assignee: Stan Silvert > Attachments: install-myfaces-2.1.11.cli, Localization.war > > > With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default. > The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script. > See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-976) Multi-JSF doesn't understand new modules structure

by Glenn Kastrinos (JIRA)

[ https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s... ] Glenn Kastrinos edited comment on WFLY-976 at 4/29/13 5:40 PM: --------------------------------------------------------------- 17:30:57,015 INFO [org.apache.myfaces.config.DefaultFacesConfigurationProvider] (MSC service thread 1-1) Reading config : jar:file:/C:/wildfly-8.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/as/weld/main/jboss-as-weld-8.0.0.Alpha1-SNAPSHOT.jar!/META-INF/faces-config.xml 17:30:57,062 SEVERE [org.apache.myfaces.webapp.AbstractFacesInitializer] (MSC service thread 1-1) An error occured while initializing MyFaces: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory: java.lang.IllegalArgumentException: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder.newFactoryInstance(FactoryFinder.java:354) [myfaces-api-2.1.11.jar:2.1.11] at javax.faces.FactoryFinder._getFactory(FactoryFinder.java:317) [myfaces-api-2.1.11.jar:2.1.11] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:206) [myfaces-api-2.1.11.jar:2.1.11] at org.apache.myfaces.config.FacesConfigurator.configureApplication(FacesConfigurator.java:510) [myfaces-impl-2.1.11.jar:2.1.11] was (Author: glennk): 17:33:28,859 SEVERE [org.apache.myfaces.webapp.AbstractFacesInitializer] (MSC service thread 1-2) An error occured while initializing MyFaces: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory: java.lang.IllegalArgumentException: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory > Multi-JSF doesn't understand new modules structure > -------------------------------------------------- > > Key: WFLY-976 > URL: https://issues.jboss.org/browse/WFLY-976 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Stan Silvert > Assignee: Stan Silvert > Attachments: install-myfaces-2.1.11.cli, Localization.war > > > With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default. > The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script. > See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-976) Multi-JSF doesn't understand new modules structure

by Glenn Kastrinos (JIRA)

[ https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s... ] Glenn Kastrinos commented on WFLY-976: -------------------------------------- Hey, I appreciate all of your help. I followed all of your steps, but no matter what config I use, I eventualy always make it back to: 17:33:28,859 SEVERE [org.apache.myfaces.webapp.AbstractFacesInitializer] (MSC service thread 1-2) An error occured while initializing MyFaces: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory: java.lang.IllegalArgumentException: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory which occurs in the myfaces jars (whether I use the bundle or the impl/api jars). At your convenience, I can answer more about my configuration, but I just cannot figure out why it keeps throwing that error. I've attached my .war file. Is it obvious? Thank you yet again > Multi-JSF doesn't understand new modules structure > -------------------------------------------------- > > Key: WFLY-976 > URL: https://issues.jboss.org/browse/WFLY-976 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Stan Silvert > Assignee: Stan Silvert > Attachments: install-myfaces-2.1.11.cli, Localization.war > > > With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default. > The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script. > See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-976) Multi-JSF doesn't understand new modules structure

by Glenn Kastrinos (JIRA)

[ https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s... ] Glenn Kastrinos updated WFLY-976: --------------------------------- Attachment: Localization.war 17:33:28,859 SEVERE [org.apache.myfaces.webapp.AbstractFacesInitializer] (MSC service thread 1-2) An error occured while initializing MyFaces: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory: java.lang.IllegalArgumentException: Class org.jboss.as.weld.webtier.jsf.WeldApplicationFactory is no javax.faces.application.ApplicationFactory > Multi-JSF doesn't understand new modules structure > -------------------------------------------------- > > Key: WFLY-976 > URL: https://issues.jboss.org/browse/WFLY-976 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Stan Silvert > Assignee: Stan Silvert > Attachments: install-myfaces-2.1.11.cli, Localization.war > > > With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default. > The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script. > See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1299) AS 7 managed container: Different source and work dir (copy AS for each config)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-1299?page=com.atlassian.jira.plugin.... ] Ondrej Zizka commented on WFLY-1299: ------------------------------------ {quote} We have implemented this concept in RichFaces 5, but we need to install just one instance of the container (BeforeSuite/AfterSuite), you will need to solve a problem of multiple instances: https://github.com/richfaces/richfaces5/blob/master/build/build-resources... We resolve the server as a Maven artifact using ShrinkWrap descriptor - which gives us caching of browser binary for free in local M2 repo. We also use prepared ZIP overlays with configuration [1] or you can use kind of ShrinkWrap Descriptors type of API in order to configure the container as needed in ConfigureContainer phase. ~ Lukas [1] https://github.com/richfaces/richfaces5/tree/master/build/build-resources... {quote} > AS 7 managed container: Different source and work dir (copy AS for each config) > ------------------------------------------------------------------------------- > > Key: WFLY-1299 > URL: https://issues.jboss.org/browse/WFLY-1299 > Project: WildFly > Issue Type: Feature Request > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > In my project (AS config migration), I need to keep the results of every config I run with (one per test). > This could be handled in Maven or Ant by creating copies in advance. > But much more ellegant would be to use [multiple containers|https://docs.jboss.org/author/display/ARQ/Multiple+Containers] and to let Arq copy some source dir and run AS from there. > For this purpose, I propose to add a config property {{jbossAsDist}} and copy it to {{jbossHome}} before launching it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-967) ClassLoader memory leak with JSF

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/WFLY-967?page=com.atlassian.jira.plugin.s... ] Stan Silvert commented on WFLY-967: ----------------------------------- 7.2.0.Final doesn't use Undertow, so that's why you don't see UNDERTOW-42. I'm going to have to do some more digging to figure out why it takes 30 minutes for these instances to go away. > ClassLoader memory leak with JSF > -------------------------------- > > Key: WFLY-967 > URL: https://issues.jboss.org/browse/WFLY-967 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Vlad Arkhipov > Assignee: Stan Silvert > Priority: Critical > Attachments: war-leak.tar.gz > > > JSF application's classes are not unloaded properly when undeployed. The test case is in the attachment. Steps to reproduce: > # mvn package > # deploy war-leak.war > # open http://localhost:8080/war-leak > # undeploy war-leak.war > # analyze a heap dump to find unloaded ModuleClassLoader of war-leak.war > References to the WAR classes are hold by java.beans.Introspector caches. It seems to be a known bug (feature?). For example Tomcat automatically invokes java.beans.Introspector.flushCaches() when WAR undeploys. There is also IntrospectorCleanupListener in Spring for the same purpose. > http://wiki.apache.org/commons/Logging/UndeployMemoryLeak > http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1299) AS 7 managed container: Different source and work dir (copy AS for each config)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/WFLY-1299?page=com.atlassian.jira.plugin.... ] Ondrej Zizka reassigned WFLY-1299: ---------------------------------- Assignee: Ondrej Zizka > AS 7 managed container: Different source and work dir (copy AS for each config) > ------------------------------------------------------------------------------- > > Key: WFLY-1299 > URL: https://issues.jboss.org/browse/WFLY-1299 > Project: WildFly > Issue Type: Feature Request > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > In my project (AS config migration), I need to keep the results of every config I run with (one per test). > This could be handled in Maven or Ant by creating copies in advance. > But much more ellegant would be to use [multiple containers|https://docs.jboss.org/author/display/ARQ/Multiple+Containers] and to let Arq copy some source dir and run AS from there. > For this purpose, I propose to add a config property {{jbossAsDist}} and copy it to {{jbossHome}} before launching it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1030) Add statistics for free threads

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1030?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1030: ----------------------------------- Summary: Add statistics for free threads (was: Add statistic for free threads) Fix Version/s: 1.1.0.Beta5 Component/s: Core > Add statistics for free threads > ------------------------------- > > Key: JBJCA-1030 > URL: https://issues.jboss.org/browse/JBJCA-1030 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 1.1.0.Beta5 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-275) pooled-connection-factory's inbound-config is not persisted

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-275?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-275: ---------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 900842|https://bugzilla.redhat.com/show_bug.cgi?id=900842] Verified in EAP 6.1.0.ER5. > pooled-connection-factory's inbound-config is not persisted > ----------------------------------------------------------- > > Key: WFLY-275 > URL: https://issues.jboss.org/browse/WFLY-275 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The code to persist pooled-connection-factory's inbound-config is not correct in MessagingXMLWriter (the pooled-connection-factory ModelNode layout does not have an intermediate inbound-config node): any changes to AS7 configuration will discard the <inbound-config> element from the persisted XML files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013