June 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6196) HttpInvokerProxyHA doesn't have logic to prevent failover w/in a tx

by Brian Stansberry (JIRA)

HttpInvokerProxyHA doesn't have logic to prevent failover w/in a tx ------------------------------------------------------------------- Key: JBAS-6196 URL: https://jira.jboss.org/jira/browse/JBAS-6196 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.CR2 Reporter: Brian Stansberry -- 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

16 years, 1 month

1
6
0 / 0

[JBoss JIRA] Created: (JBAS-7977) Upgrade JGroups to 2.10 Final

by Brian Stansberry (JIRA)

Upgrade JGroups to 2.10 Final ----------------------------- Key: JBAS-7977 URL: https://jira.jboss.org/jira/browse/JBAS-7977 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M4 -- 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

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-8056) Extract core clustering infrastructure from AS cluster module

by Brian Stansberry (JIRA)

Extract core clustering infrastructure from AS cluster module ------------------------------------------------------------- Key: JBAS-8056 URL: https://jira.jboss.org/browse/JBAS-8056 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 6.0.0.M4 Create an ha-server-core project under projects/cluster and move the core stuff in the AS cluster module's org.jboss.ha.framework.server package to it. This includes: 1) JChannelFactory and related classes 2) ClusterPartition and related classes The purpose of this is to: A) Support instantiating the core services outside of the AS. B) Allow the core services to be consumed by ha-server-cache-jbc and ha-server-cache-infinispan for use in controlling session ownership. The AS cluster module will retain a couple subclasses of the core classes that support the @ManagementObject view. -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8085) Clean up jbossweb-cluster.aop

by Brian Stansberry (JIRA)

Clean up jbossweb-cluster.aop ----------------------------- Key: JBAS-8085 URL: https://jira.jboss.org/browse/JBAS-8085 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web Services Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 6.0.0.M4 We no longer support FIELD granularity web session replication, so jbossweb-cluster.aop needs some cleanup. 1) We still ship POJO Cache, and this artifact basically deploys the aspects needed for POJO Cache, nothing really specific to FIELD granularity web session replication. So I'll still deploy the aspects, but not build them in the tomcat module and not call them jbossweb-cluster.aop. 2) This jar contains nothing but a jboss-aop.xml file so there is no reason to package it as a jar, force inclusion of jboss-scanning.xml etc. It was a jar because in the past it contained classes; it no longer does. So, deploy/cluster/jbossweb-cluster.aop will become deploy/cluster/pojocache-aop.xml. Built out of the cluster/ module. -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7775) Default jsf 2.0 resource lookup fails if resources are present in jar in WEB-INF/lib

by Johan Kustermans (JIRA)

Default jsf 2.0 resource lookup fails if resources are present in jar in WEB-INF/lib ------------------------------------------------------------------------------------ Key: JBAS-7775 URL: https://jira.jboss.org/jira/browse/JBAS-7775 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-6.0.0.M2 Reporter: Johan Kustermans We have a JSF 2.0 composite component in WEBROOT/resources and at the same time a jar in WEB-INF/lib that has resources under the META-INF/resources directory. Then a nullpointer is thrown with the following stacktrace 2010-02-28 19:21:32,839 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost%2F127.0.0.1-8080-1) Error Rendering View[/homeLucene.xhtml]: java.lang.NullPointerException at org.apache.naming.resources.ProxyDirContext.listBindings(ProxyDirContext.java:714) at org.apache.catalina.core.ApplicationContext.listCollectionPaths(ApplicationContext.java:1397) at org.apache.catalina.core.ApplicationContext.getResourcePathsInternal(ApplicationContext.java:645) at org.apache.catalina.core.ApplicationContext.getResourcePaths(ApplicationContext.java:628) at org.apache.catalina.core.ApplicationContextFacade.getResourcePaths(ApplicationContextFacade.java:199) at com.sun.faces.context.ExternalContextImpl.getResourcePaths(ExternalContextImpl.java:480) at com.sun.faces.application.resource.WebappResourceHelper.findResource(WebappResourceHelper.java:191) at com.sun.faces.application.resource.ResourceManager.findResource(ResourceManager.java:384) at com.sun.faces.application.resource.ResourceManager.doLookup(ResourceManager.java:234) at com.sun.faces.application.resource.ResourceManager.findResource(ResourceManager.java:181) at com.sun.faces.application.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:140) at com.sun.faces.application.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:120) at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:91) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:878) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1620) at org.primefaces.renderkit.HeadRenderer.encodeBegin(HeadRenderer.java:42) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:823) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1611) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:380) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:273) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) The error is thrown in the listbindings-method of the ProxyDirContext at the line while (overlay.hasMore()) { Binding pair = overlay.next(); ... } because overlay = null. This part of the code is reached in this case because the presence of the kind of jar mentioned in the beginning of this issue description implies that the overlays member field of the ProxyDirContext is not-null. A simple check on overlay != null before executing the while loop seems sufficient to resolve the issue. -- 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

