XI is not responding

[Former Member]

Hi Experts,

During the weekend, our admin guys did some kernal upgradation and for some reason when the parameter files were edited on Friday part of the file was dropped/corrupted. Now they are able to revert back to previous kernel level. But the problem is nothing is coming to XI either from R/3 or from 3rd party system. I did all checks like

1) SLD Check

2) Cache

3) RFC connections

4) Testing the Connection to Integration Builder & SLD

5) Cache Connectivity Test

6) Runtime Workbench

7) Adapter Monitor checks

😎 Message Monitoring

9) ICM Monitoring

10) Gateway Monitoring

11) Que Monitoring

12) J2EE Monitoring

Everything seems perfectly alright. Can somebody throw some light on this? Plz it's kinda urgent, as the system is under client testing.

Thanks in advance

regards

[bhavesh_kantilal · Accepted solution]

Check the Idoc status in your R3 system in SM 58./ Make the user id as *. Check if you get any dumps.

Regards

Bhavesh

[Former Member · Accepted solution]

Tq Bhavesh,

Not only from the R/3 side, when siebel trys to send thru HTTP, they are getting an error as

"Error: SiebelError: Error invoking service 'EAI HTTP Transport', method 'Send' at step 'Send to SAP'.(SBL-BPR-00162) HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'(SBL-EAI-04117)"

regards

[Former Member · Accepted solution]

Hi,

SM58 is showing an error "Idoc Adapter Inbound Channel : Error Erro when read" and the QOUT(Scheduler) is with inactive status.

Plz advice me.

regards

[former_member189354 · Accepted solution]

Hi,

So HTTP Status code is 500 means internal server error. As (AE) java stack is not woking properly. After downgrading the kernal patch is they restarted Java Stack. If not, ask they to restart java instance. If not, restart the services of adapters from visual admin tool. If not the case, ask them to debug the XI adapters ( as Suggested by SAP).

Regards,

Daniel.LA

[Former Member · Accepted solution]

Hi Daniel,

yes, they have restarted the java instance.

regards

[former_member189354 · Accepted solution]

Hi,

Can you check the following log files

/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/applications.[n].log for every

N server node.

There is also an XIspecific log available (which also containing information about adapters):

/usr/sap/[SID]/[instance]/j2ee/cluster/server[N]/log/applications\com.sap.xi\xi.log

You can access the files with the log viewer service of the J2EE Visual Admin tool.

Regards,

Daniel.LA

[Former Member]

Hi Experts,

Thanks for your all help. This problem is resolved and this is because of user got locked.

regards

[bhavesh_kantilal]

Which user was this? Can you provde more info?

regards

Bhavesh

[Former Member]

Hi Bhavesh,

It is XIAPPLUSER.

regards

[agasthuri_doss]

Hi,

The HTTP code 500 indicates internal error in your application.

Check on to the stacktrace in

<local drive>:\usr\sap\XXX\YYY\j2ee\cluster\server0\log

Also and check note number 804124 at service.sap.com

Regards

Agasthuri Doss