May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1183) Use total replication by default for clustered SFSB replication

by Brian Stansberry (JIRA)

Use total replication by default for clustered SFSB replication --------------------------------------------------------------- Key: EJBTHREE-1183 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1183 Project: EJB 3.0 Issue Type: Task Components: Clustering Affects Versions: AS 5.0.0.Beta3 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.CR1 Total replication is simpler and quite adequate for the more common smaller clusters; buddy replication should be something users enable. This is the approach we are taking for web sessions as well. This is a simple matter of changing the buddy replication enabled flag from true to false and tweaking the testsuite targets to specially test "BR enabled" instead of "BR disabled". -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1355) ProxiedStatefulBeanContext cannot be deserialized

by Brian Stansberry (JIRA)

ProxiedStatefulBeanContext cannot be deserialized ------------------------------------------------- Key: EJBTHREE-1355 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1355 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: AS 5.0.0.Beta4 Reporter: Brian Stansberry Fix For: AS 5.0.0.CR1 ProxiedStatefulBeanContext implements Externalizable but has no no-arg constructor, so readExternal() doesn't work. It can't just implement Serializable because its superclass doesn't expose an appropriate constructor. Looks like some refactoring of serialization of these classes was done last summer but got dropped mid way in favor of the complete rewrite (EJBTHREE-1026). Since EJBTHREE-1026 is deferred to 5.1.0, we need to get the old way working. -- 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

18 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1344) StatefulTreeCache should use JBC CacheManager

by Brian Stansberry (JIRA)

StatefulTreeCache should use JBC CacheManager --------------------------------------------- Key: EJBTHREE-1344 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1344 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.CR1 Instead of finding the JBC instance in JMX, it should use a JBC CacheManager. -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1361) Ensure SFSB interceptors are deserialized before invoking callbacks

by Brian Stansberry (JIRA)

Ensure SFSB interceptors are deserialized before invoking callbacks ------------------------------------------------------------------- Key: EJBTHREE-1361 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1361 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: AS 5.0.0.Beta4 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.CR1 The way lifecycle callbacks (e.g. PostReplicate, PostActivate) are invoked has changed from 4.x, which the result that StatefulBeanContext.extractBeanAndInterceptors() isn't always called before an attempts is made to invoke the callbacks. Result is failures like this: java.lang.IllegalArgumentException: No interceptor found for class org.jboss.ejb3.test.ejbthree921.ExplicitFailoverInterceptor in org.jboss.ejb3.stateful.StatefulBeanContext@363d37 at org.jboss.ejb3.BaseContext.getInterceptor(BaseContext.java:146) at org.jboss.ejb3.interceptors.aop.LifecycleCallbacks.createLifecycleCallbackInterceptors(LifecycleCallbacks.java:56) at org.jboss.ejb3.EJBContainer.invokeCallback(EJBContainer.java:1021) at org.jboss.ejb3.stateful.StatefulContainer.invokePostActivate(StatefulContainer.java:560) at org.jboss.ejb3.stateful.StatefulBeanContext.postReplicate(StatefulBeanContext.java:586) at org.jboss.ejb3.cache.tree.StatefulTreeCache.get(StatefulTreeCache.java:198) at org.jboss.ejb3.cache.tree.StatefulTreeCache.get(StatefulTreeCache.java:163) at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:59) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.ReplicantsManagerInterceptor.invoke(ReplicantsManagerInterceptor.java:51) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:157) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:485) at org.jboss.ejb3.session.ClassProxyHack._dynamicInvoke(ClassProxyHack.java:52) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:850) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:727) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:672) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:495) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:207) Fix is to ensure extractBeanAndInterceptors() is called before asking the container to invoke the callbacks. -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBTEST-4) Remove non-shared clustering content from server-config.xml

by Brian Stansberry (JIRA)

Remove non-shared clustering content from server-config.xml ----------------------------------------------------------- Key: JBTEST-4 URL: http://jira.jboss.com/jira/browse/JBTEST-4 Project: JBoss Test Issue Type: Task Affects Versions: 1.1.0.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 1.1.1.GA The JBTEST server-config.xml includes a bunch of clustering-related content that isn't really meant to be shared across projects; i.e. it either applies only to the AS or only to EJB3. I want to remove it from this file so it only lives in the appropriate project. Avoid issues of having to publish/integrate new JBTEST releases just to make some minor change to a testsuite. -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1360) Restore StatefulBeanContext externalization

by Brian Stansberry (JIRA)

Restore StatefulBeanContext externalization ------------------------------------------- Key: EJBTHREE-1360 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1360 Project: EJB 3.0 Issue Type: Task Components: core Affects Versions: AS 5.0.0.Beta4 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.CR1 Some of the work done last summer on EJBTHREE-1016 broke the ability to externalize ProxiedStatefulBeanContext and related classes in the StatefulBeanContext class hierarchy. This hierarchy will be replaced in 5.1.0 by the work for EJBTHREE-1026, but for 5.0.0 we need to restore the old serialization/externalization mechanisms. -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-287) Error message trying to use aop-mc-int schema in AS5

by Kabir Khan (JIRA)

Error message trying to use aop-mc-int schema in AS5 ---------------------------------------------------- Key: JBMICROCONT-287 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-287 Project: JBoss MicroContainer Issue Type: Feature Request Components: AOP Reporter: Kabir Khan Attachments: boot.txt The forum post truncates the stack trace, so I am attaching it to this issue -- 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

18 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-218) SecurityConfiguration : remove Application Policy method

by Anil Saldhana (JIRA)

SecurityConfiguration : remove Application Policy method -------------------------------------------------------- Key: SECURITY-218 URL: http://jira.jboss.com/jira/browse/SECURITY-218 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.CR1 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR2 -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5521) EJBPermissionMapping legacy method needs to be removed

by Anil Saldhana (JIRA)

EJBPermissionMapping legacy method needs to be removed ------------------------------------------------------ Key: JBAS-5521 URL: http://jira.jboss.com/jira/browse/JBAS-5521 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2, Security Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 public static void createPermissions(BeanMetaData bean, PolicyConfiguration pc) throws PolicyContextException; needs to go as it is unused. -- 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

18 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-32) White Paper on Clustered SSO

by Anil Saldhana (JIRA)

White Paper on Clustered SSO ---------------------------- Key: SECURITY-32 URL: http://jira.jboss.com/jira/browse/SECURITY-32 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: White Papers Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Sakthi Samabsivam Fix For: 2.0 White paper on the Clustered SSO offering from JBoss. http://wiki.jboss.org/wiki/Wiki.jsp?page=SingleSignOn http://wiki.jboss.org/wiki/Wiki.jsp?page=BuddyReplicationAndClusteredSSO This is important because many customers are using this along with http session replication. -- 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

18 years, 2 months

2
12
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 May 2008