no valid destination server available for '!J2EE' rc=4

[Former Member]

Hi Folks,

We have setup a webdispatcher7.0 for a standalone java stack system and configured SSL termination on it,

Every thing works fine but we get the below error sometimes:

*[Thr 3284] Wed Feb 02 09:21:21 2011

[Thr 3284] *** ERROR => NiBufIConnect: non-buffered connect pending after 5000ms (hdl 5;XYZSAPUT01:51200) [nibuf.cpp 4611]

[Thr 3284] *** ERROR => Connection request to host: XYZSAPUT01, service: 51200 failed (NIECONN_REFUSED) [icxxpool.c 1968]

[Thr 3284] *** ERROR => error connecting to server 'J2EE128219500' [http_route.c 2935] [Thr 3284] *** WARNING => redispatching of failed stateful request [http_route.c 3024] [Thr 3284] *** ERROR => no valid destination server available for '!J2EE' rc=4 [http_route.c 3126]

[Thr 3284] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3146]

[Thr 3284] *** WARNING => original destination was '!J2EE' [http_route.c 3149]

[Thr 3284] *** ERROR => no valid destination server available for '!ALL' rc=4 [http_route.c 3126] [Thr 3284] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3146] [Thr 3284] *** WARNING => original destination was '!ALL' [http_route.c 3149] [Thr 3284] *** ERROR => no valid destination server available for '!ALL' rc=4 [http_route.c 3126]

[Thr 460] Wed Feb 02 09:22:36 2011

[Thr 460] *** ERROR => NiBufIConnect: non-buffered connect pending after 5000ms (hdl 26;XYZSAPUT01:8101) [nibuf.cpp 4611]

[Thr 460] *** ERROR => Connection request from (-1/65535/0) to host: XYZSAPUT01, service: 8101 failed (NIECONN_REFUSED) [icxxconn.c 2738]

[Thr 460] *** ERROR => IcmConnClientRqCreate() failed (rc=-8) [icrxx.c 5234]

[Thr 460] *** ERROR => Could not connect to SAP Message Server at XYZSAPUT01. URL=/msgserver/text/logon?version=1.2 [icrxx.c *

500 dispatching error message is shown to the enduser and the above error is present in the log. No problem with the message server of the Java stack, Java stack is up and running. All the profile parameters are fine. This behaviour of dispatcher is pretty strange? Did any one face similar issue? Any Idea on this?

Regards,

Vamshi.

[Former Member]

login as icmadm to

http://host:port/sap/wdisp/admin

and on the right pane click monitor server groups. If you don't find any j2ee instances, sap webdispathcer cannot send the load to the backend j2ee.

try this first sapwebdisp pf=../sapwebdisp.pfl -checkconfig it will show you the issues.

also set is/HTTP/default_root_hdl = j2ee.

Also you said that ssl termination, is your parameters are like this:

icm/server_port_0= ... PROT=HTTPS, PORT=443

wdisp/ssl_encrypt=0

Let me know.

Regards

SM.

[Former Member]

it migh be the network issue. are you able to ping java stack IP all the time?

[Former Member]

Yes I am able to.

[Former Member]

check the below note: it has the solution for your error.

Note 552286 - Troubleshooting for the SAP Web Dispatcher

[Former Member]

Thanks for the post.

Checked that note before posting the thread. It doesn't explain the problem, the note says backend is down or not available but in my case the J2ee engine is up and running.

Regards,

Vamshi.

[Former Member]

Hello Vamshi,

What is the value of parameter icm/ssl_block_timeout set to ? Is it 50 s?

Regards.

Ruchit

[Former Member]

Hi Ruchit,

Thanks for your reply.

I haven't set this parameter on the webdisp. I can't find this parameter in the below link : http://help.sap.com/saphelp_nw70/helpdata/en/f6/3c0b0389cea34ba66f10d62b718a1a/frameset.htm

But am using the SSL termination so the request going to backend system is only http request. So I really didn't understand what this parameter would do?

Regards,

Vamshi.

[Former Member]

Hi Vamshi,

Any progress on this issue? I'm getting same problems. I'm trying to use https for the metadata exchange. I can't seem to connect to the https message server port of my portal. I have ssl setup and set ms/https_port and

#SSL Metadata Parameters

wdisp/server_info_protocol = https

wdisp/group_info_protocol = https

wdisp/url_map_protocol = https

Is that what you were trying to do? Any resolution?

Thanks, Pat

[Former Member]

I found my problem, my ms/server_port_01 for https is not getting created. There is an ssl error in the port in the SCS instance. I'll have to test, but it looks like SCS does not get the ssl parameters and the exe directory of SCS does not have the sapcrypto lib. So problem is portal message server https port is not created.

[Former Member]

Hello,

Are you setting uo end-to-end SSL ? IN my case am using ssl termination so I really dont need to set any parameters at my J2ee Engine.

I face this problem intermittently. It doesn't occur always.

Regards,

Vamshi.

[Former Member]

What is the webdispatcher release,

try patching it up, in most cases that should resolve it or debug it by increasing the trace level when the issue happens.

Regards

SM.

[Former Member]

HI,

Ya we are planning to update it to the latest patch. Currently we are on 144 patch.

Regards,

Vamshi.

[Former Member]

Hello Folks!!!!

I have updated to the latest kernel patch but still I get the same error 500 Dispatching error . Any ideas?

Regards,

Vamshi.

[Former Member]

Have you specified the right message server port in webdisp.pfl?

Reply the dev_webdisp and dev_ms of Java SCS instance here.

Thanks

SM

[Former Member]

Hi Vamshi,

When you login to the Admin tool for web dispatcher, does it show a green tick mark against all the J2EE servers in there?

Regards,

Venkatesh.K

[Former Member]

Hi,

Yes I have put the correct port in the profile. If not I would get this error all the time. As I said this is only intermittent.

To be clear, if the user opens the ur for the first time it works fine, He refreshes the Page for 5-6 times them this error may occur. Some time this doesn't occur. We have done the network connectivity test and everything went fine no issues with the network.

Regards,

Vamshi.

[Former Member]

You can upgrade the webdispatcher to the latest version without having the backend system kernel upgraded and see if it helps.

If upgrade doesn't work, you can bypass the SCS Message server and directly hit the Dispatcher Port and we can reduce the Network time. I have used this scenario for Portal only System and skipped the Message Server.

Configuration:

Setup the webdisp.pfl to the following values: and input

wdisp/server_info_location = file://D:/usr/sap/WEB/SYS/profile/info.icr

wdisp/group_info_location = file://D:/usr/sap/WEB/SYS/profile/icrgroups.txt

wdisp/url_map_location = file://D:/usr/sap/WEB/SYS/profile/urlinfo.txt

Refer: http://netweaverturk.com/category/web-dispatcher/

Thanks

SM