on 06-08-2010 3:29 PM
Hello guys,
We're having a problem with the web dispatcher regarding HTTP port of one Appl. Server.
Web Dispatcher should connect to HTTP port 8000 of all servers but it connects to port 50000 in one Appl. Server. The other ones it connects correctly to HTTP port 8000.
Appl. Server profiles are the same!!!
Where does web dispatcher get the HTTP port 50000?
Could you please help me?
regards,
Filipe Vasconcelos
I've restarted the system and now it's working well. thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It's redirecting to the java server just in one appl. server. In other AS it's redirecting well to abap http.
I have wdisp/add_xforwardedfor_header=1 in my webdispatcher. Is this URL redirecting??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
What do you mean by redirecting ?
If you don't use redirect commands in the web dispatcher profile, it does not redirect because it is a reverse proxy.
If you mean reverse proxifying the connection to a java server, when does it happen ?
Do you type a java URL or an abap url ?
Do you have a java stack installed on all app servers or on only one ?
Regards,
Olivier
The webdispatcher is connecting to the message server http port, which is providing the information regarding the java system. So connections to the webdispatcher are balanced over the java servers of your cluster.
Do you have url redirection active in your webdispatcher?
Kind regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.