January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8020) Complete Site and Documentation for AS6 Weld

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 Weld -------------------------------------------- Key: JBAS-8020 URL: https://jira.jboss.org/jira/browse/JBAS-8020 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert -- 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, 9 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-8656) TimerService broken in AS600CR1

by Vitaliy Abramov (JIRA)

TimerService broken in AS600CR1 ------------------------------- Key: JBAS-8656 URL: https://jira.jboss.org/browse/JBAS-8656 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Scheduling/Timers Affects Versions: 6.0.0.CR1 Environment: Java 1.6_20 Windows, Linux Reporter: Vitaliy Abramov Assignee: Dimitris Andreadis TimerService started by Schedule annotation not working correctly. In 6.0.0.M5 everything works as expected, in 6.0.0.CR1 timer callback called five times in a row every minute. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (JBAS-8114) Automatically set EJB timeout greater than session timeout if CDI is enabled

by Shane Bryzak (JIRA)

Automatically set EJB timeout greater than session timeout if CDI is enabled ---------------------------------------------------------------------------- Key: JBAS-8114 URL: https://jira.jboss.org/browse/JBAS-8114 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M3 Reporter: Shane Bryzak Assignee: Pete Muir The EJB timeout (for SFSBs) should automatically be set to be longer than the session timeout, if CDI/Weld is enabled . Otherwise we can get exceptions such as the following, if a SFSB times out before the session ends: javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-kry0ga-gaj04tmw-1-gal0kea7-ek org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:479) org.jboss.ejb3.cache.simple.SimpleStatefulCache.get(SimpleStatefulCache.java:430) org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:59) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:193) org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:109) org.jboss.ejb3.nointerface.impl.invocationhandler.NoInterfaceViewInvocationHandler.invoke(NoInterfaceViewInvocationHandler.java:148) org.jboss.ejb3.proxy.javassist.JavassistInvocationHandlerAdapter.invoke(JavassistInvocationHandlerAdapter.java:71) org.jboss.weld.examples.pastecode.session.History_$$_javassist_737.search(History_$$_javassist_737.java) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:304) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:298) org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127) org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43) org.jboss.weld.examples.pastecode.session.History_$$_javassist_724.search(History_$$_javassist_724.java) sun.reflect.GeneratedMethodAccessor2070.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:304) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:298) org.jboss.weld.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:113) org.jboss.weld.util.CleanableMethodHandler.invoke(CleanableMethodHandler.java:43) org.jboss.weld.examples.pastecode.session.History_$$_javassist_735.search(History_$$_javassist_735.java) sun.reflect.GeneratedMethodAccessor2069.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.el.parser.AstValue.invoke(AstValue.java:196) org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:72) org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:72) com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:98) com.sun.faces.facelets.tag.jsf.core.DeclarativeSystemEventListener.processEvent(EventHandler.java:118) javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2345) javax.faces.event.SystemEvent.processListener(SystemEvent.java:102) com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:1993) com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:1941) com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:285) com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:243) org.jboss.weld.integration.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:336) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:114) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:417) -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8476) Embed tattletale to help diagnose classpath/classloading issues

by Baptiste MATHUS (JIRA)

Embed tattletale to help diagnose classpath/classloading issues --------------------------------------------------------------- Key: JBAS-8476 URL: https://jira.jboss.org/browse/JBAS-8476 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.1.0.GA Reporter: Baptiste MATHUS Assignee: Scott Stark Trying to migrate a working tomcat application to JBoss AS, I'm having a hard-time finding where the classes come/get loaded from. I just discovered JBAS-3180 and thought it would be great to have a standard servlet or something that would help have insights about some deployed webapp. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8715) classloader leak test failure in IsolatedEjb3EarClassloaderLeakTestCase

by Scott Marlow (JIRA)

classloader leak test failure in IsolatedEjb3EarClassloaderLeakTestCase ----------------------------------------------------------------------- Key: JBAS-8715 URL: https://jira.jboss.org/browse/JBAS-8715 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott Marlow Assignee: Andrew Rubinger Fix For: 6.0.0.Final Example of failure is on https://hudson.jboss.org/hudson/job/JBoss-AS-6.0.x-classloader-leak-x86_6... To reproduce with AS6 build: 1. Setup virtual ip addresses (for the clustering part of the test) su /sbin/ip addr add 172.19.1.2/32 dev eth0 /sbin/ip addr add 172.19.1.3/32 dev eth0 2. build as and cd into testsuite folder ./build.sh ./build.sh tests-all-classloader-leak -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8099) Lazy-load JSF configurations in JSF Deployer

by Stan Silvert (JIRA)

