October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-763) Transaction rollback does not restore contents of collection of cached collections

by Nitzan Niv (JIRA)

Transaction rollback does not restore contents of collection of cached collections ---------------------------------------------------------------------------------- Key: JBCACHE-763 URL: http://jira.jboss.com/jira/browse/JBCACHE-763 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Nitzan Niv Assigned To: Manik Surtani In PojoCache, transaction rollback does not restore (by completely undoing modifications) the contents of a cached collection when the updated element is in itself a cached collection. 1. create 2 "data elements" in the cache which are Map instances. 2. create a "data elements container" in the cache which is a Map instance. 3. initalize the container with one data element. 4. in a transaction, replace the initial data element in the container with the other data element, and then rollback the transaction. After the rollback the element in the container is neither the new data element nor the old data element. It looks like the aopInstance reference in the internal CachedMapInterceptor is not restored by the rollback and contains null after it. -- 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, 7 months

3
10
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-534) Embeddable Container fails if javax.management.MBeanServerFactory is loaded from jboss-ejb3-all.jar

by Darren Hartford (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-534?page=comments#action_12345797 ] Darren Hartford commented on EJBTHREE-534: ------------------------------------------ Also experiencing this problem with both RC8 and RC9 when trying to do Surefire tests through Maven 2.0.4. > Embeddable Container fails if javax.management.MBeanServerFactory is loaded from jboss-ejb3-all.jar > --------------------------------------------------------------------------------------------------- > > Key: EJBTHREE-534 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-534 > Project: EJB 3.0 > Issue Type: Bug > Components: EJB3 Extensions > Affects Versions: EJB 3.0 RC6 - PFD > Environment: Windows XP, JDK 1.5.0 update 6 > Reporter: Matthias Germann > > It's not possible to deploy a stateless session Bean to the embeddable EJB 3.0 container if the "javax.manangement.MBeanServerFactory" class is loaded from jboss-ejb3-all.jar instead of sun's rt.jar. > The problem is that "javax.management.MBeanServerFactory" calls the getInstance() method of the "org.jboss.mx.server.ServerConfig" class to initialize a static member. This method fails because the "org.jboss.mx.server.JBossMXServerConfig" class is not included in jboss-ejb3-all.jar > See the following stack trace: > INFO 25-04 15:34:58,343 (MCKernelAbstraction.java:install:79) -installing bean: jboss.j2ee:jar=test-classes,name=SimpleStatelessServiceBean,service=EJB3 with dependencies: > INFO 25-04 15:34:58,750 (EJBContainer.java:start:558) -STARTED EJB: com.unisys.insieme.testing.junit.SimpleStatelessServiceBean ejbName: SimpleStatelessServiceBean > ERROR 25-04 15:34:58,875 (AbstractController.java:incrementState:350) -Error installing to Start: name=jboss.j2ee:jar=test-classes,name=SimpleStatelessServiceBean,service=EJB3 sta > te=Create > java.lang.ExceptionInInitializerError > at org.jboss.mx.util.MBeanServerLocator.locateJBoss(MBeanServerLocator.java:114) > at org.jboss.ejb3.EjbTimerUtil.getTimerService(EjbTimerUtil.java:46) > at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:81) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55) > at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:107) > at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) > at org.jboss.kernel.plugins.dependency.KernelControllerContextActions.dispatchJoinPoint(KernelControllerContextActions.java:100) > at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$LifecycleAction.installAction(KernelControllerContextActions.java:583) > at org.jboss.kernel.plugins.dependency.KernelControllerContextActions$KernelControllerContextAction.install(KernelControllerContextActions.java:175) > at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:593) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:346) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:438) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:379) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:225) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:151) > at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:79) > at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:73) > at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:86) > at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:437) > at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:484) > at org.jboss.ejb3.embedded.EJB3StandaloneDeployer.start(EJB3StandaloneDeployer.java:450) > at com.unisys.insieme.testing.environment.JBossBeanContainer.<init>(JBossBeanContainer.java:86) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) > at java.lang.reflect.Constructor.newInstance(Unknown Source) > at java.lang.Class.newInstance0(Unknown Source) > at java.lang.Class.newInstance(Unknown Source) > at com.unisys.insieme.testing.environment.BeanContainer.getInstance(BeanContainer.java:38) > at com.unisys.insieme.testing.junit.EjbTestCase.setUp(EjbTestCase.java:26) > at com.unisys.insieme.testing.junit.CustomerServiceBeanTest.setUp(CustomerServiceBeanTest.java:25) > at junit.framework.TestCase.runBare(TestCase.java:125) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(JUnitBattery.java:242) > at org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBattery.java:216) > at org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215) > at org.apache.maven.surefire.Surefire.run(Surefire.java:163) > at org.apache.maven.surefire.Surefire.run(Surefire.java:87) > at org.apache.maven.surefire.Surefire.run(Surefire.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.apache.maven.surefire.SurefireBooter.main(SurefireBooter.java:785) > Caused by: org.jboss.util.NestedRuntimeException: Cannot load class org.jboss.mx.server.JBossMXServerConfig; - nested throwable: (java.lang.ClassNotFoundException: org.jboss.mx.ser > ver.JBossMXServerConfig) > at org.jboss.util.Classes.instantiate(Classes.java:531) > at org.jboss.mx.server.ServerConfig.getInstance(ServerConfig.java:74) > at javax.management.MBeanServerFactory.<clinit>(MBeanServerFactory.java:79) > ... 59 more > Caused by: java.lang.ClassNotFoundException: org.jboss.mx.server.JBossMXServerConfig > at java.net.URLClassLoader$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at org.apache.maven.surefire.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:85) > at org.jboss.util.Classes.loadClass(Classes.java:631) > at org.jboss.util.Classes.loadClass(Classes.java:570) > at org.jboss.util.Classes.instantiate(Classes.java:527) > ... 61 more -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-107) Extract locks from TreeCache into LockingTable

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-107?page=all ] Manik Surtani updated JBCACHE-107: ---------------------------------- Fix Version/s: 2.1.0 (was: 2.0.0) Complexity: Medium > Extract locks from TreeCache into LockingTable > ---------------------------------------------- > > Key: JBCACHE-107 > URL: http://jira.jboss.com/jira/browse/JBCACHE-107 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.1.0 > > > Used by LockInterceptor and CreateIfNotExistsInterceptor -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAOP-82) Generic ProxyAdvisor

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-82?page=all ] Kabir Khan resolved JBAOP-82. ----------------------------- Resolution: Done Assignee: Kabir Khan (was: Bill Burke) Please let me know if I am missing anything > Generic ProxyAdvisor > -------------------- > > Key: JBAOP-82 > URL: http://jira.jboss.com/jira/browse/JBAOP-82 > Project: JBoss AOP > Issue Type: Task > Reporter: Adrian Brock > Assigned To: Kabir Khan > > There should be a Generic ProxyAdvisor like the EJB3 Container implementation. > This can be used when a class is not instrumented. Obviously it won't have all the > features of the ClasAdvisor. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBMICROCONT-18) Annotation metadata

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-18?page=all ] Kabir Khan resolved JBMICROCONT-18. ----------------------------------- Resolution: Done Please let me know if I am missing anything > Annotation metadata > ------------------- > > Key: JBMICROCONT-18 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-18 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: JBossMC_2_0_0M1 > > > Add annotation metadata to the BeanMetaData classes for overriding class values > at the instance level. This replaces the getValue(...) stuff in FeatureMetaData. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JGRP-236) Combine join and state transfer

