October 2006 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Server side HA and failover

by timfox

I would like to use this thread for discussing the implementation of server side failover and HA. (As opposed to the other thread which concentrates more on the client side). I am particularly interested in the following questions: 1) How much of AS server side failover code we can re-use. (Brian?) 2) How this is going to work in detail. How can we maintain a consistent mapping between nodes and their failover nodes. Is this maintained in the JGroups group state, or can we just use the JGroups view? 3) How we can ensure that the client fails over to the same server as the server fails over onto. 4) How we ensure that the client doesn't start sending requests to it's failover server after it has failed over, before the server has failed over. 5) We need to make sure we tackle any other race conditions and edge cases. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976612#3976612 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976612

19 years, 6 months

1
0
0 / 0

[Other JBoss Development Design] - Re: run.sh to launch JBoss in background

by ips

Sure, I'll add support for trapping 1, 10, and 15, and test it on RHEL and Cygwin. If it appears to be working, I'll attach a patch to JBAS-3748. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976606#3976606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976606

19 years, 6 months

1
0
0 / 0

[Other JBoss Development Design] - Re: run.sh to launch JBoss in background

by dimitris＠jboss.org

Actually 10 is the exit code of jboss when restarted, so the loop can kick in, so we don't need to catch this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976602#3976602 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976602

19 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: SLBs cyclic dependencies

by bill.burke＠jboss.com

use @IgnoreDependency to break the cyclic chain. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976600#3976600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976600

19 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: SLBs cyclic dependencies

by bill.burke＠jboss.com

19 years, 6 months

1
0
0 / 0

[Other JBoss Development Design] - Re: run.sh to launch JBoss in background

by dimitris＠jboss.org

I think trap'ing 1 10 15 would be Ok. Ian, you look quite confident, so do you want to test this and attach a patch to the case. I wonder if this will work in cygwin. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976598#3976598 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976598

19 years, 6 months

1
0
0 / 0

[Other JBoss Development Design] - Re: run.sh to launch JBoss in background

by ips

+1 - I like it because it encapsulates all the complexity in run.sh, and the user can simply treat the run.sh process as if it is the JBoss process itself. So we'd have to add a line like the following to run.sh for each signal we want to relay: trap "kill -1 $JBOSS_PID" 1 I guess, at a minimum, we'd want to support 1 (HUP), 10 (JBoss restart), and 15 (TERM). Or you could use something like the following to support all signals: i=0 while [ "$i" -le 64 ]; do [ "$i" -ne 9 ] && [ "$i" -ne 19 ] && trap "kill -$i $JBOSS_PID" $i i=`expr $i + 1` done Note, I skip 9 (KILL) and 19 (STOP), because these can't be trapped, and POSIX impls of trap are not required to even allow them as args. I'm not sure if the max signal number on Solaris, HP-UX, etc. is 64, as it is on Linux, so some testing would be required there in order to make sure the above while loop is portable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976595#3976595 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976595

19 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Jars for Drool integration examples

by jeffdelong

In order to run the RulesAssignmentHandler and RulesActionHandler examples that I have created I needed to add the following Drools related jars to the classpath: antlr-3.0ea8 commons-jci-core-1.0-406301 commons-jci-eclipse-3.2.0.666 core-3.2.0.666 drools-compiler-3.0.4 drools-core-3.0.4 stringtemplate-2.3b6 Most of these are required because the rules are compiled at run time. This should be added to JBPM_REPO. Jeff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976594#3976594 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976594

19 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Reminder, No lazy loading in the UMD

by jason.greene＠jboss.com

Hi Everyone, Last night I stumbled across this: | public OperationMetaData getOperation(Method method) | { | OperationMetaData opMetaData = methodCache.get(method); | if (opMetaData == null) | { | for (OperationMetaData aux : operations) | { | if (aux.getJavaMethod().equals(method)) | { | methodCache.put(method, aux); | opMetaData = aux; | break; | } | } | } | return opMetaData; | } | As a general reminder, we can't use lazy loading in the UnifiedMetaData model because it is shared across threads. If we need to cache something, it needs to be done in eagerInitialize() -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976588#3976588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976588

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Trailblazer out-of-the-box experience

by mark.little＠jboss.com

Thanks for the feedback Tom. Sounds like we need to register a few issues in JIRA then once we know what the problems are. Cheers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976587#3976587 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976587

19 years, 6 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 October 2006