March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-659) SFSB throws exception with second passivation

by Ben Wang (JIRA)

SFSB throws exception with second passivation --------------------------------------------- Key: EJBTHREE-659 URL: http://jira.jboss.com/jira/browse/EJBTHREE-659 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Ben Wang Assigned To: Ben Wang Fix For: EJB 3.0 RC9 - FD I have created a test case to illustrate this for both SimpleStatefulCache and StatefulTreeCache, NestedBeanUnitTestCase (cache and clusteredsession). Basically, if we do this: bean.getXXX sleep(10000); // to passivate bean.getXXX; // to acitvate sleep(10000); // to passivate again This will produce: 2006-07-24 04:46:59,358 ERROR [org.jboss.ejb3.cache.simple.SimpleStatefulCache] problem passivation thread^M javax.ejb.EJBException: Could not passivate; failed to save state^M at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:363)^M at org.jboss.ejb3.cache.simple.SimpleStatefulCache.passivate(SimpleStatefulCache.java:196)^M at org.jboss.ejb3.cache.simple.SimpleStatefulCache$SessionTimeoutTask.run(SimpleStatefulCache.java:129)^M Caused by: java.lang.NullPointerException^M at org.jboss.serial.util.StringUtil.calculateUTFSize(StringUtil.java:319)^M at org.jboss.serial.util.StringUtil.saveString(StringUtil.java:63)^M at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeUTF(DataContainer.java:265)^M at org.jboss.ejb3.stateful.StatefulBeanContextReference.writeExternal(StatefulBeanContextReference.java:65)^M at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58)^M at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275)^M at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:197)^M at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181)^M at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:287)^M at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:347)^M ... 2 more^M This is caused by a bug from ProxiedStatefuleBeanContext serialization where we dont serialiaze parentRef if it is not null. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-660) Nested sfsb passivation notification is incorrect

by Ben Wang (JIRA)

Nested sfsb passivation notification is incorrect ------------------------------------------------- Key: EJBTHREE-660 URL: http://jira.jboss.com/jira/browse/EJBTHREE-660 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Ben Wang Assigned To: Ben Wang Fix For: EJB 3.0 RC9 - FD Current sfsb activation/passivation notification relies on read/writeExternal. This is semnatically not correct since replication also relies on serialization. So each replication would trigger a activation/passivation pair. I don't believe ejb3 specifies specifically activation/passivation to serialization (there is no word on how to perform passivation actually). So a better way is to decouple this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-650) javax.ejb.SessionContext.getInvokedBusinessInterface() has wrong return type

by Carlo de Wolf (JIRA)

javax.ejb.SessionContext.getInvokedBusinessInterface() has wrong return type ---------------------------------------------------------------------------- Key: EJBTHREE-650 URL: http://jira.jboss.com/jira/browse/EJBTHREE-650 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Carlo de Wolf javax.ejb.SessionContext.getInvokedBusinessInterface() must return Class not Object. See http://java.sun.com/javaee/5/docs/api/javax/ejb/SessionContext.html#getIn... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

2
3
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-630) EJB timers not persisted upon undeployment

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-630?page=all ] Carlo de Wolf closed EJBTHREE-630. ---------------------------------- > EJB timers not persisted upon undeployment > ------------------------------------------ > > Key: EJBTHREE-630 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-630 > Project: EJB 3.0 > Issue Type: Task > Reporter: Dimitris Andreadis > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > > Since jboss 4.0.4.GA (see JBAS-1091) ejb timers can be persisted at undeployment time. > However, this was a feature added to the org.jboss.ejb.txtimer.EJBTimerService API with a second removeTimerService method: > /** > * Remove the TimerService for a given containerId. > * > * This should be used to remove the timer service and timers for > * any type of container (session, entity, message) at the time of > * undeployment. > * > * @param containerId The string identifier for a class of TimedObjects > * @param keepState Flag indicating whether timer persistent state should be kept or removed > */ > void removeTimerService(ObjectName containerId, boolean keepState) throws IllegalStateException; > EJB3 uses the old removeTimerService() method that has the legacy behaviour of removing the timers at undeployment time. > void removeTimerService(ObjectName containerId, Object pKey) throws IllegalStateException; > So, call the new method instead. However, this will mean the EJB3 bundle will only run on JBoss4.0.4+ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-620) Spec for @EJB calls for beanInterface not businessInterface

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-620?page=all ] Carlo de Wolf closed EJBTHREE-620. ---------------------------------- > Spec for @EJB calls for beanInterface not businessInterface > ----------------------------------------------------------- > > Key: EJBTHREE-620 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-620 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC8 - FD > Reporter: STV Consultants > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > Current HEAD revision for @EJB appears to be in conflict with the spec. > says: > http://fisheye.labs.jboss.com/viewrep/JBoss/jboss-ejb3x/src/main/javax/ej... > Class businessInterface() default java.lang.Object.class; > should say: > Class beanInterface() default java.lang.Object.class; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-626) Error while booting EJB3StandaloneBootstrap if config file are in another folder than root

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-626?page=all ] Carlo de Wolf closed EJBTHREE-626. ---------------------------------- > Error while booting EJB3StandaloneBootstrap if config file are in another folder than root > ------------------------------------------------------------------------------------------ > > Key: EJBTHREE-626 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-626 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC8 - FD > Environment: not relevant > Reporter: Christian Lischnig > Assigned To: Carlo de Wolf > Priority: Minor > Fix For: EJB 3.0 RC9 - FD > > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > In the boot(String configPath) method of the EJB3StandaloneBootstrap class following line: > URL ejb3_interceptors = Thread.currentThread().getContextClassLoader().getResource("ejb3-interceptors-aop.xml"); > should be change to > URL ejb3_interceptors = Thread.currentThread().getContextClassLoader().getResource(basePath + "ejb3-interceptors-aop.xml"); > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-613) Support for getTimerService in ServiceContainer for MBeans

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-613?page=all ] Carlo de Wolf closed EJBTHREE-613. ---------------------------------- > Support for getTimerService in ServiceContainer for MBeans > ---------------------------------------------------------- > > Key: EJBTHREE-613 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-613 > Project: EJB 3.0 > Issue Type: Feature Request > Components: EJB3 Extensions > Affects Versions: EJB 3.0 RC7 - FD > Reporter: mtuckah > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > > The ServiceContainer currently does not support the getTimerService() method. This would be a useful feature for scheduled Service POJO method invocation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-619) Build EJB Timer Service on top of Quartz

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-619?page=all ] Carlo de Wolf closed EJBTHREE-619. ---------------------------------- > Build EJB Timer Service on top of Quartz > ---------------------------------------- > > Key: EJBTHREE-619 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-619 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Carlo de Wolf > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-580) Test out failover passivation under JBC

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-580?page=all ] Carlo de Wolf closed EJBTHREE-580. ---------------------------------- > Test out failover passivation under JBC > --------------------------------------- > > Key: EJBTHREE-580 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-580 > Project: EJB 3.0 > Issue Type: Sub-task > Components: Clustering > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: EJB 3.0 RC9 - FD > > > In PassivationUnitTestCase, we need to add a test case that test the passivation with failover case. And if it fails, fix it accordingly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-606) lifecycle methods not called for embedded Service beans

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-606?page=all ] Carlo de Wolf closed EJBTHREE-606. ---------------------------------- > lifecycle methods not called for embedded Service beans > ------------------------------------------------------- > > Key: EJBTHREE-606 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-606 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC6 - PFD > Reporter: William DeCoste > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

1
0
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 March 2007