by Vladimir Blagojevic (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-236?page=all ] Vladimir Blagojevic updated JGRP-236: ------------------------------------- Fix Version/s: 2.5 (was: 2.6) > Combine join and state transfer > ------------------------------- > > Key: JGRP-236 > URL: http://jira.jboss.com/jira/browse/JGRP-236 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.8, 2.2.9, 2.3, 2.2.9.1, 2.2.9.2 > Reporter: Bela Ban > Assigned To: Vladimir Blagojevic > Fix For: 2.5 > > > Add an additional connect(String group_name, boolean fetch_state, String state_id) method to Channel, so that we can combine joining and state transfer into 1 operation. This also requires only 1 FLUSH phase. > The state would be returned either via pulling with Channel.receive() or pushing the setState() method in a registered Receiver/MessageListener. > - The JOIN_REQ contains the boolean > - The algorithm in GMS is the same as the two described above, except that before multicasting the new view and sending > the JOIN_RSPs and LEAVE_RSPs, we ask the application for its state (GET_APPLSTATE) and when received (GET_APPLSTATE_OK), > we send it back to the joining member(s), and the RESUME sending messages -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-298) Construction does not work when we have inheritance and generated advisors

by Kabir Khan (JIRA)

Construction does not work when we have inheritance and generated advisors -------------------------------------------------------------------------- Key: JBAOP-298 URL: http://jira.jboss.com/jira/browse/JBAOP-298 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha2 class Parent{ } class Child extends Parent{ } <bind pointcut="execution(* Parent->new()"> <interceptor class="SomeInterceptor"> </bind> <bind pointcut="execution(* Child->new()"> <interceptor class="SomeInterceptor"> </bind> -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-618) Failure in stress tests

