October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7326) fix org.jboss.test.web.test.WebProgrammaticLoginTestCase(tomcat-sso).testSuccessfulLogin

by Dimitris Andreadis (JIRA)

fix org.jboss.test.web.test.WebProgrammaticLoginTestCase(tomcat-sso).testSuccessfulLogin ---------------------------------------------------------------------------------------- Key: JBAS-7326 URL: https://jira.jboss.org/jira/browse/JBAS-7326 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security, Test Suite Reporter: Dimitris Andreadis Assignee: Anil Saldhana Fix For: JBossAS-5.2.0.Beta1 I think this test started failing when JBAS-7311 was introduced. http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.x-testSu... -- 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, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBREFLECT-64) ConcurrentModificationException on JBossClDelegatingClassPoolFactory

by Flavia Rainone (JIRA)

ConcurrentModificationException on JBossClDelegatingClassPoolFactory -------------------------------------------------------------------- Key: JBREFLECT-64 URL: https://jira.jboss.org/jira/browse/JBREFLECT-64 Project: JBoss Reflection Issue Type: Bug Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0-Beta1 Fix the concurrent modification exception: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:841) at java.util.HashMap$KeyIterator.next(HashMap.java:877) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) at org.jboss.classpool.plugins.as5.jbosscl.JBossClDelegatingClassPoolFactory.registerBootstrapLoaders(JBossClDelegatingClassPoolFactory.java:146) at org.jboss.classpool.plugins.as5.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:76) at org.jboss.classpool.plugins.as5.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:52) at javassist.scopedpool.ScopedClassPoolRepositoryImpl.createScopedClassPool(ScopedClassPoolRepositoryImpl.java:99) at javassist.scopedpool.ScopedClassPoolRepositoryImpl.registerClassLoader(ScopedClassPoolRepositoryImpl.java:125) at org.jboss.classpool.spi.ClassPoolRepository.registerClassLoader(ClassPoolRepository.java:167) at org.jboss.reflect.plugins.javassist.classpool.RepositoryClassPoolFactory.getPoolForLoader(RepositoryClassPoolFactory.java:53) at org.jboss.reflect.plugins.javassist.JavassistTypeInfoFactoryImpl.get(JavassistTypeInfoFactoryImpl.java:269) at org.jboss.reflect.plugins.javassist.JavassistTypeInfoFactoryImpl.get(JavassistTypeInfoFactoryImpl.java:294) at org.jboss.reflect.plugins.javassist.JavassistTypeInfoFactoryImpl.getTypeInfo(JavassistTypeInfoFactoryImpl.java:469) at org.jboss.reflect.plugins.javassist.JavassistTypeInfoFactoryImpl.getTypeInfo(JavassistTypeInfoFactoryImpl.java:501) at org.jboss.reflect.plugins.javassist.JavassistTypeInfoFactory.getTypeInfo(JavassistTypeInfoFactory.java:56) at org.jboss.test.deployers.vfs.classpool.test.ClassPoolTest.assertClassPool(ClassPoolTest.java:80) at org.jboss.test.deployers.vfs.classpool.test.ClassPoolTestCase.testBasicEar(ClassPoolTestCase.java:83) -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-114) Move api-embedded and impl-embedded out and back into EMB project

by Andrew Lee Rubinger (JIRA)

Move api-embedded and impl-embedded out and back into EMB project ----------------------------------------------------------------- Key: JBBOOT-114 URL: https://jira.jboss.org/jira/browse/JBBOOT-114 Project: JBoss Bootstrap Issue Type: Task Components: api-embedded, impl-embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Remove these components from the Bootstrap project. @see linked issue for definition and discussion on forum. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1926) EJBTimer Restart Issue : Dropped/Failed Timer Execution

by Kyle S. Bober (JIRA)

EJBTimer Restart Issue : Dropped/Failed Timer Execution ------------------------------------------------------- Key: EJBTHREE-1926 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1926 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Affects Versions: 1.1.15 Environment: JBoss 5.1.0.GA Reporter: Kyle S. Bober Priority: Critical Here is the situation: I launch a series of EJBTimers that are scheduled to run in the future. I shut down JBoss and restart the server. Upon Jboss restart I notice a good portion of the EJBTimer(s) which were scheduled to execute fail on JBoss restart. This is what I see in the log: 10:02:35,250 ERROR [TimerImpl] Error invoking ejbTimeout org.jboss.aop.DispatcherConnectException: EJB container is not completely started, or is stopped. at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:6 2) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterce ptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateless.StatelessContainer.callTimeout(StatelessContainer.java:249) at org.jboss.as.ejb3.timerservice.TimedObjectInvokerBridge.callTimeout(TimedObjectInvokerBridge.jav a:44) at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run(TimerImpl.java:561) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Looking at the stacktrace it appears that the timer is triggered even before the EJB container is probably completely started. The unfortunate thing about this is that a good portion of the EJBTimer(s) that were schedule to execute are never executed and are removed from the Timers Table. Yet some of the EJBTimer(s) are successfully kicked of and executed properly. I will provided a sample application to reproduce this issue in the near future. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1936) Track release of plugin 1.0.16

