January 2007 - jboss-dev-forums - Jboss List Archives

[Design of Clustering on JBoss (Clusters/JBoss)] - Use of JGroups Multiplexer in AS 4.2.0

by bstansberry＠jboss.com

Bela, Vladimir and I had a discussion this AM and decided to defer integration of the JGroups multiplexer into AS 4.2.0. Primarily this because we want to ensure the issues discussed in http://jira.jboss.com/jira/browse/JGRP-415 are properly handled before we use the multiplexer in a supported AS release. I will probably add the code hooks to ClusterPartition to support use of the multiplexer (they are already there in JBC 1.4.1), but 4.2.0 will not ship with the multiplexer sar. This approach will leave the potential for 4.2.0 installs to configure the multiplexer once all issues like JGRP-415 are resolved. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004882#4004882 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004882

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1464 - Adding MTOM support to WSDL To Java - Design

by noel.rocher＠jboss.com

anonymous wrote : It's right what you are saying, but in the only (rare) case this becomes a problem is when users types contain base64 types that should be optimized and others that shouldnt at the same time. If this doesnt occur on the same payload then you easily turn off MTOM for that port. | I don't see it as "rare" if you consider that customers are using it as an ID type. I'm talking about big WS users with a lot of webservices (several hundreds) where using attachment or not is an implementation detail (in fact, it's an optimisation required to have decent response times). What they need is to a natural set of functional operations. It's not a good practice to break this for technical reason. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004866#4004866 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004866

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by timfox

Looking through the code, the only place where a replication change with prefix CF_PREFIX = "CF_" is sent is when a connection factory is deployed or undeployed, i.e. in registerConnectionFactory() and unregisterConnectionFactory(). There is no where else in the code where such a replication change is propagated. So you still haven't explained how such a replication event gets propagated when a node crashes..... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004864#4004864 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004864

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by timfox

CF_PREFIX is used when a connection factory is deployed/undeployed. ADDRESS_INFO_KEY is used when a node joins/leaves What you are now saying is that we make a change with prefix CF_PREFIX when a node joins leaves? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004862#4004862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004862

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by timfox

line of code please? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004860#4004860 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004860

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by clebert.suconic＠jboss.com

anonymous wrote : Sigh... You're still missing the point :) | | This line of code is only called when the replication change is a deploy/undeploy of a connection factory: Nope... this place is called also when a node leaves/joins the cluster. Replicator is re-sending the lists when a node leaves... (crash). This is exactly the place where we were doing rebinds before. I just executed ClusterViewUpdate Test, using run test... and I could see the event fired on logs. ClusterViewUpdate would fail if the Connection Factory was not updated after a crash. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004858#4004858 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004858

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by timfox

"clebert.suconic(a)jboss.com" wrote : | | The update is happening on ConnectionFactoryJNDIMapper::onReplicationChange.. | | | Look at the method's implementation, you will see a call to updateClusteredClients: | | | | line 359: endpoint.updateClusteredClients(delArr, failoverMap); | | | Sigh... You're still missing the point :) This line of code is only called when the replication change is a deploy/undeploy of a connection factory: | else if (sKey.startsWith(CF_PREFIX) && originatorNodeID != serverPeer.getServerPeerID()) | { | My question was, can you explain to me how this is called when a node crashes? When a node crashes it won't have the courtesy to undeploy its connection factories first. So how would this get called? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004852#4004852 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004852

19 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Porting a large project from Oracle WorkFlow to JBoss BPM

by fmarchioni

Dear jBoss users, I have to design a new architecture for a large system. At the moment this system is developed using Oracle Application server and Oracle Workflow 2.6 for BPM. Since the number of BPM is huge I'm planning for the first phase of the porting to keep together Oracle for the old BPM and jBoss for the new BPM that will be written. But in the future all BPM must be ported to the new architecture. Anybody has experience with this porting ? And is JBoss BPM tested with a very large number of processes ? Thanks in advance Francesco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004849#4004849 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004849

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by clebert.suconic＠jboss.com

"timfox" wrote : Clebert- | | I just tried to deploy the scoped sar in JBAS and it fails, complaining that it cannot find a property editor for ConnectionFactory::setLoadBalancingFactory. | | Looking at the code, the method setLoadBalancingFactory() takes a LoadBalancingFactory, but the MBean method takes a String. | | I have fixed this, so I can get on with my work. You may want to review my fix since it was very quick. | | This tells me one thing, you added an MBean attribute without adding a corresponding test for it. | | All new functionality needs to have unit tests, so please could you add a test. | | Cheers. I just changed this in top of what Ovidiu had before... Ovidiu had a LoadBalancingPolicy and I placed a LoadBalancingFactory in replacement. I actually started doing this by using a String the same way you changed... but then I realized what Ovidiu had before and I used the same thing. By looking at his code I thought MBeans would take care of it on the XML description (using a default's constructor) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004843#4004843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004843

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by clebert.suconic＠jboss.com

"timfox" wrote : If the client view is being updated, as you say, when a node crashes, then the only other possibility AFAICT is that the connection factory deploy/undeploy even is being triggered when a node crashes. | | Can you explain how this happens? The update is happening on ConnectionFactoryJNDIMapper::onReplicationChange.. Look at the method's implementation, you will see a call to updateClusteredClients: | line 359: endpoint.updateClusteredClients(delArr, failoverMap); | And the LoadBalancingPolicy is being updated at anonymous wrote : | line 348: del.setDelegates(delArr); | This is the very same routine we were using to rebing the ConnectionFactory when the ViewChanged, fired by the ClusteredPostOffice's replicator. We don't undeploy/deploy when a node crashes... we rebing the ConnectionFActory and the place I was telling you. anonymous wrote : I am just saying that creating a new interface is redundant since you are not calling the methods polymorphically. Ah... I see what you mean.... I wanted to do more refactoring on it and have it totally poliymorphically as you were saying but I would need to move some stuff for that. I will take a look if would be possible to refactor it a little bit more. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004840#4004840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004840

19 years, 2 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 January 2007