May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBCACHE-471) Handle JGroups MERGE

by Galder Zamarreno (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-471?page=comments#action_12362839 ] Galder Zamarreno commented on JBCACHE-471: ------------------------------------------ Yeah, you are right. What I was trying to say is that, imo both tasks fall under the same umbrella, which how to resolve conflicts. Whether one rollbacks the transaction or the other one does something more sophisticated as merging, is just part of the resolution to the conflict itself. It'd be nice to provide a common structure for both. Thoughts? > Handle JGroups MERGE > -------------------- > > Key: JBCACHE-471 > URL: http://jira.jboss.com/jira/browse/JBCACHE-471 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Fix For: 2.1.0.GA > > > When JGroups needs to do a merge due to a temporary break in the group structure, JGroups does not handle the merging of data. This is usually left up to the application to handle. > JBossCache should support pluggable merge policies, we could provide some simple merge policies and allow users to write their own. > 1. Evict on merge policy - when a merge occurs, evict the entire in-memory state. Useful for Hibernate or when used with a shared cache loader. > 2. Other merge algos ... ? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-46) scheduler

by Matt Read (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-46?page=comments#action_12362837 ] Matt Read commented on JBPM-46: ------------------------------- The SchedulerServlet was available in 3.1.4 but no longer seems to be in 3.2.GA, am I missing something? The basis for my Quartz implementation will be to create an implementation of SchedulerService and SchedulerServiceFactory, can you confirm that is a sensible approach? Thanks, Matt. > scheduler > --------- > > Key: JBPM-46 > URL: http://jira.jboss.com/jira/browse/JBPM-46 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM 3.0 alpha 4 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > implement the scheduler functionality + a simple servlet that acts as a cron-task to check for due jobs on regular intervals. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-727) @Depends annotation does not work in EJB3 Embeddable release

by Magesh Kumar B (JIRA)

@Depends annotation does not work in EJB3 Embeddable release ------------------------------------------------------------ Key: EJBTHREE-727 URL: http://jira.jboss.com/jira/browse/EJBTHREE-727 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Magesh Kumar B The ServiceOne, ServiceTwo and ServiceThree example given in the EJB3.0 documentation does not work when testing with the embeddable release -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-959) Potential issue in MDB reconnection

by Tim Fox (JIRA)

Potential issue in MDB reconnection ------------------------------------ Key: JBMESSAGING-959 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-959 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.SP2 Need to investigate whether there is an issue in MDB reconnection after connection failure. Need to investigate 1) How reconnection works in a non clustered environment - which CF to specify. 2) How reconnection works in a clustered environment with only one member 3) How reconnection works in a clustered environment. 4) MDBs shouldn't be using a clustered CF See forum rerefernce -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3985) EJB3 hot redeployment causes a permanently locked file handle

by Vladimir Ralev (JIRA)

EJB3 hot redeployment causes a permanently locked file handle ------------------------------------------------------------- Key: JBAS-3985 URL: http://jira.jboss.com/jira/browse/JBAS-3985 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB3 Affects Versions: JBossAS-4.0.5.GA Environment: Windows XP Pro, JRE 1.5_9, JBoss AS 4.0.5.GA, EJB3.CR9.patch1 Reporter: Vladimir Ralev Assigned To: Dimitris Andreadis I am not sure which component is responsible for the bug, but since it happened with an ejb3-jar I am rising it here. If it doesn't belong here please forward it the right place. 1. I copy titan.jar to the deploy folder -> the server deploys the ejb3 application and says ejb running 2. I delete titan.jar from the deploy folder -> the server says that the app is undeployed 3. I copy titian.jar in the deploy folder again -> the server deploys the ejb3 application and says ejb running again (everything seems ok for now, here comes the problem) 4. I try to delete titan.jar from the deploy folder -> I get a windows explorer error message saying that the file is in use and can't be deleted. When I checked with process explorer which process is using the file it turned out it's the java.exe process (the server didn't release the handle?). This doesn't not occur on Linux! -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4055) Hot Deploy doesn't work in JBoss 5.0.0.Beta1

by Charles Crouch (JIRA)

Hot Deploy doesn't work in JBoss 5.0.0.Beta1 -------------------------------------------- Key: JBAS-4055 URL: http://jira.jboss.com/jira/browse/JBAS-4055 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Charles Crouch Fix For: JBossAS-5.0.0.Beta2 Hot Deploy doesn't work in JBoss 5.0.0.Beta1 -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Commented: (JBCACHE-471) Handle JGroups MERGE

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-471?page=comments#action_12362822 ] Manik Surtani commented on JBCACHE-471: --------------------------------------- Somehow for optimistic workspace merging I think the correct approach should be a tx rollback since each workspace is a clearly defined and identifiable unit of work. In the case of a JGroups merge, both pieces may contain multiple unidentifiable transactions which cannot be rolled back or resolved, and hence the need for a merge. > Handle JGroups MERGE > -------------------- > > Key: JBCACHE-471 > URL: http://jira.jboss.com/jira/browse/JBCACHE-471 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Fix For: 2.1.0.GA > > > When JGroups needs to do a merge due to a temporary break in the group structure, JGroups does not handle the merging of data. This is usually left up to the application to handle. > JBossCache should support pluggable merge policies, we could provide some simple merge policies and allow users to write their own. > 1. Evict on merge policy - when a merge occurs, evict the entire in-memory state. Useful for Hibernate or when used with a shared cache loader. > 2. Other merge algos ... ? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4229) HASingletonController doesn't handle "split brain" correctly.

by Adrian Brock (JIRA)

HASingletonController doesn't handle "split brain" correctly. ------------------------------------------------------------- Key: JBAS-4229 URL: http://jira.jboss.com/jira/browse/JBAS-4229 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.3 SP1 Reporter: Adrian Brock Assigned To: Brian Stansberry The HASingletonController doesn't understand the "split brain" problem. Take for example a JBossMQ destination (queue) which needs to be "restored" from the database when a new singleton is elected. The scenario goes as follows: STEP1 (original state): cluster=server1, server2 master=server1 STEP2 (unplug server1 from the network): cluster=server2 master=server2 server2 will now restore the queue from the database BUT! server1 has the view cluster=server1 master=server1 STEP3 (plug server1 back into the network) cluster=server1, server2 master=server1 We are back to the original state, but since server1 thinks it never left the cluster, it doesn't restore the changes (from the database) that server2 made to the queue between STEP2 and STEP3. This is because it doesn't restart the HASingleton on server1. If there was a third server (server3) to abitrate this wouldn't be a problem. Both server2 and server3 would agree that server2 is the master and that server1 has left and must rejoin. There needs to be some extra processing in the "merge" when two masters agree to form a cluster that ensures that whoever they elect as the new master gets its HASingleton(s) restarted. Otherwise, it won't have the up-to-date state from the other master. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1064) PojoCacheException should declare a serialVersionUID

by Brian Stansberry (JIRA)

PojoCacheException should declare a serialVersionUID ---------------------------------------------------- Key: JBCACHE-1064 URL: http://jira.jboss.com/jira/browse/JBCACHE-1064 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 2.0.0.CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0.CR2 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-856) Version history can skip true ordering

by Michael Neale (JIRA)

Version history can skip true ordering -------------------------------------- Key: JBRULES-856 URL: http://jira.jboss.com/jira/browse/JBRULES-856 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 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 May 2007