16 years, 1 month

9
31
0 / 0

[JBoss JIRA] Created: (JBAS-8074) Build script doesn't work

by Jesper Pedersen (JIRA)

Build script doesn't work ------------------------- Key: JBAS-8074 URL: https://jira.jboss.org/browse/JBAS-8074 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Jesper Pedersen Assignee: Paul Gier Priority: Critical Fix For: 6.0.0.M4 Doing cd AS6/build && ./build.sh doesn't compile the classes of the project anymore. Only the "install" part is done. -- 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

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2108) Extend the functionality of TimedObjectInvoker to allow for passing the timeout method and params on timeout callback

by jaikiran pai (JIRA)

Extend the functionality of TimedObjectInvoker to allow for passing the timeout method and params on timeout callback --------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2108 URL: https://jira.jboss.org/browse/EJBTHREE-2108 Project: EJB 3.0 Issue Type: Feature Request Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 TimedObjectInvoker is based on EJB3.0 spec which expected that there will be only one timeout method on a bean. Starting EJB3.1, there can be multiple methods on a bean which can act as timeout invocation methods, due to the autotimer (@Schedule, @Schedules feature). The TimedObjectInvoker's: void callTimeout(Timer timer) throws Exception; is no longer sufficient to identify the correct timeout method corresponding to the timer. There now needs to be a way wherein the timer service implementation can pass the information about the timeout method (which will be provided to the timer service implementation when the auto timers are being created). -- 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

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8083) Update aop.xml for changes in jboss-aop and jboss-classpools

by Kabir Khan (JIRA)

Update aop.xml for changes in jboss-aop and jboss-classpools ------------------------------------------------------------ Key: JBAS-8083 URL: https://jira.jboss.org/browse/JBAS-8083 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 6.0.0.M4 -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8079) Deployment failing with ClassNotFoundException: Empty class name '' is Main-Class attribute present in Manifest but not specified

by Darran Lofthouse (JIRA)

Deployment failing with ClassNotFoundException: Empty class name '' is Main-Class attribute present in Manifest but not specified --------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-8079 URL: https://jira.jboss.org/browse/JBAS-8079 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.M3 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 6.0.0.M4 Caused by: java.lang.ClassNotFoundException: Empty class name '' at org.jboss.classloader.plugins.ClassLoaderUtils.checkClassName(ClassLoaderUtils.java:52) at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:413) at java.lang.ClassLoader.loadClass(ClassLoader.java:250) at org.jboss.deployment.OptAnnotationMetaDataDeployer.processJBossClientMetaData(OptAnnotationMetaDataDeployer.java:115) at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:82) at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:177) ... 33 more -- 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

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2107) Refactor the containers to remove duplicated logic around timerservice creation, restore and suspend functionality

by jaikiran pai (JIRA)

Refactor the containers to remove duplicated logic around timerservice creation, restore and suspend functionality ------------------------------------------------------------------------------------------------------------------ Key: EJBTHREE-2107 URL: https://jira.jboss.org/browse/EJBTHREE-2107 Project: EJB 3.0 Issue Type: Task Components: core Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 Currently the containers have duplicated copy/paste code for timer service creation, restoration and suspension. All this can be extracted out in a separate abstract TimerServiceContainer to remove the duplication. The TimerServiceContainer will be aware that stateful beans do not support timerservice. -- 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

16 years, 1 month

1
1
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 June 2010