March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (EJBTHREE-579) Data eviction is not done correctly under JBC framework

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-579?page=all ] Carlo de Wolf closed EJBTHREE-579. ---------------------------------- > Data eviction is not done correctly under JBC framework > ------------------------------------------------------- > > Key: EJBTHREE-579 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-579 > Project: EJB 3.0 > Issue Type: Sub-task > Components: Clustering > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: EJB 3.0 RC9 - FD > > > Currently, the unit test clusteredsession/PassivationUnitTestCase fails becuase of the activation and passivation is called repeatedly. Turned out the data is not eivcted correctly by JBC. -- 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-603) Passivation failure for nested session bean

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-603?page=all ] Carlo de Wolf closed EJBTHREE-603. ---------------------------------- > Passivation failure for nested session bean > ------------------------------------------- > > Key: EJBTHREE-603 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-603 > Project: EJB 3.0 > Issue Type: Bug > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: EJB 3.0 RC9 - FD > > > I discovered this when I was writing more test cases for clustering sfsb. I have checked in the unit test case: org.jboss.ejb3.test.stateful.unit.NestedBeanTestCase. Basically, the passivation fails when there is a nested sfsb. -- 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-612) Nested bean during repeated failover throw NPE

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-612?page=all ] Carlo de Wolf closed EJBTHREE-612. ---------------------------------- > Nested bean during repeated failover throw NPE > ---------------------------------------------- > > Key: EJBTHREE-612 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-612 > Project: EJB 3.0 > Issue Type: Bug > Components: Clustering > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: EJB 3.0 RC9 - FD > > > I have encountered this during writing more complete unit testing for sfsb clustering. The test case is: > org.jboss.ejb3.test.clusteredsession.unit.testStatefulBeanCounterFailover > Here is how to reproduce it: > Create a ParentBean and NestedBean for nested sfsb case. Hit node1, failover to node2, and execute will produce the following exception: > Caused by: java.lang.NullPointerException^M > at org.jboss.ejb3.stateful.StatefulBeanContextReference.<init>(StatefulBeanContextReference.java:51)^M > at org.jboss.ejb3.stateful.ProxiedStatefulBeanContext.writeExternal(ProxiedStatefulBeanContext.java:92)^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.JBossObjectOutputStreamSharedTree.writeObjectOverride(JBossObjectOutputStreamSharedTree.java:59)^M > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:287)^M > at org.jboss.cache.marshall.EnhancedTreeCacheMarshaller.marshallObject(EnhancedTreeCacheMarshaller.java:258)^M > @ > Note that this error has already existed before any refactoring is in place. -- 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-400) Timer transaction warning problem

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-400?page=all ] Carlo de Wolf closed EJBTHREE-400. ---------------------------------- > Timer transaction warning problem > --------------------------------- > > Key: EJBTHREE-400 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-400 > Project: EJB 3.0 > Issue Type: Bug > Reporter: Bill Burke > 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-500) Use JBossCache passivation feature for clustered ejb3 SFSB

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-500?page=all ] Carlo de Wolf closed EJBTHREE-500. ---------------------------------- > Use JBossCache passivation feature for clustered ejb3 SFSB > ---------------------------------------------------------- > > Key: EJBTHREE-500 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-500 > Project: EJB 3.0 > Issue Type: Task > Components: Clustering > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: EJB 3.0 RC9 - FD > > Original Estimate: 1 week, 1 day > Time Spent: 1 week > Remaining Estimate: 1 day > > Currently the clustered sfsb uses its own passivation implmentation because JBossCache didn't offer that previously. However, now that it has this feature, we should refactor to use that. There is a corresonding Forum post for this discussion. -- 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-576) Added test case to validate extended persistence context under clustering

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-576?page=all ] Carlo de Wolf closed EJBTHREE-576. ---------------------------------- > Added test case to validate extended persistence context under clustering > ------------------------------------------------------------------------- > > Key: EJBTHREE-576 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-576 > Project: EJB 3.0 > Issue Type: Task > Components: Clustering > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: EJB 3.0 RC9 - FD > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > I have copied the longlived test case over to test out the extended persistence context on clustering under clusteredsession. -- 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-323) @Service + @Management doesn't work in embeddable environment

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-323?page=all ] Carlo de Wolf closed EJBTHREE-323. ---------------------------------- > @Service + @Management doesn't work in embeddable environment > ------------------------------------------------------------- > > Key: EJBTHREE-323 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-323 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: EJB 3.0 RC1, EJB 3.0 RC2, EJB 3.0 RC3 > Reporter: Bill Burke > Assigned To: Carlo de Wolf > Fix For: EJB 3.0 RC9 - FD > > > try to use JVM's MBeanServer. -- 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] Created: (JBREM-719) Fix spelling of ServerInvokerCallbackHandler.REMOTING_ACKNOWLEDGES_PUSH_CALLBACKS

by Ron Sigal (JIRA)

Fix spelling of ServerInvokerCallbackHandler.REMOTING_ACKNOWLEDGES_PUSH_CALLBACKS --------------------------------------------------------------------------------- Key: JBREM-719 URL: http://jira.jboss.com/jira/browse/JBREM-719 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) The value is "remotingAcknowledgesPushCallbackss" instead of "remotingAcknowledgesPushCallbacks". -- 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
1
0 / 0

[JBoss JIRA] Created: (JBRULES-726) Remove category option (does not delete rules)

by Michael Neale (JIRA)

Remove category option (does not delete rules) ---------------------------------------------- Key: JBRULES-726 URL: http://jira.jboss.com/jira/browse/JBRULES-726 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-151) Refactor DeploymentUnit to cleanup attachment usage

by Scott M Stark (JIRA)

Refactor DeploymentUnit to cleanup attachment usage --------------------------------------------------- Key: JBMICROCONT-151 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-151 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0 Beta3 The three levels of attachments, getPredeterminedManagedObjects(), getTransientManagedObjects(), and getTransientAttachments() are not being used properly. In particular managed objects that are part of the persistent view of the deployment are being mixed with non-persistent, non-managed attachments. This is due to an api on the DeploymentUnit that facilitates the separation. -- 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
2
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