November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-567) Default constructors are not handled

by Flavia Rainone (JIRA)

Default constructors are not handled ------------------------------------ Key: JBAOP-567 URL: http://jira.jboss.com/jira/browse/JBAOP-567 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR8 Reporter: Flavia Rainone Fix For: 2.1.0.GA Pointcut expressions don't match default constructors. To reproduce this error, comment out the empty default constructors present in the following classes: org.jboss.test.aop.rebuildingchain.ConstructorExecutionSyncThread org.jboss.test.aop.rebuildingchain.ConstructionExecutionSyncThread -- 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

15 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1056) Redo NestedBeanUnitTestCase.testConsistentPassivatedState()

by Brian Stansberry (JIRA)

Redo NestedBeanUnitTestCase.testConsistentPassivatedState() ----------------------------------------------------------- Key: EJBTHREE-1056 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1056 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor NestedBeanUnitTestCase.testConsistentPassivatedState() is a pretty weak test for the EJBTHREE-1053 condition; when the parent issue is fixed, replace this test with something better. -- 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

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1346) Disabling @Clustered via jboss.xml not being respected

by Brian Stansberry (JIRA)

Disabling @Clustered via jboss.xml not being respected ------------------------------------------------------ Key: EJBTHREE-1346 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1346 Project: EJB 3.0 Issue Type: Bug Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.CR1 An @Clustered bean with <clustered>false</clustered> in its jboss.xml is still using the clustered proxy factory: 2008-05-08 12:56:44,768 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (RMI TCP Connection(27)-127.0.0.1) Error installing to Start: name=jboss.j2ee:ear=clusteredsession-test.jar,jar=clusteredsession-test.jar,name=NonClusteredStateful,service=EJB3 state=Create java.lang.IllegalStateException: Partition BogusPartition not found at org.jboss.ha.framework.server.HAPartitionLocator.getHAPartition(HAPartitionLocator.java:125) at org.jboss.ejb3.proxy.factory.stateful.StatefulClusterProxyFactory.start(StatefulClusterProxyFactory.java:144) at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:95) at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:188) at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:249) -- 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

15 years, 9 months

3
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1540) Test handling of SFSB with @Clustered but no @Remote

by Brian Stansberry (JIRA)

Test handling of SFSB with @Clustered but no @Remote ---------------------------------------------------- Key: EJBTHREE-1540 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1540 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Effect should be that the bean state is replicated around the cluster but there is no clustered proxy (i.e. no load balancing / failover in the bean proxy). The lack of a remote interface precludes a clustered proxy. This is quite a useful config if the bean client is something like a clustered webapp; the proxy is stored in the web session, which is replicated. Loadbalancing/failover are managed at the web tier level. If the web session fails over, the proxy should be able to interact with the local bean container, and the replication of the bean state means the needed state is available. -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1570) Pull basic clustered proxy tests out of testsuite and into proxy-clustered

by Brian Stansberry (JIRA)

Pull basic clustered proxy tests out of testsuite and into proxy-clustered -------------------------------------------------------------------------- Key: EJBTHREE-1570 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1570 Project: EJB 3.0 Issue Type: Task Components: Clustering, proxy-clustered, testsuite Reporter: Brian Stansberry Look through the testsuite/org.jboss.ejb3.test.clusteredsession packages and pull stuff out that logically should be tested in proxy-clustered. -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1547) ProxyFactory remains usable during SFSB container shutdown

by Brian Stansberry (JIRA)

