May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4360) Upgrade to JGroups 2.4.1.SP2

by Brian Stansberry (JIRA)

Upgrade to JGroups 2.4.1.SP2 ---------------------------- Key: JBAS-4360 URL: http://jira.jboss.com/jira/browse/JBAS-4360 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.0.CR2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.GA -- 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

16 years, 12 months

3
8
0 / 0

[JBoss JIRA] Commented: (JBCACHE-1041)

by Galder Zamarreno (JIRA)

Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI In-Reply-To: <27496970.1178097510296.JavaMail.jira(a)cloud.prod.atl2.jboss.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk [ http://jira.jboss.com/jira/browse/JBCACHE-1041?page=comments#action_12361113 ] Galder Zamarreno commented on JBCACHE-1041: ------------------------------------------- Manik, I'm working refactoring the tutorial to fit PojoCache tutorial into it too, so I might as well deal with this JIRA too? > Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI > ---------------------------------------------------------------------------------------------------- > > Key: JBCACHE-1041 > URL: http://jira.jboss.com/jira/browse/JBCACHE-1041 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.CR1 > Reporter: Galder Zamarreno > Assigned To: Galder Zamarreno > Priority: Minor > Fix For: 2.0.0.CR2 > > > Instructions: > - add a node to the cache > - start a transaction > - do a put on that node > - clicking on the node via the GUI to check that the node has not been > updated blocks both the GUI and the beanshell. This is due to not being able to > acquire the read lock on the node to show it. > - Also, once the exception is thrown, the GUI/beanshell stops which shouldn't. > Solution: > - Updates on the GUI should be handled in a different thread so that it does > not block the shell? While the shell is blocked, the current transaction cannot be > committed, leaving the user no option. -- 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

16 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1041)

by Galder Zamarreno (JIRA)

Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI In-Reply-To: <27496970.1178097510296.JavaMail.jira(a)cloud.prod.atl2.jboss.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk [ http://jira.jboss.com/jira/browse/JBCACHE-1041?page=all ] Galder Zamarreno updated JBCACHE-1041: -------------------------------------- Summary: Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI was: Tutorial Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI > Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI > ---------------------------------------------------------------------------------------------------- > > Key: JBCACHE-1041 > URL: http://jira.jboss.com/jira/browse/JBCACHE-1041 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.CR1 > Reporter: Galder Zamarreno > Assigned To: Galder Zamarreno > Priority: Minor > Fix For: 2.0.0.CR2 > > > Instructions: > - add a node to the cache > - start a transaction > - do a put on that node > - clicking on the node via the GUI to check that the node has not been > updated blocks both the GUI and the beanshell. This is due to not being able to > acquire the read lock on the node to show it. > - Also, once the exception is thrown, the GUI/beanshell stops which shouldn't. > Solution: > - Updates on the GUI should be handled in a different thread so that it does > not block the shell? While the shell is blocked, the current transaction cannot be > committed, leaving the user no option. -- 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

16 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1041) Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI

by Galder Zamarreno (JIRA)

Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI In-Reply-To: <27496970.1178097510296.JavaMail.jira(a)cloud.prod.atl2.jboss.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk [ http://jira.jboss.com/jira/browse/JBCACHE-1041?page=all ] Galder Zamarreno updated JBCACHE-1041: -------------------------------------- Summary: Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI was: Tutorial - GUI/beanshell block if node modified within transaction and Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI > Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBCACHE-1041 > URL: http://jira.jboss.com/jira/browse/JBCACHE-1041 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.CR1 > Reporter: Galder Zamarreno > Assigned To: Galder Zamarreno > Priority: Minor > Fix For: 2.0.0.CR2 > > > Instructions: > - add a node to the cache > - start a transaction > - do a put on that node > - clicking on the node via the GUI to check that the node has not been > updated blocks both the GUI and the beanshell. This is due to not being able to > acquire the read lock on the node to show it. > - Also, once the exception is thrown, the GUI/beanshell stops which shouldn't. > Solution: > - Updates on the GUI should be handled in a different thread so that it does > not block the shell? While the shell is blocked, the current transaction cannot be > committed, leaving the user no option. -- 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

16 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1041) Tutorial

