problem when loging

[former_member529475]

Hi sdn friends. I got the Error in Cache Refresh. The Error is Unable to Refresh the Cache.

What it is? and How can it be solved?

One more thing While activating my change list my system got stucked and I Manually restarted the System. After restarting my XI Server runs very slowly. It takes lot of time to open my integration repository and integration directory. It was showing the message as problem when loging on and the exception is

java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.100.101.106,port=50004,localport=2424]Nested exception is: java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/10.100.101.106,port=50004,localport=2424]

And then I went to J2ee admin and there also It was taking lot of time?

Why it was raised? Is it due to restart of my system manually? How can I rectified it.

Can any one help me ..... to solve this problem

- Vasu

[agasthuri_doss · Accepted solution]

Dear Rao,

1) Cache Connectivity Test

In RWB component monitoring, we have the option of checking whether the cache-connectivity is functioning correctly. This is useful when we are experiencing problems when updating the runtime cache. The system displays a separate window in which we perform the test. If no previous tests have been performed, the system displays a corresponding message. Otherwise, the system shows when and by whom the last test run was started, together with the result of this test.

• To start a new test run, choose Start Test.

The system displays the first results of the test run. Since the whole test takes some time, we can update the displayed results if necessary.

• To Update the displayed results, choose Refresh Display.

The overall result for each component is displayed as a green, yellow, red, or gray symbol. A green symbol is only displayed if both update steps for the runtime cache were successful, that is, they both have a green symbol.

If you still face the issue try this too,

Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.

However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason, SAP recommends that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.

To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.

Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.

Thanks & Regards

Agasthuri Doss