February 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBossXB] - Re: 2 root elements question

by jeff.zhang

Thanks Alex. Please noticed me when we have multi-class binding resolver. And do you have plan to release 1.0.0CR17 this week? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208820#4208820 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208820

17 years, 1 month

1
0
0 / 0

[Design of JBoss Labs] - Re: JBoss Community Leaders polls not working

by rayme

A special notice about the status of the JBoss Community Recognition Awards: http://jboss.org/jbcrupdate View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208805#4208805 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208805

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Journal Clean up / Compactor

by clebert.suconic＠jboss.com

"timfox" wrote : Tried to ping you on IRC but you'd gone. | | Anyway, after some reflection I think you're idea of moving those records that cause the "linked list" problem in memory is good. Note however you only need to change the JournalFile objects and counts in memory - you don't need to change anything on disk. Doing so will make normal reclaim kick in and delete the files. | The idea was to update the file on disk, + change the counters in memory, so case there is a reload, after the linked files were deleted, the data would be preserved. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208788#4208788 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208788

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Journal Clean up / Compactor

by timfox

Tried to ping you on IRC but you'd gone. Anyway, after some reflection I think you're idea of moving those records that cause the "linked list" problem in memory is good. Note however you only need to change the JournalFile objects and counts in memory - you don't need to change anything on disk. Doing so will make normal reclaim kick in and delete the files. Be careful though to make sure if you delete one file you delete them all - or you might end up deleting the files with deletes in them, leaving the adds! On top of that, we also need to solve the other reclaiming issue I talked of before. Undeleted records in a file surrounded by deleted records. This can only be solved by compaction. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208776#4208776 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208776

17 years, 1 month

1
0
0 / 0

[Design of JBossCache] - Re: Removing non-existing key in UnversionedNode causes data

by AlexFu.Novell

Thanks. "manik.surtani(a)jboss.com" wrote : Never mind, I have created it - JBCACHE-1474 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208757#4208757 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208757

17 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: Concurrency in jBPM4

by roschmel

@Bernd We have a clustered environment where we have following resources: 1) The database transaction for jbpm to an oracle 2) Another or mapping technology to a legacy database which is transacted but non xa 3) Various WebService calls which are causing operation in external systems and cannot be rolled back and we might get other stuff to.... (its an EAI scenario). We are using a JTA Manager but we do not use XA. And I know - perhaps an ESB would fit better into it - but for different reasons its currently not an option. I will try to sum up my issues to make it more clear: 1) The jBPM throws StaleObjectExceptions when one ProcessInstance is getting Signals concurently. When your process is using non transacted (or not XA capable) resources this might cause problems because you cannot just retry easily. Our solution: We replaced the CommandService Implementation with our own implementation managing clusterwide locks on process instances. 2) When you use non transacted (or non XA capable) resources you might want to have more fine granular transaction demarcation. Therefore you can use async="true" but this will again increase the possiblity for 1) at least with the source up to 3.2.3 (thx alex) Our solution: We are using BMT and implemented an ActionHandler which can commit the transaction during process execution - but we need a dirty code hack for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208747#4208747 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208747

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Journal Clean up / Compactor

by clebert.suconic＠jboss.com

Yes.. but there are two ways of doing this: I - doing only a cleanup on the file, what would only remove the records that are causing issues, and letting reclaiming to work. Which is a very simple approach to implement. II - Doing a full compactation of files, merging multiple files, what will have more complexity, and it would require a little bit more of time to implement. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208745#4208745 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208745

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Journal Clean up / Compactor

by timfox

Right, but that's the job of the compactor - to physically remove records that have been deleted - then the problem disappears. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208741#4208741 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208741

17 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: Concurrency in jBPM4

by roschmel

@Alex: Thanks for the tip - I just had a look at it. It seems quite interesting solution. Two issue are comming to my mind, when I look at the code: If you have multiple excluive jobs which should be executed concurrently I think you will 1) get stale object exception in the ExecuteJobCommand because the will overwrite the lockowner each other and 2) change the transaction behaviour because you execute multiple jobs with the ExecuteJobsCommand in one transaction. This might have unwanted side effects. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208740#4208740 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208740

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Journal Clean up / Compactor

by clebert.suconic＠jboss.com

So... if you keep a single record on any file... You can have 1 million adds, 1 million deletes .... and you will have about thousand files on the journal, when you only needed 1. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208739#4208739 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208739

17 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2009