WEB dispatcher error - Guide .

[Former Member]

Hi All,

Here again.

I am getting the error in my Web Dispatcher Can anyone please guide me to find the root cause issue.

I am attaching the web dispatcher error here.

Thanks.

[isaias_freitas]

This error indicates that the client (browser) is not using any of the SSL protocols that are configured at the Web Dispatcher.

Try enabling SSLv3 and/or TLSv1.2 at the browser.

Another option is to verify/change the parameters "ssl/ciphersuites" and "ssl/client_ciphersuites".

The SAP note 510007 may help with the parameters.

[Former Member]

Hi Isaias,

Thanks for the information. But is it possible that the IP mentioned in the screen shot can made web dispatcher hung or not responsive.

Because once we check the web dispatcher is not responding then we check the log and found the related info. But is there any other reason for it? or anything which may cause , but once we restart it it got resolved.

Thanks.

[isaias_freitas]

Hello Biswajit,

That should not cause the Web Dispatcher to hang.

How did you conclude it was hanging?

[Former Member]

Hi Isaias,

Can you please check this screen shots. This is kind of error dev_webdisp has thrown many times. .

Do you find the issue which may got down the web dispatcher or hung it for the time being.

[isaias_freitas]

Hello Biswajit,

Those entries just indicate that the Web Dispatcher received an invalid request.

They would not cause the Web Disp. to hang.

[Former Member]

Hi Isaias,

Thanks for the reply. But do you have any idea for any standard parameter setting of Web Disp. can made this issue??

like I found as per SAP Note , wdisp/HTTP/max_pooled_con = 16000 and wdisp/HTTPS/mx_pooled_con = 16000 which is not mentioned in the parameter list.

Do you think this will make the Web disp. unresponsive?

Thanks .

[Former Member]

Hey Biswajit,

I've seen these errors before on my own webdisp. But usually it's because I enabled the HTTPs and not a HTTP port.

it seems for me even when you want to use HTTPs you should always put the param in for HTTP as well.

Also, is the back-end SAP system recently changed to add a "ASCS"?  if so, you may need to change the port for ms/http_port just watch out!

Check for your sapcrypto libraries are in place

Also, check your params like so to see if similar:

rdisp/mshost = YOURHOST

ms/http_port = 8101 (could vary..just check!)

icm/server_port_0 = PROT=HTTP,HOST=YourHOST.domain.com,PORT=81$$,TIMEOUT=90,PROCTIMEOUT=2700

icm/server_port_2 = PROT=HTTPS,HOST=YourHOST.domain.com,PORT=8191,TIMEOUT=90,PROCTIMEOUT=2700

icm/server_port_1 = PROT=HTTP,HOST=localhost,PORT=81$$

icm/HTTP/admin_0 = PREFIX=/sap/admin,DOCROOT=$(DIR_DATA)$(DIR_SEP)icmandir,AUTHFILE=$(icm/authfile),PORT=81$$

ssl/ssl_lib = $(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL)

sec/libsapsecu = $(ssl/ssl_lib)

ssf/ssfapi_lib = $(ssl/ssl_lib)

icm/host_name_full = FQDN (yours!)

DIR_INSTANCE = /usr/sap/WRQ/W90

ssl/server_pse = /usr/sap/WRQ/W90/sec/SAPSSLS.pse

ssl/client_pse = /usr/sap/WRQ/W90/sec/SAPSSLC.pse

icm/HTTPS/verify_client = 1

wdisp/ssl_encrypt = 1

wdisp/ssl_auth = 2

wdisp/ssl_cred = /usr/sap/WRQ/W90/sec/SAPSSLC.pse

icm/HTTPS/forward_ccert_as_header = true

My SID is different than yours ...but just check!

[Former Member]

Hi Both ,

The parameters are well defined except the two I mentioned .

So I think this must be some issue which can not be documented . It is resolved once we restart the web disp.

Or Kind of any memory or pool issue .

If you find anything else please let me know.

Thanks.

[isaias_freitas]

Hello,

The first error (SSL related) states "the client hello ... requests SSLv2".

This is not supported (as mentioned at the error entry itself).

The client has to be reconfigured to use a more secure SSL/TLS protocol.

The second error (illegal path) shows the request sent by the client, and it is invalid.

You should investigate why the client sends such invalid request.

None of these should cause the Web Dispatcher to hang.