Re: loadbalancing & failover of stateless beans

2008-06-05 Thread youcef . hilem
Hi,

Indeed, the use of ejb over HTTP with a web load balancer is a very attractive
alternative.
Thank you for this advice.

CDT.


Re: loadbalancing & failover of stateless beans

2008-06-04 Thread Dain Sundstrom

Youcef,

I'd like to reiterate one of David's points.  If you already have a  
web load balancer in production, you can get load balancing today for  
free by simply using our ejb over http protocol.  This has a big  
advantage for your operations staff as they would only have one load  
balancing system to maintain.  Also, it works today :)


Regardless, we definitely need load balancing for the standalone  
protocol.


-dain

On Jun 4, 2008, at 12:03 AM, David Blevins wrote:



On Jun 3, 2008, at 10:36 PM, Youcef HILEM wrote:


Hi David,
I confirm that my request relates only to stateless beans and not  
to stateful beans.


Most of our business services are available for both Web and Swing  
applications. The management of state is supported by these  
applications. We do not use statefull beans.


Sounds like a fantastic application for Tomcat + OpenEJB and  
Collapsed EARs.


For loadbalancing, I think it is enough for us to add a class  
similar to

org.apache.openejb.client.StickToLastServerConnectionFactoryStrategy
(like RandomServerConnectionFactoryStrategy or  
StickToNextServerConnectionFactoryStrategy) and change the method  
getConnectionFactoryStrategy() of class  
org.apache.openejb.client.ServerMetaData.


I take this opportunity to ask whether it is possible to extend the  
method getInitialContext(Hashtable environment) of class  
org.apache.openejb.client.JNDIContext to deal with a list of URLs  
(for key Context.PROVIDER_URL).


That's definitely one of the options I had in mind :)  If that kind  
of approach would work for you, we could plum that in and  
additionally add a way for you to specify the  
ConnectionFactoryStrategy via an additional InitialContext param or  
similar.


If that works for you, can you add a JIRA for it?

Thanks for the request!

-David





Re: loadbalancing & failover of stateless beans

2008-06-04 Thread youcef . hilem
Thanks for your responses.
I created a Jira : https://issues.apache.org/jira/browse/OPENEJB-816


Re: loadbalancing & failover of stateless beans

2008-06-04 Thread David Blevins


On Jun 3, 2008, at 10:36 PM, Youcef HILEM wrote:


Hi David,
I confirm that my request relates only to stateless beans and not to  
stateful beans.


Most of our business services are available for both Web and Swing  
applications. The management of state is supported by these  
applications. We do not use statefull beans.


Sounds like a fantastic application for Tomcat + OpenEJB and Collapsed  
EARs.


For loadbalancing, I think it is enough for us to add a class  
similar to

org.apache.openejb.client.StickToLastServerConnectionFactoryStrategy
(like RandomServerConnectionFactoryStrategy or  
StickToNextServerConnectionFactoryStrategy) and change the method  
getConnectionFactoryStrategy() of class  
org.apache.openejb.client.ServerMetaData.


I take this opportunity to ask whether it is possible to extend the  
method getInitialContext(Hashtable environment) of class  
org.apache.openejb.client.JNDIContext to deal with a list of URLs  
(for key Context.PROVIDER_URL).


That's definitely one of the options I had in mind :)  If that kind of  
approach would work for you, we could plum that in and additionally  
add a way for you to specify the ConnectionFactoryStrategy via an  
additional InitialContext param or similar.


If that works for you, can you add a JIRA for it?

Thanks for the request!

-David



Re: loadbalancing & failover of stateless beans

2008-06-03 Thread Youcef HILEM
Hi David,
I confirm that my request relates only to stateless beans and not to stateful 
beans.

Most of our business services are available for both Web and Swing 
applications. The management of state is supported by these applications. We do 
not use statefull beans.

For loadbalancing, I think it is enough for us to add a class similar to 
org.apache.openejb.client.StickToLastServerConnectionFactoryStrategy
 (like RandomServerConnectionFactoryStrategy or 
StickToNextServerConnectionFactoryStrategy) and change the method 
getConnectionFactoryStrategy() of class 
org.apache.openejb.client.ServerMetaData.

I take this opportunity to ask whether it is possible to extend the method 
getInitialContext(Hashtable environment) of class 
org.apache.openejb.client.JNDIContext to deal with a list of URLs (for key 
Context.PROVIDER_URL). 






Re: loadbalancing & failover of stateless beans

2008-06-03 Thread David Blevins


On Jun 3, 2008, at 3:02 AM, [EMAIL PROTECTED] wrote:



Hi,
Can we expect an implementation in the next delivery. It is an  
essential feature

for us.


Hi Youcef,

Are you sure you mean failover for stateless beans and not stateful?   
Getting failover for stateless is pretty trivial and we have a little  
bit of client logic in that area.  Essentially the client code is  
already capable of rolling over to other servers just there's no real  
way to *configure* the list of available servers.  We can easily add  
something in this regard.


Loadbalancing might be more difficult.  If you have an http load  
balancer, we could likely fix up the ejbd over http protocol to  
support it which would be the most robust option.


If you can describe your desired topology would be a great start.

-David