October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-598) Simplify FLUSH

by Vladimir Blagojevic (JIRA)

Simplify FLUSH -------------- Key: JGRP-598 URL: http://jira.jboss.com/jira/browse/JGRP-598 Project: JGroups Issue Type: Task Affects Versions: 2.5, 2.4 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.6 #1 Superfluous FLUSH-COMPLETED phase ? -------------------------------------- It seems we don't need the FLUSH-COMPLETED phase, it is sufficient for the FLUSH leader to do a START-FLUSH and wait for all FLUSH-OK messages. Why ? Because the reconciliation protocol will reconcile messages before the view installation (or state transfer). Example: {A,B,C}. E sends message M and then crashes. Only C receives M. - A does a START-FLUSH - B and C send a FLUSH-OK back to A. This means that all multicasts from B will be seen by A *before* B's FLUSH-OK is received, and all multicasts from C will be seen by A before C's FLUSH-OK is received by A. HOWEVER, C will not necessarily send M to A before sending the FLUSH-OK message. This is only done through the reconciliation protocol ! - FLUSH-COMPLETED can be removed, the digest that's part of FLUSH-COMPLETED has to moved to FKLUSH-OK phase. - FLUSH-OK is unicast *not* multicast. #2 Superfluous STOP-FLUSH-OK phase ? ------------------------------------ Why do we need the acks here ? JGroups guarantees the STOP-FLUSH message is delivered to all non-faulty members, so why wait fr the STOP-FLUSH-OK ? If we make STOP-FLUSH *OOB* (JGRP-337), then this should work ! We can get rid of STOP-FLUSH-OK !! Just send STOP-FLUSH as OOB multicast. Note: this requires the concurrent stack, so possibly check for concurrent stack. Throw an exception if concurrent stack is not present when FLUSH is used. So, these changes cannot be applied to 2.4, only to 2.5 and 2.6. #3 Timeouts ----------- - ClientGmsImpl: has a hard coded timeout of 4 secs - CoordGmsImpl also has a timeout for block() - If we *need* timeouts, we should get them from the FLUSH protocol ! CoorsGmsImpl.startFlush() should *not* have a timeout, this should be in FLUSH itself. startFlush() should block forever, until it gets the ack #4 Spurious FLUSH-OK in the diagram ----------------------------------- In the JOIN diagram, probably also in the state transfer diagram -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-25) Microcontainer integration

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ] Tim Fox updated JBMESSAGING-25: ------------------------------- Fix Version/s: 2.0.0 Alpha (was: 2.0.0 Beta 1) > Microcontainer integration > -------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Andy Taylor > Priority: Critical > Fix For: 2.0.0 Alpha > > Attachments: JBMESSAGING-26.tar > > > We should POJOify all our current MBean services and allow the microcontainer to enforce dependencies. > The microcontainer can also provide MBean interfaces transparently if needed. > This task is critical in allowing an "embedded JBM". > This is critical to kick start ESB. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-406) Persistence refactoring

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ] Tim Fox updated JBMESSAGING-406: -------------------------------- Fix Version/s: 2.0.0 Alpha (was: 2.0.0 Beta 1) > Persistence refactoring > ----------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 2.0.0 Alpha > > > Need to refactor persistence so each node has its own storage. > We should provide at least three local persistence manager configs: > 1) JDBC local pm that works out of the box with HSQL - not recommended for production. > 2) BDB based pm that customers need to download - recommended for best performance. > Should optimise for the SAN use case. > Need to consider whether we need to support replication for failover too. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-314) Extend messaging core to be fully functioning

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-314?page=all ] Tim Fox updated JBMESSAGING-314: -------------------------------- Summary: Extend messaging core to be fully functioning (was: Ensure Messaging core has no dependencies on the JMS facade) Original Estimate: (was: 2 days) Remaining Estimate: (was: 2 days) Description: The scope of messaging core should be extended out to the client side and JMS dependencies should only exist on thin layer on the client side. Core should be a fully functioning messaging system with useable clients. (was: Messaging core still has some dependencies on the jms facade. These should be factored out.) > Extend messaging core to be fully functioning > --------------------------------------------- > > Key: JBMESSAGING-314 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-314 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 2.0.0 Beta 1 > > > The scope of messaging core should be extended out to the client side and JMS dependencies should only exist on thin layer on the client side. Core should be a fully functioning messaging system with useable clients. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-373) Different persistance destinations for different JMS destinations

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-373?page=all ] Tim Fox closed JBMESSAGING-373. ------------------------------- Resolution: Rejected Rejected since JBM 2 will use local storage > Different persistance destinations for different JMS destinations > ----------------------------------------------------------------- > > Key: JBMESSAGING-373 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-373 > Project: JBoss Messaging > Issue Type: Feature Request > Affects Versions: 1.0.0, 1.0.1.CR1 > Reporter: Milena > Fix For: 2.0.0 Beta 1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > We need to store the messages from different queues into a different tables, ot at least to separate them somehow. > This is not possible with the current JBOSS Messaging as I was told. > The motivation behind is that since we have a very high load on some of the queues, the persistance table appears a bottleneck for the rest of the messaging. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-406) Persistence refactoring

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ] Tim Fox updated JBMESSAGING-406: -------------------------------- Summary: Persistence refactoring (was: Enabled local persistent storage per node) Description: Need to refactor persistence so each node has its own storage. We should provide at least three local persistence manager configs: 1) JDBC local pm that works out of the box with HSQL - not recommended for production. 2) BDB based pm that customers need to download - recommended for best performance. Should optimise for the SAN use case. Need to consider whether we need to support replication for failover too. was: Implement non shared file based persistent store. Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this. Also look at HOWL. http://howl.objectweb.org/ > Persistence refactoring > ----------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 2.0.0 Beta 1 > > > Need to refactor persistence so each node has its own storage. > We should provide at least three local persistence manager configs: > 1) JDBC local pm that works out of the box with HSQL - not recommended for production. > 2) BDB based pm that customers need to download - recommended for best performance. > Should optimise for the SAN use case. > Need to consider whether we need to support replication for failover too. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1084) AS5 integration code should be in AS workspace