by jaikiran pai (JIRA)

Track release of plugin 1.0.16 ------------------------------ Key: EJBTHREE-1936 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1936 Project: EJB 3.0 Issue Type: Task Components: plugin Reporter: jaikiran pai Assignee: jaikiran pai Track the release of EJB3 plugin 1.0.16 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Deleted: (JBPORTAL-2461) Session scoped Seam component calls PortalIdentity.instance().getPrincipal() which returns null.

by Gary Hu (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-2461?page=com.atlassian.jira.... ] Gary Hu deleted JBPORTAL-2461: ------------------------------ > Session scoped Seam component calls PortalIdentity.instance().getPrincipal() which returns null. > ------------------------------------------------------------------------------------------------ > > Key: JBPORTAL-2461 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-2461 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gary Hu > > In a session scoped Seam component the following call returns null value: > PortalIdentity.instance().getPrincipal(); > The further investigation shows that the above call is dependent upon the availability of FacesContext. However, FacesContext.getCurrentInstance() returns null in this case. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7394) org.jboss.metadata.ear.jboss.JBossAppMetaData

by Shelly McGowan (JIRA)

org.jboss.metadata.ear.jboss.JBossAppMetaData --------------------------------------------- Key: JBAS-7394 URL: https://jira.jboss.org/jira/browse/JBAS-7394 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2461) Session scoped Seam component calls PortalIdentity.instance().getPrincipal() which returns null.

by Gary Hu (JIRA)

Session scoped Seam component calls PortalIdentity.instance().getPrincipal() which returns null. ------------------------------------------------------------------------------------------------ Key: JBPORTAL-2461 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2461 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gary Hu In a session scoped Seam component the following call returns null value: PortalIdentity.instance().getPrincipal(); The further investigation shows that the above call is dependent upon the availability of FacesContext. However, FacesContext.getCurrentInstance() returns null in this case. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMAN-49) Add a java.io.File MetaMapper implementation

by Scott M Stark (JIRA)

Add a java.io.File MetaMapper implementation -------------------------------------------- Key: JBMAN-49 URL: https://jira.jboss.org/jira/browse/JBMAN-49 Project: JBoss Managed Issue Type: Feature Request Affects Versions: JBossMan.2.0.0.GA Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossMan.2.0.1.CR1 It would be helpful to have a java.io.File MetaMapper implementation since the File type is not serializable and generally should just be a string. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7386) javax.faces

by Shelly McGowan (JIRA)

javax.faces ----------- Key: JBAS-7386 URL: https://jira.jboss.org/jira/browse/JBAS-7386 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JSF Reporter: Shelly McGowan Assignee: Stan Silvert Fix For: JBossAS-5.2.0.GA Already Excluded: FAIL: serialVersionUID error for javax.faces.component.UIComponentBase$FacetsMap, 423 8609899080216831864, current: 4485903508811150216 FAIL: serialVersionUID error for javax.faces.model.ResultSetDataModel$ResultSetMap, 423 799240087409033268, current: -5368520859290297898 FAIL: serialVersionUID error for javax.faces.validator.ValidatorException, 423 4026308396973607, current: 2930547978354852546 New: FAIL: serialVersionUID error for javax.faces.FacesException, 510 -3553142415948858495, current: 6592152487577416317 FAIL: serialVersionUID error for javax.faces.application.FacesMessage, 510 -1180773928220076822, current: 4851488727794169661 FAIL: serialVersionUID error for javax.faces.convert.ConverterException, 510 3029059296191571679, current: 8668056061177480197 FAIL: serialVersionUID error for javax.faces.event.FacesEvent, 510 6326602303331494367, current: -3273926187856277200 FAIL: serialVersionUID error for javax.faces.event.PhaseEvent, 510 7603034985956521464, current: -7235692965954486239 FAIL: serialVersionUID error for javax.faces.event.ValueChangeEvent, 510 1678010455621487208, current: -2490528664421353795 FAIL: serialVersionUID error for javax.faces.model.DataModelEvent, 510 -1822980374964965366, current: 1823115573192262656 FAIL: serialVersionUID error for javax.faces.model.SelectItem, 510 876782311414654999, current: 8841094741464512226 FAIL: serialVersionUID error for javax.faces.model.SelectItemGroup, 510 8355957402275580167, current: 849845793056900213 FAIL: serialVersionUID error for javax.faces.webapp.AttributeTag, 510 -7782950243436672334, current: 3147657100171678632 FAIL: serialVersionUID error for javax.faces.webapp.ConverterELTag, 510 -1876768812840134640, current: -616834506829108081 FAIL: serialVersionUID error for javax.faces.webapp.ConverterTag, 510 -5909792518081427720, current: -6168345066829108081 FAIL: serialVersionUID error for javax.faces.webapp.FacetTag, 510 5019035861261307895, current: -5254277925259361302 FAIL: serialVersionUID error for javax.faces.webapp.ValidatorELTag, 510 -4373376368829344328, current: 8794036166323016663 FAIL: serialVersionUID error for javax.faces.webapp.ValidatorTag, 510 -5562623615418158868, current: 8794036166323016663 -- 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, 9 months

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 October 2009