November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Closed: (WELD-86) Perform profiling for performance hotspots

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-86?page=com.atlassian.jira.plugin.syst... ] Pete Muir closed WELD-86. ------------------------- Assignee: Pete Muir Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.CR1) Resolution: Done Martin and Stale have done an excellent job of this, and we have more than met targets. We are now showing performance as good as all other CDI impls at runtime, and additionally other frameworks in the same space. > Perform profiling for performance hotspots > ------------------------------------------ > > Key: WELD-86 > URL: https://jira.jboss.org/browse/WELD-86 > Project: Weld > Issue Type: Sub-task > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.0.Beta3 > > > Grouping issue for suspected performance hotspots -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (WELD-89) Performance hotspots

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-89?page=com.atlassian.jira.plugin.syst... ] Pete Muir closed WELD-89. ------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.CR1) Resolution: Done No none hotspots left. > Performance hotspots > -------------------- > > Key: WELD-89 > URL: https://jira.jboss.org/browse/WELD-89 > Project: Weld > Issue Type: Task > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.0.Beta3 > > > Grouping task for tracking performance hotspot related issues -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-757) @New beans are created for every managed bean

by Stuart Douglas (JIRA)

@New beans are created for every managed bean --------------------------------------------- Key: WELD-757 URL: https://jira.jboss.org/browse/WELD-757 Project: Weld Issue Type: Bug Reporter: Stuart Douglas @New beans should be created only if there is an injection point that they satisfy, at the moment we create an @New bean for every managed bean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-766) NullPointerException if bean reference can't be resolved

by Tom Fennelly (JIRA)

NullPointerException if bean reference can't be resolved -------------------------------------------------------- Key: WELD-766 URL: https://jira.jboss.org/browse/WELD-766 Project: Weld Issue Type: Bug Reporter: Tom Fennelly Get the following exception if the "resolvedBean" arg to BeanManagerImpl.getReference is null. java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:729) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:137) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:869) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-497) Check for null in BeanManager.getReference()

by Jozef Hartinger (JIRA)

Check for null in BeanManager.getReference() -------------------------------------------- Key: WELD-497 URL: https://jira.jboss.org/jira/browse/WELD-497 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.1.Final Reporter: Jozef Hartinger Assignee: Pete Muir Priority: Minor Fix For: 1.0.2.CR1 Weld currently throws the following exception if the "bean" parameter is null during getReference() invocation Caused by: java.lang.NullPointerException at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:810) An exception with self-explanatory message should be thrown instead. Also, check the other parameters for null values. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Updated: (WELD-30) Include instructions in ref guide and readme's on how to run examples with GlassFish

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-30?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-30: -------------------------- Assignee: Sahoo Sahoo (was: Roger Kitain) > Include instructions in ref guide and readme's on how to run examples with GlassFish > ------------------------------------------------------------------------------------ > > Key: WELD-30 > URL: https://jira.jboss.org/browse/WELD-30 > Project: Weld > Issue Type: Feature Request > Components: Examples, GlassFish Integration > Environment: GlassFish > Reporter: Roger Kitain > Assignee: Sahoo Sahoo > Priority: Critical > Fix For: TBC > > > JBoss runs WebBeans example applications with GlassFish. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-31: -------------------------- Assignee: Sahoo Sahoo (was: Roger Kitain) > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://jira.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Sahoo Sahoo > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-273) Add GlassFish targets to example POMs

by Pete Muir (JIRA)

Add GlassFish targets to example POMs ------------------------------------- Key: WELD-273 URL: https://jira.jboss.org/jira/browse/WELD-273 Project: Weld Issue Type: Feature Request Components: Examples, GlassFish Integration Reporter: Pete Muir Fix For: 1.0.1.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
7
0 / 0

[JBoss JIRA] Created: (WELD-570) Partial export of javasisst from Weld breaks other javasisst clients

by Harald Wellmann (JIRA)

Partial export of javasisst from Weld breaks other javasisst clients -------------------------------------------------------------------- Key: WELD-570 URL: https://jira.jboss.org/browse/WELD-570 Project: Weld Issue Type: Bug Components: OSGi support Affects Versions: 1.1.0.BETA1 Reporter: Harald Wellmann weld-osgi-bundle.jar (as used in Glassfish 3.0 and higher) still contains a buggy version of javasisst causing memory leaks. See WELD-453 and JASSIST-104. Even though Weld itself no longer uses the problematic javassist ProxyFactory, it is still the root cause for a memory leak occurring when HIbernate (or potentially any other Javassist client) is used on Glassfish. The problem exists in Glassfish 3.0.1 and also in the promoted build 3.1-b12 using a 1.1.0 prerelease of Weld, see https://glassfish.dev.java.net/issues/show_bug.cgi?id=12368 weld-osgi-bundle.jar contains a version of javassist which is almost but not fully private. There is a package export for javassist.util.proxy. When deploying a WAR on Glassfish containing Hibernate (3.5.3) and another copy of Javasisst required by Hibernate, then by parent classloader delegation Hibernate will end up using the javassist ProxyFactory from Weld, registering its proxies deep down in the container, and thus causing a memory leak with each redeployment of the WAR. Weld should either keep its included version of javassist fully private or import all of javasisst via Import-Package, relying on javasisst installed in a separate bundle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-758) @SessionBean name attribute usage results in WELD-000079

