Sync issue: "server returned http response code: 500 for URL"

[Former Member]

Hi All,

I am running on <b>SAP MI 2.5 SP 18 Patch 01</b>, with a DB2E and our application. I am syncing via the ICM / ABAP port of our middleware.

When I install the DB2E everything goes well. After that I install the application and my SP upgrade. After that I do a sync with my data request. I wait a few minutes till the moment my data is ready to sync.

When I sync I get the following error after 15 minutes of syncing:

<i>• Synchronization started

• Connection set up (without proxy) to: https://<host>:<port>/sap/bc/MJC/mi_host?~sysid=<system>&;

• Successfully connected with server.

• Processing of inbound data began.

• Synchronisation problems: Transport-layer (http) sync exception raised (root cause: Exception while synchronizing (java.io.IOException: Server returned HTTP response code: 500 for URL: https://<host>:<port>/sap/bc/MJC/mi_host?_{sysid=<system>&}client=<client>&~language=EN&PACKET_SIZE=100&ACKNOWLEDGE=X&)) </i>

I tried it without data packaging, and I tried it with data packaging on size small. But this time I receive the error after 90 minutes of syncing. I saw something in the monitor but 1% of my data packages are received by my mobile client this time, and I also get the error.

I tried it with the normal J2EE sync and I tried it with the ABAP sync, but both are not working.

When I try it on the J2EE port it is working.

When I do an installation with the initial data load via the J2EE port it is working. When I switch to the ICM / ABAP port after this initial data load via the J2EE port it still works.

What can be the problem? Can someone please help me with this?

Thanks in advance,

Bart Elshout

[Former Member · Accepted solution]

Hi Bart Elshout

The note i had mentioned has a mandatory note no 984207 that also needs to be applied. Have you done this???

Also just for information --- Once you have changed the client to connect to ABAP Sync Service to Java Sync Servlet you can never revert back to Java Sync Servlet.

Best Regards

Sivakumar

[Former Member]

Hi Bart Elshout

Please apply note no. 1001292 and this should ideally solve your problem. Do let me know if problem persists.

Best Regards

Sivakumar

[Former Member]

Hi Sivakumar,

Thanks for your solution, this seems to work.

I am now getting another error, but almost the same:

Synchronisation problems: Transport-layer (http) sync exception raised (root cause: Exception while synchronizing (java.io.IOException: Server returned HTTP response code: 502 for URL: <host>:<port>/meSync/servlet/meSync?_{sysid=<system>&}client=<client>&~language=EN&ACKNOWLEDGE=X&))

So this time 502 in stead of 500. Is there also a note for this error?

As you can see this time I am not syncing via the ABAP sync, but just the J2EE sync. The time of receiving the error is just te same: "when I do my initial data load"!

I hope you can also help me with this error. I could not find a note for it.

Thanks in advance and kind regards,

Bart Elshout

[Former Member]

hello bart,

had you configured an https_port?

can you confirm that the client messages reaches the ICM?

(try checking on the ICM logs)

regards

jo

[Former Member]

Hi Jo,

With the data packaging on small I can see some packages are send to my mobile client. 1% of my packages are send in 1,5 hour but after that the error occurs. I can see this in the merep_mon, so the client messages reaches the ICM.

regards,

bart

[Former Member]

Hi Bart Elshout

The HTTP response code: 500 error on the client in combination with ABAP Sync Service most probably occurs due to a Short Dump in the middleware. Please check for the same in st22 transaction for that particular user on the specified date. If possibile post and i may help you furhter.

Best Regards

Sivakumar

[Former Member]

Hi Sivakumar,

I have checked the st22, but there are no short dumps for my user.

I am also getting the error with J2EE sync, so not only with the ABAP sync.

I hope you can help me, also without getting short dumps in the middleware.

Thanks in advance and kind regards,

Bart