Receiver JDBC Adapter

[Former Member]

Hi All,

My scenario is R/3-XI-JDBC. When any error is encountered in the receiver end, will the JDBC adapter retry? If so how many times? at what interval? Can I change this setting?

Thanks & Regards,

Jai Shankar.

[moorthy · Accepted solution]

Hi,

Go thru this blog to set the retry settings -

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Regards,

Moorthy

[Former Member · Accepted solution]

Hi Moorthy,

There is no error on XI part. In RWB--> Communication channel monitoring, I got the error(I have given wrong database/table name). I expected to get the msg only once. But I found it 4 times.

The msg in Commn. channel monitoring is

Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Employee'(structureure 'STATEMENTNAME'): java.sql.SQLException: [SQL0204] Employee in SARJAI type *FILE not found.

8/30/06 1:15:36 PM 44f4a7b2b2c417ce01000000ac130c39

Processing started

I got this msg 4 times. I dint know why it happened?

FYI

The interface got triggered only once and only 1 msg in SXMB_MONI.

Hence this thread in forum.

Thanks & Regards,

Jai Shakar.

Message was edited by: Jai Shankar

[moorthy · Accepted solution]

Hi,

Oh...

As per the question, you can Retry the CallAdapter based on the settings as mentioned in the blog for your reference.

Now I think, you understood the reason, probably IS_Retry parameter is set to 4 times .. check this as per the blog

Regards,

Moorthy

[Former Member · Accepted solution]

Moorthy,

Thanks a lot. Is it IS_Retry or QRFC_RESTART_ALLOWED parameter? I dont have any queues used in my scenario(EO).

Thanks & Regards,

Jai Shankar.

[moorthy · Accepted solution]

HI,

It is IS_Retry parameter.

The parameter QRFC_RESTART_ALLOWED used to restart the queues if it is stuck beacause of any reasons.

<i> I dont have any queues used in my scenario(EO).</i>

>>>Yes, you did not mention explicitly. But all messages will go thru this message queues in XI. Once adapter puts messages in the integration engine, it will be in message queues. It is amdiministrated in the transaction code SXMB_ADM->Manage Queues

Regards,

Moorthy

[Former Member · Accepted solution]

Hi Moorthy,

Thanks a lot. Got your point.

Thanks & Regards,

Jai Shankar.

[Former Member]

Hi Jai,

a possible workaroud is using BPM.

You will use a exception branch for system errors. In this exception branch you can set a WAIT-step (possibly surround it with a LOOP step). After the WAIT Step there is your second SEND Step for the retry.

regards mario

[Former Member]

Mario,

Thanks for the alternative idea. But I can not use BPM in my scenario. How can I do it with out a BPM?

Thanks & Regards,

Jai Shankar.

[Former Member]

Hi Jai,

unfortunately I have no system at the moment. I hope anybody else will help you!

Regards Mario