File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Soft Skills: The software developer's life manual this week in the Jobs Discussion forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

request.getRemoteAddr() not returning correct value

 
Boby sharma
Greenhorn
Posts: 1
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

we are facing a issue which i describe below.

we have our application previously on Tomcat 6.0.32 which has to be migrated to JOnAS 5.2.1 server.

we are also using Apache HTTP 2.2 as a proxy server between Tomcat and application every request goes to Apache HTTP 2.2 server first then it redirect to the our local environment.So as the request is

coming from Apache HTTP 2.2 the method request.getRemoteAddr() returns the IP Address of the server where Apache HTTP 2.2 is installed.

But as we have migrated our application from Tomcat to JOnAS,the same line in one of the filter request.getRemoteAddr() is returning IP address of our local development machine where JOnAS is running.

---->Earlier in Tomcat we used to set path of our application in server.xml of tomcat.

<Context path="/oscar" reloadable="true" docBase="D:\Projects\Oscar\Integration\sources\projects\Oscar\WebContent" workDir="D:\Projects\Oscar\Integration\sources\projects\Oscar\WebContent\work\org\apache\jsp" >

But in JOnAS we are deploying WAR due to problem in loading from context.

I am really unable to understand the problem.

Thanks for your support.

Regards,
KSH
 
Tim Holloway
Saloon Keeper
Pie
Posts: 17615
38
Android Eclipse IDE Linux
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the JavaRanch, Boby!

What benefits are you hoping to achieve using getRemoteAddr(). It's actually fairly useless. For example, every machine on my LAN would appear to your server under the same IP address.

The JOnAS webapp server runs an embedded copy of Tomcat, but because JOnAS is a full-stack implementation, it has to deal with EARs and other non-WAR deployables as well as WARs themselves. So its deployment processes are different from stand-alone Tomcat.

Fortunately, the JOnAS documentation is generally fairly good, and the people on the JOnAS project were always very helpful to me, so I always enjoyed working with JOnAS.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic