March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-2004) Track release of EJB3_1 1.0.3

by jaikiran pai (JIRA)

Track release of EJB3_1 1.0.3 ----------------------------- Key: EJBTHREE-2004 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2004 Project: EJB 3.0 Issue Type: Task Components: ejb3_1 Reporter: jaikiran pai Assignee: jaikiran pai JIRA to track upgrades during ejb3_1 1.0.3 release. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2021) Ant task to install ejb3 in defaul-with-hornetq profile

by Christian Reichel (JIRA)

Ant task to install ejb3 in defaul-with-hornetq profile ------------------------------------------------------- Key: EJBTHREE-2021 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2021 Project: EJB 3.0 Issue Type: Feature Request Components: installer Affects Versions: Plugin 1.0.19 Environment: any Reporter: Christian Reichel I have JBOSS AS 5.1.0 GA installed with HornetQ 2.0.0 GA instaled as a new profile (default-with-hornetq). So when I try to install the ejb3 plugin this instance is not found. -- 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2024) Set a sensible timeout on EJB3 remoting connector

by jaikiran pai (JIRA)

Set a sensible timeout on EJB3 remoting connector ------------------------------------------------- Key: EJBTHREE-2024 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2024 Project: EJB 3.0 Issue Type: Task Components: core Affects Versions: EJB3_1 1.0.4 Reporter: jaikiran pai Assignee: jaikiran pai Recent hanging jobs on Mike have shown that the remoting client socket timeout (default = 30 mins) doesn't work because of JBREM-1188. The workaround to the issue is to explicitly set a timeout value. Even if it wasn't a bug, the default timeout of 30 minutes is a bit too high. Maybe a timeout of 10 minutes (or lesser) would be sufficient. I'll open a forum thread just in case someone has any inputs for a sensible timeout value. -- 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

16 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2030) SimpleStatefulCache does not check for passivated session during a remove() call

by jaikiran pai (JIRA)

SimpleStatefulCache does not check for passivated session during a remove() call -------------------------------------------------------------------------------- Key: EJBTHREE-2030 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2030 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: EJB3_1 1.0.5, Plugin 1.0.19, 1.1.22 Reporter: jaikiran pai Assignee: jaikiran pai org.jboss.ejb3.cache.SimpleStatefulCache during passivation call does the following: 1) passivates the session 2) removes the session from the cache However, later, if some code calls a remove() for the passivated instance, it throws a NoSuchEJBException because the remove() method does *not* check for passivated instances. See the referenced forum thread for the complete details. -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-277) CFConstructor rule

by Jesper Pedersen (JIRA)

CFConstructor rule ------------------ Key: JBJCA-277 URL: https://jira.jboss.org/jira/browse/JBJCA-277 Project: JBoss JCA Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 1.0.0.Alpha9 Add a cf.CFConstructor rule that test if the class has a no argument constructor. Severity: ERROR Section: 17.5.1.1 Description: A ConnectionFactory must have a default constructor -- 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBJCA-291) Extract the validator code from deployers/ into validator module

by Jeff Zhang (JIRA)

Extract the validator code from deployers/ into validator module ---------------------------------------------------------------- Key: JBJCA-291 URL: https://jira.jboss.org/jira/browse/JBJCA-291 Project: JBoss JCA Issue Type: Task Components: Validator Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Alpha10 Extract the validator code from deployers/ into validator module The jboss-jca-validator-*.jar could then depend on jboss-jca-common-impl.jar as the annotation / metadata classes would move to the common/ module. The validator should be refactored into org.jboss.jca.validator -- and sub-packages. The validator/ module should of course be built before deployers/ - as the deployers would depend on it. The validator/ module should have * jboss-jca-validator.jar (framework) * jboss-jca-validator-cli.jar (standalone) * jboss-jca-validator-ant.jar (Ant task) * jboss-jca-validator-maven.jar (Maven plugin) -- 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

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1171) Integrate remote protocol into R3

by David Lloyd (JIRA)

Integrate remote protocol into R3 --------------------------------- Key: JBREM-1171 URL: https://jira.jboss.org/jira/browse/JBREM-1171 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.GA -- 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

16 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 2010