May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4455) LoadBalancePolicy that tries to pin all requests associated with a tx to one server

by Brian Stansberry (JIRA)

LoadBalancePolicy that tries to pin all requests associated with a tx to one server ----------------------------------------------------------------------------------- Key: JBAS-4455 URL: http://jira.jboss.com/jira/browse/JBAS-4455 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Galder Zamarreno Priority: Minor The HA proxies don't allow failover once a tx has reached a server. This can lead to this kind of situation: EJB A deployed on nodes 1 and 2. EJB B deployed on nodes 1 and 2. 1) Start tx, invoke on A.1. 2) Lookup B. 3) Invoke on B. LB policy picks B.2 4) Node 2 is dead for some reason so call fails. 5) Can't fail over because tx context won't allow a failover after a call has reached a server. But, B.1 is fine and is running on the only node the tx has invoked on. :( Approach to improving this. This is based on JRMPInovkerProxyHA methods, but the idea is generic: In invocationHasReachedAServer, instead of storing null as the value, you store the target (key is the tx). In invoke, if there's a tx, you add that target (if there is one) to the invocation as transient metadata The LB policy gets passed the invocation as an arg when it chooses a target (this is already in the API) LB policy checks for the metadata. If there, and that target is in its target list, return that target -- 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, 6 months

3
12
0 / 0

[JBoss JIRA] Created: (JBFORUMS-232) Add Italian and German support

by Ryszard Kozmik (JIRA)

Add Italian and German support ------------------------------ Key: JBFORUMS-232 URL: http://jira.jboss.com/jira/browse/JBFORUMS-232 Project: JBoss Forums Issue Type: Task Components: Forum View Layer, Portlet Productization Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC ResourceBundles for those languages have to be added and made simplified like the main one. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-324) Build.xml in testsuite directory doesn't support multiple JVM argument

by Sunny Chan (JIRA)

Build.xml in testsuite directory doesn't support multiple JVM argument ---------------------------------------------------------------------- Key: JBBUILD-324 URL: http://jira.jboss.com/jira/browse/JBBUILD-324 Project: JBoss Build System Issue Type: Feature Request Components: Targets and Tasks Affects Versions: Repository Build head, Repsository Build Branch_4_0 Environment: Any Reporter: Sunny Chan Priority: Minor We are using the JBoss unit test as part of our JVM verification testsuite. We wanted to be able to invoke tests with multiple JVM options, but it didn't work. If you set parameters via build.sh -Djunit.vm.options with multiple paramters (e.g. -Djunit.vm.options="-d64 -verbose:gc"), it will fail with unrecongized option error. The problem is that in testsuite/build.xml, the junit.vm.options is passed onto junit ant task via <jvmarg value> tag rather then <jvmarg line> tag. The jvmarg line allows multiple JVM options exist in one line. Once I replace all instance of <jvmarg value="${junit.jvm.options}"/> with <jvmarg line="${junit.jvm.options}"/> then the problem goes away. I can provide a patch for this if you want - but I don't know the rules on patches (whether I need to be cleared for contribution) so let me know if you want that. -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-4301) Evaluate replacing FileCacheLoader with JdbmCacheLoader

by Brian Stansberry (JIRA)

Evaluate replacing FileCacheLoader with JdbmCacheLoader ------------------------------------------------------- Key: JBAS-4301 URL: http://jira.jboss.com/jira/browse/JBAS-4301 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Need to establish a relationship with the JDBM guys to see how suitable and supportable it is. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-974) Temporarly have the SecurityDeployer ignore all EJB3 deployments

by Carlo de Wolf (JIRA)

Temporarly have the SecurityDeployer ignore all EJB3 deployments ---------------------------------------------------------------- Key: EJBTHREE-974 URL: http://jira.jboss.com/jira/browse/EJBTHREE-974 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - 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

18 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-971) Allow injection of EJBContext into java:comp/env via Resource annotation

by Carlo de Wolf (JIRA)

Allow injection of EJBContext into java:comp/env via Resource annotation ------------------------------------------------------------------------ Key: EJBTHREE-971 URL: http://jira.jboss.com/jira/browse/EJBTHREE-971 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - 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

18 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-973) Allow a @SecurityDomain with only unauthenticatedPrincipal

by Carlo de Wolf (JIRA)

Allow a @SecurityDomain with only unauthenticatedPrincipal ---------------------------------------------------------- Key: EJBTHREE-973 URL: http://jira.jboss.com/jira/browse/EJBTHREE-973 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Allow a @SecurityDomain with only an unauthenticatedPrincipal so getCallerPrincipal doesn't throw an IllegalStateException. Effectively the bean would run without security, because principals can't be validated. Note that in time the server itself will have an unauthenticatedPrincipal default which comes from the security deployer. (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107751) -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-972) sessionContext.getBusinessObject(null) should throw IllegalStateException

by Carlo de Wolf (JIRA)

sessionContext.getBusinessObject(null) should throw IllegalStateException ------------------------------------------------------------------------- Key: EJBTHREE-972 URL: http://jira.jboss.com/jira/browse/EJBTHREE-972 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - 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

18 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-963) ejbCreate method is optional in EJB 2.1 bean

by Carlo de Wolf (JIRA)

ejbCreate method is optional in EJB 2.1 bean -------------------------------------------- Key: EJBTHREE-963 URL: http://jira.jboss.com/jira/browse/EJBTHREE-963 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf -- 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, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-966) setSessionContext not called on an EJB 2.1 bean

by Carlo de Wolf (JIRA)

setSessionContext not called on an EJB 2.1 bean ----------------------------------------------- Key: EJBTHREE-966 URL: http://jira.jboss.com/jira/browse/EJBTHREE-966 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Fix For: Branch_4_2, EJB 3.0 RC11 - 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

18 years, 7 months

1
5
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 2007