on 02-17-2016 11:35 AM
Hi All,
I am seeing below error after upgrading web dispatcher to 745 from 721. os is linux. please can someone guide me.
[Thr 140606531098368] Wed Feb 17 06:30:10 2016
[Thr 140606531098368] *** ERROR => no valid HTTP destination server available for system '000' using logon group '!J2EE' rc=4 {0000000a} [http_route.c 3724]
[Thr 140606531098368] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3750]
[Thr 140606531098368] *** WARNING => original destination was '!J2EE' [http_route.c 3753]
[Thr 140606531098368] *** ERROR => no valid HTTP destination server available for system '000' using logon group '!ALL' rc=4 {0000000a} [http_route.c 3724]
[Thr 140606531098368] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3750]
[Thr 140606531098368] *** WARNING => original destination was '!ALL' [http_route.c 3753]
[Thr 140606527399680] Wed Feb 17 06:30:28 2016
[Thr 140606527399680] *** ERROR => no valid HTTP destination server available for system '000' using logon group '!J2EE' rc=4 {00000010} [http_route.c 3724]
[Thr 140606527399680] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3750]
[Thr 140606527399680] *** WARNING => original destination was '!J2EE' [http_route.c 3753]
[Thr 140606527399680] *** ERROR => no valid HTTP destination server available for system '000' using logon group '!ALL' rc=4 {00000010} [http_route.c 3724]
[Thr 140606527399680] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3750]
[Thr 140606527399680] *** WARNING => original destination was '!ALL' [http_route.c 3753]
Thanks,
Ranjith
Hi Ranjith.
You can refer the SAP KBA with cause number 2
1911913 - 500 Dispatching error thru web dispatcher
Regards
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rajith.
1. Are you getting any error message? If possible restart the system and update the latest log.
2. You can refer the SAP note for basic parameters wabdispatcher.
538405 - SAP Web Dispatcher: composite note
3. You can refer the Upgrade guide from the follow the SAP Note
908097 - SAP Web Dispatcher: Release, Installation, Patches, Documentation
Regards
SS
Spoiler alert: setting "icm/HTTP/auth_0 = PREFIX=/sap/wdisp/admin" will not solve the issue.
If the parameter is not explicitly set, the Web Dispatcher uses an internal default value.
This parameter is already active and don't need to be changed.
Well, if Ranjith has already opened an SAP incident, I guess he can work on the issue there.
Anyway, the profile looks correct and my next request would have been to set the parameter "rdisp/TRACE = 2", restart the Web Dispatcher, simulate the issue, and then copy the Web Dispatcher trace file (dev_webdisp).
Ranjith could then attach the trace file to this thread, remove the parameter "rdisp/TRACE" from the profile and restart the Web Dispatcher again (in order to stop the detailed tracing).
Regards,
Isaías
Hello Ranjith,
The parameter "wdisp/ssl_encrypt" is set to zero.
This means that the Web Dispatcher should deccrypt the request and forward it as HTTP to the backend.
However, the backend system does not have an HTTP port open.
Setting the parameter "wdisp/ssl_encrypt = 2" will make the Web Dispatcher decrypt the request and them re-encrypt it, sending it as HTTPS to the backend as well.
This should fix the issue.
The SAP KBA 2160678 might be of assistance as well, depending on what happens next.
Regards,
Isaías
Hi All,
Thank you for the support. the issue was fixed finally by creating logon groups !J2EE and !ALL in NWA following below links.
Determining the Server Group - Application Server Infrastructure - SAP Library
https://help.sap.com/saphelp_nw73/helpdata/en/4a/954cac17335ff9e10000000a421937/content.htm
Hello,
I believe that you have confirmed that the backend system was available, right?
(it does not hurt to ask )
If you need further assistance, after reading the WIKI sent by Raquel, please attach the Web Dispatcher profile to this thread.
In addition, clarify what are its backend systems (e.g., is it a Portal, an ABAP only system, a dual-stack system, etc.).
Regards,
Isaías
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Isaias,
backend is portal 7.3 (java stack). below is the web dispatcher profile.
when i use old version 7.20 web disp, it is working. the issue is with latest 7.45 web disp.
# unique instance number
SAPSYSTEM = 80
# add default directory settings
DIR_EXECUTABLE = .
DIR_INSTANCE = .
# Accessibility of Message Servers
rdisp/mshost = xxx
ms/http_port = 8123
# SAP Web Dispatcher Parameter
wdisp/auto_refresh = 25
wdisp/max_servers = 100
wdisp/shm_attach_mode = 6
# configuration for large scenario
icm/max_conn = 16384
icm/max_sockets = 16384
icm/req_queue_len = 6000
icm/min_threads = 100
icm/max_threads = 250
mpi/total_size_MB = 500
mpi/max_pipes = 21000
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 2000
wdisp/HTTPS/max_pooled_con = 2000
# SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=8080
icm/server_port_1 = PROT=HTTPS,PORT=8443,TIMEOUT=1800,PROCTIMEOUT=1800
# SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt
wdisp/enable_j2ee_groups = FALSE
Hi Ranjith,
Please check below wiki, which may help on resolve the issue you're having:
http://wiki.scn.sap.com/wiki/display/SI/Error+code+for+no+valid+destination+server+available+when+ac...
Regards,
Raquel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
79 | |
9 | |
9 | |
7 | |
7 | |
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.