Hi , Well we have log4j and debugging in our code. We thought the singleton might be an issue. so we tried the following without the singleton. we made a single servlet call without the singleton.We make a remote call to Websphere Application Server ( on AIX) using corbaloc like 'corbaloc::ip1:2809:ip2:2809'. Now when i one of my App server fails, the other App Server server should take over. But stil the take over was not done. We have alsofound the following information: the tomcat websphere connection is done via the following ports: bootstrap port ( which is 2809 for us) and ORB listner port ( 41999 for our application) The tomcat opens socket to connect to the bootstrap port (2809) first and then ORB listner port (41999) later when the first call is made. Now when the subsequent calls are made connection is made via the ORB listner port only. When one of the App Server fails... it still tries to connect to bootstrap port (2809) of first app server. ideally it shoulde try to connect to the new app server bootstrap port. Can anyone help me reg this problem Santosh
On 9/30/05, Tim Funk <[EMAIL PROTECTED]> wrote: > > Based on everything written so far - there is no evidence tomcat would be > chaching anything. > > I'd suggest placing as much debug code in your code as possible via a > logging > pacakge such as log4j/commons-logging so the log information can be turned > on > via configuration directives. > > -Tim > > Santosh Asbe wrote: > > > Hi All, > > > > I need your help for this problem very urgently. > > > > I have tomcat 4.1.30 on Linux. It servers as a web server and contains > only > > JSP & Servlets. We make a remote call to Websphere Application Server ( > on > > AIX) using corbaloc like 'corbaloc::ip1:2809:ip2:2809'. Now when i one > of my > > App server fails, the other App Server server should take over. This > work > > when i use a simple java client on the Linux machine, the failover > occurs. > > But when i use my application in tomcat, this does not work. > > I am using a Service locator ( singleton) which makes the initial call > to > > App Server and stores in the ip cache. initially we that the issue was > with > > the Service locator, but then even if i don't use this Service Locator, > the > > problem persists. > > > > We have talked to IBM and they say that the tomcat does some caching and > the > > problem is not with the App Server. Has anyone faced this issue? Can > anyone > > help regarding this and how can i know how and where the caching is > done? > > Can this issue be resolved. > > > > If any other information is required, i will be glad to provide with the > > same. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
