Hi Jin,
Please share your clb xml. Also share application server logs. In case
CLB is not providing any response, then some error must be logged.
Thanks,
Kshitiz
On Monday 08 March 2010 02:26 PM, Jin Yao wrote:
> Hi Kshitiz,
> Thank you.
> But actually I have tried convert the app into a converged app
> （sip&web） by including a empty sip.xml , the CLB not works either.
> We try to login our application, the expected behavior is that the app
> received error response(authentication failed), then the browser will
> display some error message to end user.
> but actually we could not get error response, no error message
> displayed on the browser.
> While we disable LB on one PL instance (which mean just one PL work),
> then it works correctly, the error message displayed!
> But, to make it more clear, for pure web application(including session
> based), nothing need to do to enable CLB ,except to make sure the PL
> instance active and LB enabled , if the sticky round robin algorithm
> works well, just the web container to auto detect and apply the
> correct CLB algorithm, right?
>
> Br,Jin
>
> ------------------------------------------------------------------------
> *From:* Kshitiz.Saxena_at_Sun.COM [mailto:Kshitiz.Saxena_at_Sun.COM]
> *Sent:* 2010年3月8日 15:50
> *To:* dev_at_glassfish.dev.java.net
> *Subject:* Re: Need you help on CLB
>
> Hi Jin,
>
> Yes, you are correct about requests belonging to pure web applications
> being distributed using sticky round robin algorithm. All new requests
> will be distributed in round robin manner across active(healthy +
> enabled) instances. All subsequent requests belonging to a
> session(i.e. first request created session) will be send to instance
> which serviced first request. This behavior will be followed until and
> unless that instance goes down and subsequent requests need to be
> failed over.
>
> DCR is applied for pure sip and converged application. To convert pure
> web application to converged application, you can include empty sip.xml.
>
> From stats you provided, it looks like all four requests(stats
> *TotalIncomingHttpRequests**BE*) were serviced by same backend. Even
> though both FE got 2 requests each(stats
> *TotalIncomingHttpRequests**F**E*), they were eventually serviced by
> PL-2_4.
>
> Thanks,
> Kshitiz
>
> On Monday 08 March 2010 10:27 AM, Jin Yao wrote:
>> Hi ,
>> We 're developing web application on SGCS, we encounter problems on
>> data centric, it seems the data-centric not works
>> This is our dcr file
>> We installed dcr using the following commands
>> SC_2_1# asadmin set-dcr-file --clbname traffic_lb
>> /home/wuigm/data-centric-rules.xml
>> SC_2_1# asadmin set
>> traffic-config.availability-service.converged-load-balancer.auto-commit=true
>>
>> We can see the file in console page
>> But the CLB seems not work.
>> If try to login WUIGM 4 times, In PL monitor log,
>> *On PL-2_4 **TotalIncomingHttpRequests**BE *count value is 4
>> *TotalIncomingHttpRequests**F**E** *value is 2
>> On *PL-2_3 **TotalIncomingHttpRequests**B**E** *count value is 0
>> *TotalIncomingHttpRequests**F**E** *value is 2
>> Do you know, What the problem is?
>> BTW: It's a pure web application! I have find some thing about CLB.
>> it's said "HTTP and HTTPS messages belonging to pure web
>> applications, the converged load balancer uses a *sticky round robin*
>> algorithm" ,then what's the *sticky round robin*
>> what should web application do to enable this
>> Does the DCR file not work for pure web application?
>> Thanks in advance!
>> Br,Jin