tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rahul <iamrahu...@yahoo.com>
Subject Re: Tomcat 6.0.26 with Java 6 update 20 on Sun Solaris 5.8 Sparc - Web application unable to execute properly
Date Mon, 05 Jul 2010 23:14:51 GMT
Thanks to all of your comments and help!! The problem is resolved. I was very fortunate that
I was testing with FireFox otherwise I would never have come to know about the actual problem
(That is Redirecting to port 8080). The Internet Explorer was not at all showing that the
request is going to the incorrect port, wonder why??. 
Now, on clicking search button, data gets posted to the correct place and data gets fetched
from the database correctlty. As this webapp uses the Salmon SOFIA framework, in order to
display the data, it internally uses its own URLGenerator class: "URLGenerator"  and gets
the PORT from System.properties file! And this is where the port was specified as 8080. I
changed that to the one in Server.xml and VOILA!! 

--- On Mon, 7/5/10, André Warnier <aw@ice-sa.com> wrote:

> From: André Warnier <aw@ice-sa.com>
> Subject: Re: Tomcat 6.0.26 with Java 6 update 20 on Sun Solaris 5.8 Sparc - Web application
unable to execute properly
> To: "Tomcat Users List" <users@tomcat.apache.org>
> Date: Monday, July 5, 2010, 1:41 PM
> rahul wrote:
> > Hello Friends
> > 
> > A very strange findings for today! Found it only
> because I skipped the first "Launch" page that used to
> launch a new window through Java Script. Now, the finding is
> - 1. After the Launch, this would open a Home Page with the
> request URL - http://<localhost>:5080/<URL>
> > 2. Clicking on Search Work Order menu, it will request
> the URL:
> > http://<localhost>:5080/<SearchListURL>
> > 3. Now, interesting bit - On providing search crietria
> and clicking search, the request is sent to -
> http://<localhost>:8080/<SearchListURL>
> > 
> > Now, why the third step is posting this to default
> 8080 port when clearly the server.xml is configured to
> listen to HTTP requests on 5080 port.
> > 
> > I tested this in Windows with 5080 listener port and
> it failed there too.
> > 
> > Any hints?
> > 
> Rahul,
> I don't know about the rest of your problem, but if you
> click on a link /in the browser/, and the browser sends a
> request to localhost:8080 as a result, then it means that
> /the html page which the browser has/ contains a link that
> points to port 8080.
> So in your example above, it is the page returned by
> http://<localhost>:5080/<SearchListURL>
> which contains a link to port 8080.
> It has nothing to do with what server.xml says about the
> ports the server is listening on.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message