HttpServletRequest#getRemoteAddr() returns NULL

Question

Why does HttpServletRequest.getRemoteAddr() return null sometimes? For approximately 2 out of 10 identical requests is returns null for no apparent reason.

Read this thread - http://stackoverflow.com/questions/262887/why-httpservletrequest-getremoteaddr-doesnt-work-in-java-servlet — KV Prajapati, Jan 20 '12 at 08:57
I am having the same problem running JBoss AS 7.1. My server receives approx 9000 requests ~= 9GB of text in a short timespawn every day. During load testing, some hits to my webservice come up with a null on getRemoteAddr(). — Yablargo, Feb 21 '13 at 18:37

milan · Accepted Answer · 2012-07-21T14:53:24.267

6

Using Tomcat7. Apparently getRemoteAddr() can return NULL if the request has already been consumed, i.e. a response has been sent. It can even throw NPE sometimes. An error in my code in any case.

edited Jul 21 '12 at 14:53

answered May 21 '12 at 08:54

milan

2,355
2
23
38

score 1 · Answer 2 · answered Aug 14 '20 at 06:07

1

Did you pass the request object to another thread to read it asynchronously? In some web container, request objects will be recycled/reset once the servlet thread is finished. Then you might get null when request.getRemoteAddr() is called.

answered Aug 14 '20 at 06:07

Anderson

2,496
1
27
41

score 0 · Answer 3 · answered Jan 20 '12 at 12:06

That would be either a bug or a misconfiguration in the specific servletcontainer or proxy used. Lookup which one you are using, check its version and check if this bug has been reported before to its maintainers and check if there is a newer version to which you can upgrade.

HttpServletRequest#getRemoteAddr() returns NULL

3 Answers3

Linked