ProxyFactory remains usable during SFSB container shutdown ---------------------------------------------------------- Key: EJBTHREE-1547 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1547 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: 1.0.0-Beta5 Reporter: Brian Stansberry During a testing session with a service that was using 4 threads to continually create SFSBs, I attempted to undeploy the bean. Got log failures like the following: 18:56:20,638 ERROR [RegionManager] failed inactivating /sfsb/jar=andymiller-test.jar,name=SimpleAnnotationStatefulBean,service=EJB3 org.jboss.cache.CacheException: Region /sfsb/jar=andymiller-test.jar,name=SimpleAnnotationStatefulBean,service=EJB3 is already being activated/deactivated at org.jboss.cache.RegionManager.inactivateRegion(RegionManager.java:573) at org.jboss.cache.RegionManager.activateRegion(RegionManager.java:508) at org.jboss.cache.RegionManager.activate(RegionManager.java:376) at org.jboss.cache.RegionManager.activate(RegionManager.java:339) at org.jboss.cache.RegionImpl.activate(RegionImpl.java:82) at org.jboss.ejb3.cache.tree.StatefulTreeCache.start(StatefulTreeCache.java:358) at org.jboss.ejb3.stateful.StatefulContainer.createAndStartCache(StatefulContainer.java:302) at org.jboss.ejb3.stateful.StatefulContainer.getCache(StatefulContainer.java:340) at org.jboss.ejb3.stateful.StatefulContainer.createSession(StatefulContainer.java:488) at org.jboss.ejb3.session.SessionContainer.createSession(SessionContainer.java:550) at org.jboss.ejb3.proxy.factory.session.stateful.StatefulSessionProxyFactoryBase.getNewSessionId(StatefulSessionProxyFactoryBase.java:296) at org.jboss.ejb3.proxy.factory.session.stateful.StatefulSessionProxyFactoryBase.createProxyBusiness(StatefulSessionProxyFactoryBase.java:160) at org.jboss.ejb3.proxy.objectfactory.session.SessionProxyObjectFactory.createProxy(SessionProxyObjectFactory.java:133) at org.jboss.ejb3.proxy.clustered.objectfactory.session.stateful.StatefulSessionClusteredProxyObjectFactory.getProxy(StatefulSessionClusteredProxyObjectFactory.java:66) at org.jboss.ejb3.proxy.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:153) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1426) at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1443) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:797) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:661) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.ejb3.test.clusteredsession.SimpleAnnotationStatefulBeanUser$BeanCreator.run(SimpleAnnotationStatefulBeanUser.java:85) at java.lang.Thread.run(Thread.java:595) The at org.jboss.ejb3.cache.tree.StatefulTreeCache.start(StatefulTreeCache.java:358) at org.jboss.ejb3.stateful.StatefulContainer.createAndStartCache(StatefulContainer.java:302) logging shows container's 'cache' field has been nulled, so the request thread is trying to create and start a new cache. This then leads to conflicts at the JBC level, where the HDScanner thread is doing work to undeploy the old cache. Couple thoughts: 1) Is letting a request thread create/start the cache a good idea? Shouldn't this be limited to the start() sequence, with an ISE thrown if a request thread finds there is no cache? 2) Should we be adding something like the org.jboss.ejb3.BlockContainerShutdownInterceptor into this call stack to ensure we don't get race conditions like this? -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2191) "Half-authentication" mode

by Thomas Heute (JIRA)

"Half-authentication" mode -------------------------- Key: JBPORTAL-2191 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2191 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Heute Assignee: Sohil Shah People want "remember me" feature which is impossible to guarantee with high level of security. Still to be able to provide such a feature without putting a portal at risk we can think of a "half-authenticated" feature, where the user coming back on a website would be remembered but won't have access to sensitive data or to modify important data (such as password) unless he authenticates. -- 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

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-922) Handle merging of clustered SFSB state if a MergeView is received

by Brian Stansberry (JIRA)

Handle merging of clustered SFSB state if a MergeView is received ----------------------------------------------------------------- Key: EJBTHREE-922 URL: http://jira.jboss.com/jira/browse/EJBTHREE-922 Project: EJB 3.0 Issue Type: Task Components: Clustering Affects Versions: AS 4.2.0 CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry The JBCACHE-8 solution will provide a notification of when a cluster merge occurs. Need to work with the JBC team to design the callback and to implement a solution that will allow merging of clustered SFSB state. -- 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

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-895) Allow clustered tests to run with -u set

by Brian Stansberry (JIRA)

Allow clustered tests to run with -u set ---------------------------------------- Key: EJBTHREE-895 URL: http://jira.jboss.com/jira/browse/EJBTHREE-895 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Need to use the local.properties "udpGroup" stuff that the AS uses. Allows running with less concern for impactt from / impacting other running servers. -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-857) Include and use buddy group topology information in clustered SFSB proxies

by Brian Stansberry (JIRA)

Include and use buddy group topology information in clustered SFSB proxies -------------------------------------------------------------------------- Key: EJBTHREE-857 URL: http://jira.jboss.com/jira/browse/EJBTHREE-857 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Look into including the replicated SFSB cache's buddy replication group topology in clustered SFSB proxies, and using that information in fail over decisions. This is basically an optimization such that when a failover occurs, data gravitation can occur in VM rather than over the network. -- 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

15 years, 9 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008