Lazy-load JSF configurations in JSF Deployer -------------------------------------------- Key: JBAS-8099 URL: https://jira.jboss.org/browse/JBAS-8099 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JSF Affects Versions: 6.0.0.M4 Reporter: Stan Silvert Assignee: Stan Silvert Priority: Minor The JSF configurations/implementations are loaded at startup by the JSF Deployer. This could improve startup a tiny bit if each were loaded on demand. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8332) Cannot add deploy directory on Windows network share

by James Livingston (JIRA)

Cannot add deploy directory on Windows network share ---------------------------------------------------- Key: JBAS-8332 URL: https://jira.jboss.org/browse/JBAS-8332 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA Environment: Windows Reporter: James Livingston Assignee: Remy Maucherat Fix For: TBD Adding a new deployment directory on a UNC path (i.e. Windows file share) does not work. TomcatDeployment currently converts the url in String form to a path by using new URL(stringUrl).getPath(), rather than simply chopping off the leading file:, and this causes problems with deployments accessed via Windows UNC paths because of the URL classes bad handling of those. The issue can also be fixed by solving JBVFS-160 so the URL string gets generated with extra slashes. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8249) CDI Extensions must be added to DU's classloader through an integration deployer

by Marius Bogoevici (JIRA)

CDI Extensions must be added to DU's classloader through an integration deployer --------------------------------------------------------------------------------- Key: JBAS-8249 URL: https://jira.jboss.org/browse/JBAS-8249 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M4 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 6.0.0.Final CDI integration features of the various JBoss components may use portable extensions for interacting with the CDI container. Wherever that is the case, make sure that the jars containing the extensions are added to deployment unit's classloader and not to the deployer's classloader (the default), as they should effectively become parts of the application that is being deployed. Also, splitting the application classes between deployers and deployment unit doesn't work with Weld 1.1's proxification mechanism. -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8705) javax.servlet.ServletException: java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/LoopTag

by David Thompson (JIRA)

javax.servlet.ServletException: java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/LoopTag ---------------------------------------------------------------------------------------------------- Key: JBAS-8705 URL: https://jira.jboss.org/browse/JBAS-8705 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: 6.0.0.CR1 Environment: Ubuntu 10.10, jboss-6.0.0.CR1, jbossweb-standalone Reporter: David Thompson Assignee: Scott Stark Started up jboss 6 CR1 in jbossweb-standalone (after some tweaking--needing jbas-8659-jboss-beans.xml) and got a working server up and running. Deployed a struts 1.3 WAR. Application deploys. When accessing a page with a c:forEach tag in it, the NoClassDefFoundError is thrown. We have jstl-1.1.2.jar within WEB-INF/lib (verified by listing the war libs below). WEB-INF/lib/cachetag.jar WEB-INF/lib/commons-beanutils-1.8.0.jar WEB-INF/lib/commons-chain-1.2.jar WEB-INF/lib/commons-digester-1.8.jar WEB-INF/lib/commons-validator-1.3.1.jar WEB-INF/lib/jakarta-oro.jar WEB-INF/lib/jstl-1.1.2.jar WEB-INF/lib/standard-1.0.6.jar WEB-INF/lib/struts-core-1.3.10.jar WEB-INF/lib/struts-el-1.3.10.jar WEB-INF/lib/struts-extras-1.3.10.jar WEB-INF/lib/struts-taglib-1.3.10.jar If I put the jstl-1.1.2.jar in jbossweb-standalon/lib, restart the server and run the application, then the error doesn't happen. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (JBWEB-172) Improve Usability of Error Message During Failed Injection

by Andrew Lee Rubinger (JIRA)

Improve Usability of Error Message During Failed Injection ---------------------------------------------------------- Key: JBWEB-172 URL: https://jira.jboss.org/browse/JBWEB-172 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assignee: Remy Maucherat Consider the following error trace in JBossAS 6.0.0.M3: 14:50:09,467 ERROR [org.jboss.web.tomcat.service.deployers.TomcatDeployment] ENC setup failed: java.lang.IllegalStateException: Resolution should not happen via injection container at org.jboss.web.tomcat.service.TomcatInjectionContainer.getEjbJndiName(TomcatInjectionContainer.java:683) [:6.0.0.20100429-M3] at org.jboss.injection.EjbEncInjector.inject(EjbEncInjector.java:80) [:1.3.1] at org.jboss.web.tomcat.service.TomcatInjectionContainer.populateEnc(TomcatInjectionContainer.java:507) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:448) [:6.0.0.20100429-M3] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [:6.0.0.20100429-M3] at org.apache.catalina.core.StandardContext.start(StandardContext.java:4192) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:323) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:148) [:6.0.0.20100429-M3] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:462) [:6.0.0.20100429-M3] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:116) [:6.0.0.20100429-M3] at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.20100429-M3] This occurs when attempting to inject an unknown type. Recommend a more user-friendly message detailing the type of field requested, as well as its name and class located. -- 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, 9 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011