by Tim Fox (JIRA)

Failure in stress tests ----------------------- Key: JBMESSAGING-618 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-618 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Alpha1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Alpha2 testQueueMultipleSenders with mySql fails with: [junit] java.lang.IllegalStateException: Didn't load expected number of refe rences, loaded: 18 expected: 36 [junit] at org.jboss.messaging.core.plugin.JDBCPersistenceManager.getPag edReferenceInfos(JDBCPersistenceManager.java:1033) [junit] at org.jboss.messaging.core.PagingChannelSupport.loadPagedRefere nces(PagingChannelSupport.java:309) [junit] at org.jboss.messaging.core.PagingChannelSupport.checkLoad(Pagin gChannelSupport.java:413) [junit] at org.jboss.messaging.core.PagingChannelSupport.removeFirstInMe mory(PagingChannelSupport.java:397) [junit] at org.jboss.messaging.core.ChannelSupport.removeReference(Chann elSupport.java:890) [junit] at org.jboss.messaging.core.ChannelSupport.deliverInternal(Chann elSupport.java:609) [junit] at org.jboss.messaging.core.ChannelSupport$DeliveryRunnable.run( ChannelSupport.java:1199) [junit] at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Q ueuedExecutor.java:89) [junit] at java.lang.Thread.run(Thread.java:534) [junit] Thread-4 19:51:53,734 ERROR [ChannelSupport] Queue[290] Failed to de liver -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-289) Make service container configurable wrt datasource and persistence manager config

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-289?page=all ] Tim Fox closed JBMESSAGING-289. ------------------------------- Resolution: Done > Make service container configurable wrt datasource and persistence manager config > --------------------------------------------------------------------------------- > > Key: JBMESSAGING-289 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-289 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Alpha2 > > > Must be made configurable so test suite can be run against different databases with different pm configs -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-810) TCP Delegating Cache Loader not multithreaded

by Manik Surtani (JIRA)

TCP Delegating Cache Loader not multithreaded --------------------------------------------- Key: JBCACHE-810 URL: http://jira.jboss.com/jira/browse/JBCACHE-810 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 1.4.0.SP2, 2.0.0 Currently causes problems with StreamCorruptedExceptions if multiple threads attempt to write to the same CL since a single instance of the TcpDelegatingCacheLoader creates just one socket connection to the TcpCacheServer. Access to writing to the output stream needs to be synchronised. -- 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, 7 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 October 2006