by Galder Zamarreno (JIRA)

Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI In-Reply-To: <27496970.1178097510296.JavaMail.jira(a)cloud.prod.atl2.jboss.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk [ http://jira.jboss.com/jira/browse/JBCACHE-1041?page=all ] Galder Zamarreno updated JBCACHE-1041: -------------------------------------- Summary: Tutorial Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI was: Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI > Tutorial Tutorial - GUI/beanshell block if node modified within transaction and node status queried via GUI > ------------------------------------------------------------------------------------------------------------ > > Key: JBCACHE-1041 > URL: http://jira.jboss.com/jira/browse/JBCACHE-1041 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.CR1 > Reporter: Galder Zamarreno > Assigned To: Galder Zamarreno > Priority: Minor > Fix For: 2.0.0.CR2 > > > Instructions: > - add a node to the cache > - start a transaction > - do a put on that node > - clicking on the node via the GUI to check that the node has not been > updated blocks both the GUI and the beanshell. This is due to not being able to > acquire the read lock on the node to show it. > - Also, once the exception is thrown, the GUI/beanshell stops which shouldn't. > Solution: > - Updates on the GUI should be handled in a different thread so that it does > not block the shell? While the shell is blocked, the current transaction cannot be > committed, leaving the user no option. -- 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

16 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1374) XML Descriptors chapter is incomplete

by Boleslaw Dawidowicz (JIRA)

XML Descriptors chapter is incomplete ------------------------------------- Key: JBPORTAL-1374 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1374 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.CR2 Reporter: Boleslaw Dawidowicz Assigned To: Julien Viet Priority: Optional Fix For: 2.6 Final XML Descriptors chapter: http://cruisecontrol.jboss.com/cc/artifacts/jboss-portal-latest-doc/refer... is incomplete - description of few tags has just "todo" or is empty -- 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

16 years, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-351) Boolean.parseBoolean() not replaced with a JDK 1.4 compat method

by Manik Surtani (JIRA)

Boolean.parseBoolean() not replaced with a JDK 1.4 compat method ---------------------------------------------------------------- Key: JBBUILD-351 URL: http://jira.jboss.com/jira/browse/JBBUILD-351 Project: JBoss Build System Issue Type: Bug Components: JBossRetro Environment: This bug exists in JBossRetro-1.0.4.GA Reporter: Manik Surtani Assigned To: Paul Gier http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Boolean.html#parseBoole... should be replaced with http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Boolean.html#valueOf(ja... and then converting the resulting Boolean object into a primitive. -- 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

17 years

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-940) Bulk operations don't work properly with JBoss Cache as 2nd level cache

by Brian Stansberry (JIRA)

Bulk operations don't work properly with JBoss Cache as 2nd level cache ----------------------------------------------------------------------- Key: EJBTHREE-940 URL: http://jira.jboss.com/jira/browse/EJBTHREE-940 Project: EJB 3.0 Issue Type: Bug Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 4.2.0 CR2 See http://opensource.atlassian.com/projects/hibernate/browse/HHH-2532 for the underlying issue. Hibernate 3.2.3 includes a temporary fix for the problem, but it doesn't work when org.jboss.ejb3.entity.TreeCacheProviderHook or OptimisticTreeCacheProviderHook are used as as the CacheProvider. For AS 4.2 need to ensure the problem is fixed when these classes are used. -- 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

17 years

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-948) FamilyClusterInfo not properly scoped

by Brian Stansberry (JIRA)

FamilyClusterInfo not properly scoped ------------------------------------- Key: EJBTHREE-948 URL: http://jira.jboss.com/jira/browse/EJBTHREE-948 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 CR2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 4.2.0 GA StatefulClusterProxyFactory and StatelessClusterProxyFactory are using Container.getEjbName() to identify beans. This is inadequate as the ejb name need not be unique across deployments. Different deployments with the same name will overwrite each others' FamilyClusterInfo. Should probably use the OID. EJB2 uses the container's JMX ObjectName, which is basically the same as the EJB3 OID. -- 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

17 years

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-946) StatefulTreeCache does not properly segregate deployments

by Brian Stansberry (JIRA)

StatefulTreeCache does not properly segregate deployments --------------------------------------------------------- Key: EJBTHREE-946 URL: http://jira.jboss.com/jira/browse/EJBTHREE-946 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.0 CR2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 4.2.0 GA StatefulTreeCache is using Container.getEjbName() as the first element in a bean node's Fqn. This is insufficient as that's not unique across deployments. If you deploy 2 jars and both have an ejb named Foo, when one of the jars is undeployed, the /Foo region is removed from the cache, which is unacceptable. StatefulSessionFilePersistenceManager solves this by adding a UID to name of the directory where it stores files, but that is inadequate for clustered beans, since all nodes in the cluster need to arrive at the same Fqn. Likely solution is to prefix the ejb name with something built up a la StatefulContainer.getDeployment().getScopedKernelName(), i.e. [ear=xyz.ear,]jar=abc.jar,StatefulBean -- 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

17 years

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2007