September 2008 - jboss-dev-forums

[Design of JBoss Portal] - Re: sever closing automatically

by thomas.heute＠jboss.com

(Moving to the User forum) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175077#4175077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175077

17 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: sever closing automatically

by prabhat.jha＠jboss.com

Instead of double clicking, can you start from command line? That way you will be able to see error and will probably give an idea what's happening. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175075#4175075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175075

17 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: sever closing automatically

by bangalorejboss

prabath thanks for reply i download server from this site http://www.jboss.org/jbossportal/download/index.html in this website package::JBoss Portal + JBoss AS 4.2.3 ,version::2.7.0.BETA1 , Released::2008-07-30. my java environment version is 1.5 for starting the server i went to bin folder and clicked on the run batch file ,so if i do this i am not able to see the console and console closing by it self automatically with in seconds please help me prabath regards surender View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175064#4175064 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175064

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by adrian＠jboss.org

"timfox" wrote : | One other possibility is to return OK, but not actually persist the branch if it only contains non persistent operations, then if we subsequently get a commit or rollback for that branch on recovery, we can return OK to the commit/rollback even though we can't find the branch. The tx mgr then thinks the transaction was resolved ok, even though the non persistent messages were lost (which is fine anyway). | The important part with returning OK is that you need to persist the XID so you can return it from XAResource.recover() - otherwise you might confuse the transaction manager. It doesn't matter whether there is actually anything behind the XID. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154677#4154677 I guess the real problem occurs when you have a non-persistent send() in a failed transaction commit, i.e.. another branch failed to commit, not you. The TM then calls later recover() and you return nothing. The TM would be well within its rights to assume you already committed (although it could be confused that you lost memory of the XID you said was OK :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175062#4175062 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175062

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by clebert.suconic＠jboss.com

"Tim Fox" wrote : ..we can return OK to the commit/rollback even though we can't find the branch. The tx mgr then thinks the transaction was resolved ok, even though the non persistent messages were lost (which is fine anyway). | If there is no other implications, that's the most optimal solution, as we won't need to record anything on the journal for NonPersistentMessages on that case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175061#4175061 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175061

17 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Changes needed in the produced distribution for jBPM 3.3

by thomas.diesler＠jboss.com

Done. I included the sources and more lib dependencies to the standalone distro. Here you find documentation on how the installer build works. http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3BuildingTheInstaller... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175056#4175056 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175056

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by timfox

"adrian(a)jboss.org" wrote : | Returning "read only" would be the most optimal thing to do. | You then don't record the prepare in the journal. | | However, once you do that the non-peristent message should be removed from memory | or anywhere else you reference it. | The problem with returning RD_ONLY as I see it, is that if I have a tx branch with a bunch of non persistent sends, and return RD_ONLY then commit will never get called, so those messages won't ever get routed in memory to its subscribers (since routing occurs on commit) One other possibility is to return OK, but not actually persist the branch if it only contains non persistent operations, then if we subsequently get a commit or rollback for that branch on recovery, we can return OK to the commit/rollback even though we can't find the branch. The tx mgr then thinks the transaction was resolved ok, even though the non persistent messages were lost (which is fine anyway). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175052#4175052 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175052

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by adrian＠jboss.org

"timfox" wrote : Ah no. We only return RD_ONLY if there the tx is completely empty, including non persistent operations, so yes I think we need to record a blank tx branch in the journal. Returning "read only" would be the most optimal thing to do. You then don't record the prepare in the journal. However, once you do that the non-peristent message should be removed from memory or anywhere else you reference it. If you return "read only" you won't get the commit/rollback notification. That obviously means non-persistent messages won't get redelivered once they've tried to be prepared in a 2PC transaction, even if the eventual outcome of the transaction is a rollback. That is perfectly spec compliant though since there's no guarantee the message would get delivered in the first place, let alone redelivered after a rollback. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175047#4175047 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175047

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by clebert.suconic＠jboss.com

"timfox" wrote : Ah no. We only return RD_ONLY if there the tx is completely empty, including non persistent operations, so yes I think we need to record a blank tx branch in the journal. Besides.. if we choose to store a Prepare Record for an Empty Transaction, we would need the commit as we need the CompletionRecord of the Prepare as we need that in order to reclaim files. So, if you add a PrepareRecord, you need a CommitRecord or you would break reclaiming. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175044#4175044 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175044

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA Recovery on Journal...

by timfox

Ah no. We only return RD_ONLY if there the tx is completely empty, including non persistent operations, so yes I think we need to record a blank tx branch in the journal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175042#4175042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175042

17 years, 7 months

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 September 2008