by Anil Saldhana (JIRA)

AS5 integration code should be in AS workspace ----------------------------------------------- Key: JBMESSAGING-1084 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1084 Project: JBoss Messaging Issue Type: Task Components: AS Integration Reporter: Anil Saldhana Assigned To: Tim Fox It is important that the AS integration code (JBoss AS) stays in the AS workspace. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4879) TECH REVIEW: Installation Guide - Chapter 6 -

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - Chapter 6 - ----------------------------------------------- Key: JBAS-4879 URL: http://jira.jboss.com/jira/browse/JBAS-4879 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Attached is an Open Office 2.0 Document contain chapter 6 of the Installation Guide. 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. -- 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, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1075) org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds)

by Jo Geraerts (JIRA)

org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds) ---------------------------------------------------------------------------------------------------------- Key: JBPM-1075 URL: http://jira.jboss.com/jira/browse/JBPM-1075 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2, jBPM jPDL 3.2.1, jBPM jPDL 3.2, jBPM jPDL 3.2 beta 2, jBPM 3.1.4 Environment: java version "1.5.0_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05) Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing) Reporter: Jo Geraerts Assigned To: Tom Baeyens I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds) with a List with 0 entries. So we end up in org.jbpm.db.TaskMgmtSession.findTaskInstances(List actorIds) with the same List ( with 0 entries) I get this Exception: 10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s ubtree [ select distinct ti from org.jbpm.taskmgmt.exe.PooledActor pooledActor join pooledActor.taskInstances ti where pooledActor.actorId in ( ) and ti.actorId is null and ti.isSuspended != true and ti.isOpen = true ] -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4850) TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment

by samson kittoli (JIRA)

TECH REVIEW: Server Configuration Guide - Chapter2 - Deployment --------------------------------------------------------------- Key: JBAS-4850 URL: http://jira.jboss.com/jira/browse/JBAS-4850 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Server Configuration Guide Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/ -- 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, 11 months

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007