August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-107) use a logger rather then STD/STERR.

by Kurt Stam (JIRA)

use a logger rather then STD/STERR. ----------------------------------- Key: JBESB-107 URL: http://jira.jboss.com/jira/browse/JBESB-107 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Fix For: 4.0 Beta 1 use a logger rather then STD/STERR. For now we use log4j. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-79) SimpleDataSource does not use the concept of Connection Pool

by Mark Little (JIRA)

SimpleDataSource does not use the concept of Connection Pool ------------------------------------------------------------ Key: JBESB-79 URL: http://jira.jboss.com/jira/browse/JBESB-79 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Beta 1 Reported by Mohit Keswani: SimpleDataSource does not use the concept of Connection Pool but rather creates a new Connection everytime. I am not sure how it will work when multiple services are configured in ESB which connect to the same DB. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-80) Poor exception handling in SimpleDataSource

by Mark Little (JIRA)

Poor exception handling in SimpleDataSource ------------------------------------------- Key: JBESB-80 URL: http://jira.jboss.com/jira/browse/JBESB-80 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Beta 1 Reported by Mohit Keswani: SimpleDataSource (line 105) does not throw any Exception when it cannot get a connection to the DB, instead it simply sets the connection reference to null. This leads to null pointer exceptions everywhere. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBESB-66) Add XML helper class(es)

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-66?page=all ] Mark Little updated JBESB-66: ----------------------------- Fix Version/s: 4.0 (was: 4.0 Beta 1) > Add XML helper class(es) > ------------------------ > > Key: JBESB-66 > URL: http://jira.jboss.com/jira/browse/JBESB-66 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ESB Core > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Arvinder Singh > Priority: Minor > Fix For: 4.0 > > > - common\src\org\jboss\soa\esb\helpers\DomElement.java > 1) Abstract into an xml handling helper package -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340624 ] Adrian Brock commented on JBAS-3242: ------------------------------------ I'll think you'll find the "performance penalty" is actually the checking done by the CachedConnectonManager (CCM) when debug=true. I'd say we enable it by default (if people don't want it, they can always disable it themselves). But we get QA to look at the relative performance of this 1) Disabled 2) Enabled with debug=true 3) Enabled with debug=false We could also split this into two valves. 1) For the CCM checking 2) For the transaction checking A further optimation would be to look at the resource type. e.g. There is no need to check for incomplete transactions if this is a static file being served. > EE spec requires that web container aborts any active txn at the end of a request > --------------------------------------------------------------------------------- > > Key: JBAS-3242 > URL: http://jira.jboss.com/jira/browse/JBAS-3242 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-4.0.6.CR1 > > > The Java EE spec requires that if there is any active JTA transaction at the end of a servlet request, then the container must abort the txn. JBoss currently does not do this. Instead it leaves orphaned transactions dangling about on pooled threads, ready and waiting to be resumed by any random request that comes along. > This is really Bad behavior and I'm kinda shocked. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340623 ] Remy Maucherat commented on JBAS-3242: -------------------------------------- I don't think I have any authority to defaine what the default configuration should be. There's going to be some kind of performance penalty, and you can accept it because the functionality is worth it. > EE spec requires that web container aborts any active txn at the end of a request > --------------------------------------------------------------------------------- > > Key: JBAS-3242 > URL: http://jira.jboss.com/jira/browse/JBAS-3242 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-4.0.6.CR1 > > > The Java EE spec requires that if there is any active JTA transaction at the end of a servlet request, then the container must abort the txn. JBoss currently does not do this. Instead it leaves orphaned transactions dangling about on pooled threads, ready and waiting to be resumed by any random request that comes along. > This is really Bad behavior and I'm kinda shocked. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-30) Ensure public javadoc comments are present and informative

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-30?page=all ] Mark Little updated JBESB-30: ----------------------------- Fix Version/s: 4.0 (was: 4.0 Beta 1) > Ensure public javadoc comments are present and informative > ---------------------------------------------------------- > > Key: JBESB-30 > URL: http://jira.jboss.com/jira/browse/JBESB-30 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB Core, Documentation > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.0 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340621 ] Dimitris Andreadis commented on JBAS-3242: ------------------------------------------ So it seems we haven't reached an aggreement whether to enable this or not, by default. > EE spec requires that web container aborts any active txn at the end of a request > --------------------------------------------------------------------------------- > > Key: JBAS-3242 > URL: http://jira.jboss.com/jira/browse/JBAS-3242 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-4.0.6.CR1 > > > The Java EE spec requires that if there is any active JTA transaction at the end of a servlet request, then the container must abort the txn. JBoss currently does not do this. Instead it leaves orphaned transactions dangling about on pooled threads, ready and waiting to be resumed by any random request that comes along. > This is really Bad behavior and I'm kinda shocked. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340619 ] Remy Maucherat commented on JBAS-3242: -------------------------------------- At the end of server.xml in the Tomcat SAR, there is:  > EE spec requires that web container aborts any active txn at the end of a request > --------------------------------------------------------------------------------- > > Key: JBAS-3242 > URL: http://jira.jboss.com/jira/browse/JBAS-3242 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-4.0.6.CR1 > > > The Java EE spec requires that if there is any active JTA transaction at the end of a servlet request, then the container must abort the txn. JBoss currently does not do this. Instead it leaves orphaned transactions dangling about on pooled threads, ready and waiting to be resumed by any random request that comes along. > This is really Bad behavior and I'm kinda shocked. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3369) Add support for encrypting the tomcat server.xml keystore/truststore attributes

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3369?page=comments#action_12340618 ] Dimitris Andreadis commented on JBAS-3369: ------------------------------------------ Anil, any chance to work on this? > Add support for encrypting the tomcat server.xml keystore/truststore attributes > ------------------------------------------------------------------------------- > > Key: JBAS-3369 > URL: http://jira.jboss.com/jira/browse/JBAS-3369 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Security > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Anil Saldhana > Priority: Critical > Fix For: JBossAS-4.0.5.CR1 > > > We have the ability to encrypt passwords in datasource/login-confg.xml files, but the tomcat server.xml parsing does not currently support this. This is something we need to add. -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006