by Nicklas Karlsson (JIRA)

@SessionBean name attribute usage results in WELD-000079 -------------------------------------------------------- Key: WELD-758 URL: https://jira.jboss.org/browse/WELD-758 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.Beta2 Reporter: Nicklas Karlsson Using something like @Stateful(name="LTKKirjautumistoiminnot") results in WELD-000079 Could not find the EJB in JNDI: class fi.affecto.kake.kirjautuminen.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$C:$Java$AS$jboss-6$0$0-SNAPSHOT$server$default$deploy$KaKe$war"-SessionBean-Kirjautumistoiminnot_$$_WeldProxy with a stacktrace like org.jboss.weld.exceptions.CreationException: WELD-000079 Could not find the EJB in JNDI: class fi.affecto.kake.kirjautuminen.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$C:$Java$AS$jboss-6$0$0-SNAPSHOT$server$default$deploy$KaKe$war"-SessionBean-Kirjautumistoiminnot_$$_WeldProxy at org.jboss.weld.bean.SessionBean.create(SessionBean.java:344) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:117) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:669) at org.jboss.weld.bean.AbstractReceiverBean.getReceiver(AbstractReceiverBean.java:83) at org.jboss.weld.bean.ProducerMethod$1.produce(ProducerMethod.java:141) at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:360) at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:59) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:669) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:707) at fi.affecto.kake.sys.apu.BeanUtil.getInstance(BeanUtil.java:35) at fi.affecto.kake.sys.jsf.KaKePhaseListener.asetaMDCtiedot(KaKePhaseListener.java:51) at fi.affecto.kake.sys.jsf.KaKePhaseListener.beforePhase(KaKePhaseListener.java:30) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:224) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:95) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:107) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:308) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:63) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.RuntimeException: Error retreiving EJB from JNDI Kirjautumistoiminnot (SFSB); BeanClass: class fi.affecto.kake.kirjautuminen.Kirjautumistoiminnot; Local Business Interfaces: [Business interface: class fi.affecto.kake.kirjautuminen.Kirjautumistoiminnot] at org.jboss.weld.integration.ejb.JBossEjbServices.resolveEjb(JBossEjbServices.java:71) at org.jboss.weld.bean.SessionBean.createReference(SessionBean.java:452) at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.<init>(EnterpriseBeanProxyMethodHandler.java:76) at org.jboss.weld.bean.SessionBean.create(SessionBean.java:327) ... 41 more Caused by: javax.naming.NamingException: Could not dereference object [Root exception is java.lang.RuntimeException: Could not push the context jboss.j2ee:jar=LTK.war,name=Kirjautumistoiminnot,service=EJB3 from its current state **ERROR** to INSTALLED] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1508) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:824) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.weld.integration.ejb.JBossSessionObjectReference.<init>(JBossSessionObjectReference.java:44) at org.jboss.weld.integration.ejb.JBossEjbServices.resolveEjb(JBossEjbServices.java:67) ... 44 more Caused by: java.lang.RuntimeException: Could not push the context jboss.j2ee:jar=LTK.war,name=Kirjautumistoiminnot,service=EJB3 from its current state **ERROR** to INSTALLED at org.jboss.ejb3.nointerface.impl.view.factory.StatefulNoInterfaceViewFacade.createNoInterfaceView(StatefulNoInterfaceViewFacade.java:99) at org.jboss.ejb3.nointerface.impl.objectfactory.StatefulNoInterfaceViewObjectFactory.getObjectInstance(StatefulNoInterfaceViewObjectFactory.java:73) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1483) at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1500) ... 49 more Caused by: java.lang.UnsupportedOperationException: Cannot invoke set on unmodifiable wrapper. at org.jboss.dependency.spi.helpers.UnmodifiableControllerContext.setRequiredState(UnmodifiableControllerContext.java:149) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:936) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) at org.jboss.ejb3.nointerface.impl.view.factory.StatefulNoInterfaceViewFacade.createNoInterfaceView(StatefulNoInterfaceViewFacade.java:95) ... 53 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2010