Error SXI_CACHE

[rodrigoalejandro_pertierr]

hi all,

i have many scenarios that work without any problem.

I had to create an interface that use BPM. later the changes were active in ID > Cache notification> the ABAP Cache was red.

i did a CPA Cache Refresh but no error but in SXI_CACHE in facing this problem: the Integration process does not appear in sxi_cache and the status is red with this error:

Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.

so, i go to SM59 to test the HTTP RFC destination but the status is 500 ( REQ ID not Found) (/dir/CacheRefresh)

if the BPM is deleted from scenario the status of SXI_Cache change to green.

The server was restarted but nothing happend.

Any clue??

Thanks

Rodrigo

[samiullah_qureshi]

Hi

ID > Cache notification> the ABAP Cache was red.

You can refresh Cache Notification in Cache Notification itself.

Until or unless cache notification will successful you will not get correct status in SXI_CACHE.

RFC destination INTEGRATION_DIRECTORY_HMI is used to update ABAP Cache with respect to Java Cache.

Check following link for further info

[http://help.sap.com/saphelp_nw70/helpdata/EN/8f/770f41218ff023e10000000a155106/frameset.htm]

Regards

Sami

Reward points if helpful.

[former_member556603]

Hi,

Go through some Experts Discussions...

Thanks,

Satya Kumar

[Former Member]

Hi Rodrigo,

For the error code 500 you can follow the below mentioned information and check if there is anything worng in your sytem.......

HTTP Error 500 - Internal server error

Introduction

Your Web server encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.

This is a 'catch-all' error generated by your Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of your Web server site to locate and analyse these logs.

500 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).

Open an IP socket connection to that IP address.

Write an HTTP data stream through that socket.

Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'.

Resolving 500 errors - general

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of your Web server site to locate and analyse the logs which should give further information about the error.

Resolving 500 errors - CheckUpDown

Please contact us (email preferred) whenever you encounter 500 errors on your CheckUpDown account. We then have to liaise with your ISP and the vendor of your Web server software so they can trace the exact reason for the error. Correcting the error may require recoding program logic for your Web server software, which could take some time.

And also if u create a BPM senario activate all the objects(instantly after creating it Ex: Actions, Integration process) and after that referesh the cache in IR (design) and wait for somtime..........

Hope this will solve your problem

Regards

Sai

Reward with points if helpful