March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBCACHE-407) Write locks not acquired on newly created empty nodes

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-407?page=comments#action_12356668 ] Manik Surtani commented on JBCACHE-407: --------------------------------------- Note that this does work properly if "LockParentForChildInsertRemove" is set to true. > Write locks not acquired on newly created empty nodes > ----------------------------------------------------- > > Key: JBCACHE-407 > URL: http://jira.jboss.com/jira/browse/JBCACHE-407 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.4.1.GA, 1.4.0.GA, 1.3.0.GA, 2.0.0.GA > Reporter: Brian Stansberry > Assigned To: Manik Surtani > Fix For: 2.1.0.GA > > > When an empty node is created during a put (e.g node "/a" created as a result of a cache.put("/a/1", "key", "value"); call), only a read lock is acquired on the empty node. If the node is created as part of a transaction, the following failure can occur: > 2 threads, empty cache, READ_COMMITTED > 1) T1 starts a tx > 2) T1 invokes cache.put("/a/1", "key", "value1"); > 3) T2 invokes cache.put("/a/2", "key", "value2"); > 4) T1's transaction rolls back > 5) T2 invokes cache.get("/a/2", "key"); Should get "value2", will get null because the tx rollback will remove node /a and thus /a/2 as well. > This IMO breaks READ_COMMITTED semantics, as T2 is able to "read" /a (in the sense of seeing it exists and thus can have children appended to it) before the tx that created /a is committed. > New unit test IsolationLevelReadCommittedTest.testNodeCreationRollback() demonstrates the 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCACHE-407) Write locks not acquired on newly created empty nodes

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-407?page=all ] Manik Surtani reassigned JBCACHE-407: ------------------------------------- Assignee: Manik Surtani (was: Bela Ban) > Write locks not acquired on newly created empty nodes > ----------------------------------------------------- > > Key: JBCACHE-407 > URL: http://jira.jboss.com/jira/browse/JBCACHE-407 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Manik Surtani > Fix For: 2.0.0.GA > > > When an empty node is created during a put (e.g node "/a" created as a result of a cache.put("/a/1", "key", "value"); call), only a read lock is acquired on the empty node. If the node is created as part of a transaction, the following failure can occur: > 2 threads, empty cache, READ_COMMITTED > 1) T1 starts a tx > 2) T1 invokes cache.put("/a/1", "key", "value1"); > 3) T2 invokes cache.put("/a/2", "key", "value2"); > 4) T1's transaction rolls back > 5) T2 invokes cache.get("/a/2", "key"); Should get "value2", will get null because the tx rollback will remove node /a and thus /a/2 as well. > This IMO breaks READ_COMMITTED semantics, as T2 is able to "read" /a (in the sense of seeing it exists and thus can have children appended to it) before the tx that created /a is committed. > New unit test IsolationLevelReadCommittedTest.testNodeCreationRollback() demonstrates the 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4219) JBoss deployment Problem

by Paresh Zawar (JIRA)

JBoss deployment Problem ------------------------ Key: JBAS-4219 URL: http://jira.jboss.com/jira/browse/JBAS-4219 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Environment: Running MyEclipse4.1.1 Reporter: Paresh Zawar I m tring to deploy a exploded archive on Jboss4. For the first time it deploys it fine. But whenever i change any piece of code and try to redeploy it,it gives me a blank error box.After closing the box,it gives the following warning in the deployment window... "Deployment is out of date due to changes in the underlying project contents.you'll need to manually redeploy the project to update the deployed archive." Other than this it sometimes also deletes the .war files it creates for the application. Any leads why this happens??? -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=all ] Adrian Brock updated JBAS-3321: ------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101152 Updated with correct development forum discussion reference. Please keep discussions/questions in the forums (not in JIRA which becomes part of the release notes). > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Weston Price > Fix For: JBossAS-4.2.0.CR1 > > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=all ] Adrian Brock updated JBAS-3321: ------------------------------- Comment: was deleted > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Weston Price > Fix For: JBossAS-4.2.0.CR1 > > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=all ] Adrian Brock updated JBAS-3321: ------------------------------- Comment: was deleted > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Weston Price > Fix For: JBossAS-4.2.0.CR1 > > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=all ] Adrian Brock updated JBAS-3321: ------------------------------- Comment: was deleted > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Weston Price > Fix For: JBossAS-4.2.0.CR1 > > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

by Johan Walles (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3321?page=comments#action_12356627 ] Johan Walles commented on JBAS-3321: ------------------------------------ In http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104410 I presented the following use-case: @TransactionAttribute(TransactionAttributeType.REQUIRED) @TransactionTimeout(1200) public void onMessage(Message message) { ... } Will that use-case (that doesn't work in 4.0.5) be supported with the fix for this bug in place? > Support for "method-attributes" including "transaction-timeout" for MDBs > ------------------------------------------------------------------------ > > Key: JBAS-3321 > URL: http://jira.jboss.com/jira/browse/JBAS-3321 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Galder Zamarreno > Assigned To: Weston Price > Fix For: JBossAS-4.2.0.CR1 > > > Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", > particularly "transaction-timeout", why is this? > I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact > Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss? > I guess it is either an error or a deliberate design decision not to support it, if it's the latter I > would be interested to hear what the rational is? > Adrian Brock wrote: > Because the MDB transaction is not started by the EJB container > like the other EJB types. > Raise a feature request. There is no reason why the ServerSessionPool > cannot ask the EJB container for this information. > _________________ > Adrian Brock > Chief Scientist > JBoss, Inc. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1254) Support UserContexts properly

by Chris Laprun (JIRA)

Support UserContexts properly ----------------------------- Key: JBPORTAL-1254 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1254 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final Convert portal identity to WSRP UserContext and back. -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4214) Need to port EARDeployer isolation settings to AppParsingDeployer

by Scott M Stark (JIRA)

Need to port EARDeployer isolation settings to AppParsingDeployer ----------------------------------------------------------------- Key: JBAS-4214 URL: http://jira.jboss.com/jira/browse/JBAS-4214 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta2 The old EARDeployer class loading isolation and call by value settings need to be ported over to the AppParsingDeployer since that is where the equivalent metadata is introduced in the new deployer layer. -- 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

19 years, 3 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 2007