Tell me about BES.

Borland BES may not have too many people to use, I also bought after the company to know
The server's kernel is all open source servers like Apache,tomcat, so it's cheaper (and we only buy Web Edition)
But it does have a very fancy management interface.
However, later use also feel as a Low-cost application server can also be used.

But this time there is a strange thing, our application needs to log each user login
IP address (naturally with request.getremoteaddr ()), after discovering the BES record IP let
People are unpredictable, for example, you just started partition. Use 112 to access, at this point, the back-end record
is 112, after the 10 access, the display of IP for a while is 112, a moment is 10, completely irregular, and then from another
Machine login, then the IP seems to be random three have visited the IP, let me very annoyed.

At first I was thinking, how to say is also money to buy a commercial server, it is impossible to have such a low-level problem,
So I've been looking for the reason for my own application, which uses a lot of filters, context management
Things like that, fear is in a certain place code out of the question, find the result is not a little effect, after simply
On the development of a small servlet deployment to test, the results, which I believe that this is a BES problem.
It's really ft.

That is to determine it is the problem, just look at the Internet should have been encountered, fortunately, the first two is off
On this question (Google:bes getremoteaddr), one of them is Borland official net
Standing, thinking that there will be an answer, it online content is as follows (HTTP://SUPPORT.BORLAND.COM/ENTRY.JSPA?EXTERNALID=3370&CATEGORYID=120):

BES60 rp1-httpservletrequest.getremoteaddr () gives IP address
Applicable for:

BES60 rp1-httpservletrequest.getremoteaddr () gives an ' old ' IP address

Product Name:bes

Product VERSION:6.0RP1

Product Component:web Container

Platform/os Version:win32

Jdk/compiler version:1.3.1/1.4.1

Problem Description:

HTTPSERVLETREQUEST.GETREMOTEADDR () gives an ' old ' IP address from the someone who used connection earlier.

Resolution:

This is a known issue into the default connector with a BES 6.0RP1. However The workaround is:

Go to the Server.xml as follows:

Borland Management Console--> Configuration--> Partition--> Web Container right click on Web Container, click Properties

Click ' Service:http ', click ' Connector:CoyoteConnector:xxxx ', click the XML tab on the right pane and comment the line

Highlighted that's as follows by placing in the end of this element.

Then Add the following line:

port= "xxxx" minprocessors= "5" maxprocessors= "enablelookups=" true "redirectport=" 8443 "acceptcount=" "debug=" 0 "

connectiontimeout= "20000" useurivalidationhack= "false" disableuploadtimeout= "true"/>

Note:change port number in new connector to match the port number that existed previously.

I looked at it for a long time, comparing it to the part that I have to replace, the root of my existing configuration is exactly the same.
After looking for a long time, only to find a forum in sun to discuss this issue, someone else's final solution is to replace a tomcat connector
There's just no connector on the Borland Web site that should be used, but a configuration that doesn't need to be replaced at all (I'd like to
The letter is the question of the importation of personnel, but its professionalism is also to be known, and Ft.
Change Org.apache.coyote.tomcat4.CoyoteConnector to Org.apache.catalina.connector.http.HttpConnector

This is a very simple question and an obvious one, so I do not think the problem should be on commercial servers.