Zeus User Community
Independent community for users of Zeus Technologies products.
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
September 05, 2010, 11:07:13 AM


Login with username, password and session length


Pages: [1]
  Print  
Author Topic: weblogic t3 connection  (Read 2043 times)
siddiqut
Member
**
Posts: 5


View Profile
« on: January 11, 2010, 05:40:38 PM »

Hi,

We are looking to use ZXTM 5.1 as a load balancer for our weblogic 10.x clusters.
The weblogic cluster has ejbs deployed which are accessed by java clients using the t3 (weblogic proprietary tcp based protocol).

Issues so far:

1.Zeus does not load balance withing the weblogic cluster: Weblogic cluster has 2 servers. I configured both as nodes in the zeus pool p1.
Now I use the zeus virtual server (with p1) for t3 based access to the cluster. The connection request always goes to one of the member of the pool for the life of the client.

Client url is : t3://zvs1:p


I think the actual tcp connection is being kept alive by weblogic, even though the client  is calling Context.close().
Any way to bypass/correct this.

Load balancing does work if I configure 2 virtual servers/pools with identical (different url) info. and  client uses both virtual servers for the lookup:
t3://zvs1,zvs2:p

But this is not optimal as client url has to change every time the no. of managed servers in weblogic cluster changes.



Many thanx for your help.



Logged
karthy
Administrator
Wizard
*****
Posts: 78


karthy


View Profile WWW Email
« Reply #1 on: January 13, 2010, 02:52:37 PM »

Hi

I do not believe, that there is an easy solution to your challenges. I have loadbalanced T3 connections quite a few times, and the issue is, that the connections is being reused by rmi calls and in essence never terminated. T3 is not very friendly toward loadbalancing in general. The ideal solution is to not use t3, but it might have quite a performance impact for your system and weblogic's implementation of IIOP have gives us some challenges (but to be fair, this was with an elder version of weblogic - I do not know the current state).

I'm afraid, that the best solution is to do as you propose in step 2...

t3 is not an open protocol, so it is not easy to do something "smart"...

Good luck,
Karsten
Logged
siddiqut
Member
**
Posts: 5


View Profile
« Reply #2 on: January 13, 2010, 08:07:10 PM »

Hi Karsten,

Many thanx for your reply.

One follow up question pls.

I also want to achieve weblogic cluster level failover thru zeus.

So lets say weblogic cluster c1 with 2 managed servers fails (all managed servers fail). I want cluster c2 to take over (for t3 connections).

What seems to work is:
defining a zeus pool which includes members of both c1 and c2 ,
giving cluster c1 members higher priority in the pool definition and
setting Minimum number of highest-priority active nodes set to 1.

This also achieves load balancing (between members of c2)  on failover.

I had tried defining the c2 members as backup pool for c1 members pool. But that doesn't achieve  loadbalancing on failover.

Any suggestions/recommendations/alternatives pls.

Thanx,
Tajdar



Logged
karthy
Administrator
Wizard
*****
Posts: 78


karthy


View Profile WWW Email
« Reply #3 on: January 15, 2010, 08:26:20 AM »

Hi


I had tried defining the c2 members as backup pool for c1 members pool. But that doesn't achieve  loadbalancing on failover.


Hmm.... I do not really understand this. Having c2 defined as backup pool for c1 would be my recommendation and I dot not understand why you do not achieve loadbalancing among c2's members? You should get loadbalancing for among c2 members as well as c1 members unless you have some kind og session persistence defined on the c2 pool?

regards,
Karsten
Logged
siddiqut
Member
**
Posts: 5


View Profile
« Reply #4 on: January 15, 2010, 03:04:09 PM »

Hi Karsten,


Yes, when failing over to c2, looks like all calls go to one of the members of c2. c2 has 2 members defined. 

I'm not sure  on session persistence. This is all using the weblogic t3 protocol.

Thanx,
Tajdar



Logged
karthy
Administrator
Wizard
*****
Posts: 78


karthy


View Profile WWW Email
« Reply #5 on: January 15, 2010, 03:53:07 PM »

Hmm...This should not happen. How are your load balancing defined for pool c2? And have you defined any session persistence for pool c2?

Karsten
Logged
siddiqut
Member
**
Posts: 5


View Profile
« Reply #6 on: January 15, 2010, 04:10:46 PM »

Hi Karsten,

Load balancing algorithm for c2 is defined as  Round robin.
No session persistence.

I think since this is all t3 based, limitation of defining 2 virtual servers to get load balancing to work (for c1 in the first place) might be coming into play  ?

Or maybe I am missing something ?

Many thanx for your help.

-Tajdar
Logged
duhhauch
Newcomer
*
Posts: 2

281145561 Idioria@all-craigs.com
View Profile
« Reply #7 on: March 16, 2010, 12:33:17 PM »

Hi,
I am converting an legacy application which has webservice functionality.

One of the webservice class uses spring managed beans.

My question is:How will get my spring managed beans in the webservice  POJO.

I am not using AXIS.Webservice is based on Weblogic8.1 SP3 RPC style.

Thx
Anan
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Images and graphics used with permission of Zeus Technology.
Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM