HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with th

[Former Member]

hello friend,

I have developed a proxy to JDBC synchronous scenario.

My scenario works like this.

i run an abap program which calls a client proxy,

the proxy fetches the data from database table and returns the data in the ABAP program.

My program is working fine but there is a small problem.

when i run the report for the first time, it gives me an exception while calling proxy

HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with the description Timeout

and when i run the report for the second time with same variant it works fine.

i can see the exception mostly in the morning when i run the report for the first time

please help me to find the solution of this problem.

thanks

kannu.

[Former Member]

thanks for ur suggestions.

i did the changes as per the instructions but the problem still persists.

I got an exception when i run the program for the first time.

It is a proxy to JDBC scenario.

Please help to find out the problem.

thanks in advance

kannu

[agasthuri_doss]

Kannu,

Try posting few records to the table ( Less than 10 records)

Is it Sync call ?

Cheers

Agasthuri

[Former Member]

thanks Agasthuri,

yes it is a synch call.

it is a synch proxy to jdbc scenario

kannu.

[agasthuri_doss]

Kannu,

Check how long does the replay message take from the database system, If it takes more time adjust the JDBC Parameter to accept higher value - Sync call.

Cheers

Agasthuri

[Former Member]

thanks for your suggestions.

i have changed the timeout parameters but facing the same problem

i have changed the program with sending the dummy proxy call to the db for the first time

and then sending the actual data but that is not working also.

Please suggest me some more options so that i can solve this issue.

thanks

kannu

[Former Member]

thanks Agasthuri,

Please telll me how to check the replay time from the database.

Please let me know which JDBC parameter are talking about.

the values in the Jdbc channel are as follows.

Interpretataton of empty strings Null value

Exactly-once handling

persistence LOCAL

conflict resolution: REDO

Escape symbol: ''

please suggest if anything needs to be changed.

thanks

Kannu

[Former Member]

1. Increase the proctimeout in smicm as per note - 824554

2. Application threads in the J2EE engine might have got consumed in high load situations.

Increase the count of application threads in config tool at location Config Tool -> cluster-data ->

<configuration template> -> <instance-ID> -> managers -> ApplicationThreadManager ->

MaxThreadCount

3. Increase the parameter ServletInputStreamTimeout from 180000 to 1728000000.

Steps for setting this parameter:

a. If you have configured ICM to forward requests to the J2EE dispatcher then apply Note

1048692. If the problem is not resolved, then apply section b.

b. The request bytes are reaching the Engine too slowly

i. Start the configtool in <J2EE>/configtool directory

ii. Browse the tree in the left pane

cluster-data -> Global server configuration -> services -> http

iii. Press the ServletInputStreamTimeout key in the keylist on the right

iv. Change the value of the "Value" field at the bottom of the right pane to the

preferred one (in milliseconds).

-1 means there is no timeout - that is unless the full request comes into a single

chunk, an error will be thrown

180000 means the Engine would wait for 3 minutes for any byte to be entered in

the stream.

1728000000 means the Engine would wait for 20 days for any byte to be entered

in the stream

v. Press the "Set" button in the top-right corner

vi. Select from the menu File -> Apply and confirm all popups.

vii. Restart the Engine for changes to take effect

[Former Member]

thanks for your valuable answer

i will do the changes and check whether the problem still persists.

[abhay_rajhans2]

Hi Kannu,

Before executing first time check in SM59 what is the connection test output of the RFC connection which is connecting ABAP to XI.