Here's a tricky question for you. You say 'when the cluster is configured'....a few years ago I looked into setting up a Tomcat Cluster...the point of setting up a cluster of course is to allow for session sharing between different Tomcat instances, so that if one goes down, the other already has the session, and there is no need to re-establish a login session....but after reading enough docs, I discovered that Mid-Tier CANNOT be setup in session sharing...I seem to recall it being because of certain objects not being serializable, or something along those lines...but, to the best of my knowledge, that hasn't changed.....so, long story short
Are you trying to setup Session Sharing in a Web Sphere Cluster?...if the answer is Yes...then that I believe is your problem, and you can't do it...so they need to NOT be clustered, but instead, two stand alone servers, with a load balancer (with sticky bits) in front of them.... On Tue, Jul 30, 2013 at 2:08 PM, <[email protected]> wrote: > That is the real interesting part. > > when we are in the clustered setup, we see that the redirection to the > Home Page is done (results of the successful login), we see the cooking > being assigned, the browser loading the home page, but the response is the > logon page. > > Now if we remove the cluster, same steps are showing, but the response is > the correct Home Page > > I am not a web expert (far from it). So I really don't understand what > the heck is going on. I am told that the sticky bit (sticky session) is > configured between F5 and Web server. This is a single app server so > nothing to configure on the Mid Tier for this. > All that is supposed to be configured on the Mid Tier seems to be done > properly (and it is done exactly the same on the Solaris environment) > All that is supposed to be configured on the Websphere8 seems to be done > properly (and it is done exactly the same on the Solaris environment) > > Thank you, > > Pascale Sterrett > Kenavo ar wech all > > > > > [email protected] > Sent by: [email protected] > 07/30/2013 12:56 PM > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Re: Midtier 7.6 sp 4 on websphere 8 is not working, any suggestions? > > > > > > > ** > Pascale, > If you run a Fiddler log for both scenarios > 1 - Direct to the Web Server > 2 - Through the Load Balancer > > What sort of differences do you see? > > > On Tue, Jul 30, 2013 at 1:51 PM, <[email protected]> wrote: > Deyon and the list > > We have some additional information about this issue. May be someone on > the list can help us both with this. We have similar issues. > > we have 2 web servers 2 Mid Tiers 1 app server. > > AIX > Websphere8 > Mid Tier 7.6.04 SP4 > > ARS 7.6.04 SP4 (Win 2003) > > When we have the server in clustered we get to the logon page, and loop > constantly. The logs shows that the Home Page (or an pages) gets properly > called, but the logon page is what gets displayed all the time. We did > all the recommended configuration. > If we connect to one set at a time it works fine. > > Now to make things even more complex. We have another environment that is > exactly the same > 2 web servers 2 Mid Tiers 1 app server (same app server), except it is > running on Solaris > > Solaris > Websphere8 > Mid Tier 7.6.04 SP4 > > ARS 7.6.04 SP4 (Win 2003) > > That second environment works perfectly fine without any issues. > > Any ideas? Would that be due to the Mid Tier 7.6.04 SP4 build for AIX > having the issue? or the Websphere 8 AIX build? Or no clue and we need to > keep on going crazy trying to get help finding a resolution on this since > both BMC and IBM are pointing fingers at each others. > > Thank you, > > Pascale Sterrett > Kenavo ar wech all > > > > > [email protected] > Sent by: [email protected] > 07/16/2013 04:21 PM > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Re: Midtier 7.6 sp 4 on websphere 8 is not working, any suggestions? > > > > > > > revised. > > > Pascale/List > > I'm still experiencing this issue, we have a issue open with BMC for > months now. > Along with what you suggested, which BMC also suggested, we have > implemented - didnot work. > In your websphere 8 configuration is httponly enable or disabled? > > > > issue: > > We are using > Back end - ARS 7.5 P4 on Unix 6.1.7 with 11g > Currently - We have a functioning 7.5 P4 MT 32 bit environment connected > to the back end. > This new MT 7.6 SP 4 is our attempt to upgrade the MT environment, then do > the back end. > > New MT env, > UNIX 6.1.7 > Websphere 8 64 bit > Deployed 7.6 SP 4 > Able to login in to config > http://new_httpserver:port1/arsys/shared/config.jsp > http://new_httpserver:port2/arsys/shared/config.jsp > - and add the backend server, and the report and log filesystem. > I'm currently not going thru the loadbalancers. > > (installed tomcat on win7 pc , and deployed 7.6sp4 mt against 7.5p4 > backend, works fine) > > New MT: > new_httpserver >-F/W- http port1, port2--> > new_websphere_app_MT7.6SP4_server_1---> F/W- http port1, port2, 80, 8080, > TCP_1 ->Backend_ARS_7.5P4_server > > new_httpserver >-F/W- http port1, > port2-->new_websphere_app_MT7.6SP4_server_2 ---> F/W- http port1, port2, > 80, 8080, TCP_1 -> Backend_ARS_7.5P4_server > > New MT: > old_httpserver:port3>-no firewall --> old_websphere_app_MT7.5p4_server_1 > >-F/W- http port3, port4, 80, 8080, TCP_1 ->Backend_ARS_7.5P4_server > > old_httpserver:port4>-no firewall -->old_websphere_app_MT7.4P4_server_2 > >-F/W- http port3, port4, 80, 8080, TCP_1 ->Backend_ARS_7.5P4_server > > issue: > > http://new_httpserver:port1/arsys/shared/login.jsp > http://new_httpserver:port2/arsys/shared/login.jsp > > after entering id and password it returns the below page and not getting > authenticated and same login page appears with below url - > http://httpserver:port1 > /arsys/shared/login.jsp?/arsys/forms/server/Remedy+Home+Page+2/Default+Admin+View/?cacheid=d74a89db > > > http://httpserver:port2 > /arsys/shared/login.jsp?/arsys/forms/server/Remedy+Home+Page+2/Default+Admin+View/?cacheid=d74a89db > > > > However, the user is logged in, per the license usage or being prompt to > logout user when try to log into old http servers. > http://old_httpserver:port3/arsys/shared/login.jsp > http://_oldhttpserver:port4/arsys/shared/login.jsp > > This is the closest to the our issue I have looked at for references, > please let me know if i'm on the the right track.. > > http://ars-action-request-system.1093659.n2.nabble.com/Midtier-Loadbalancer-is-not-working-Any-suggestion-URGENT-td7586174.html > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > > > If you are not the intended addressee, please inform us immediately that > you have received this e-mail in error, and delete it. We thank you for > your cooperation. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > If you are not the intended addressee, please inform us immediately that > you have received this e-mail in error, and delete it. We thank you for > your cooperation. > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
