JDBC Receiver Comm Channel Issue

[Former Member]

Hi Team,

We have around 77 interfaces inserting/updating information into a database.

Q1) Should we creating 77 different receiver JDBC communication channels for the same receiver?

Q2) Or would a single JDBC communication channel suffice?

Currently, we have only created a single communication channel and we are encounter 'JDBC Message processing failed, due to Channel has reached maximum concurrency ' error.

The Maximum Concurrency is set to '1' for now.

Q3)How do we manipulate the 'Maximum Concurrency' value?

Please advice.

Thank you,

Rakesh.

[Shabarish_Nair · Accepted solution]

Hi Team,
> 
> We have around 77 interfaces inserting/updating information into a database. 
> 
> Q1) Should we creating 77 different receiver JDBC communication channels for the same receiver?

it can be handled by a single on also

> Q2) Or would a single JDBC communication channel suffice?
> 
> Currently, we have only created a single communication channel and we are encounter 'JDBC Message processing failed, due to Channel has reached maximum concurrency ' error.
> 

creating multiple channels allows the flexibility of manual start or stopping particular interface flows in some business scenarios. if it is a single CC then there is no flexibility. so it depends.

> The Maximum Concurrency is set to '1' for now. 
> 
> Q3)How do we manipulate the 'Maximum Concurrency' value?
> 
> Please advice.
> 
> Thank you,
> Rakesh.

try increasing the value from 1 to 99 or the maximum permissible value

[Former Member · Accepted solution]

Thanks for the quick response.

So, If create 15 channels for these 77 interfaces and have a maximum concurrency of say 5 for all of them? That would work?

And how do I know if the Database CAN process so much information simultaneously?

Please advice.

Rakesh.

[rajasekhar_reddy14 · Accepted solution]

Hi,

Enter Max concurrency value 3 .

[Former Member]

Hi Experts,

Thank you for all the advice.

We have created a single receiver JDBC comm channel with the 'Maximum Concurrency' set to 1. Things are working fine now.

Thank you again,

Regards,

Rakesh.

[Former Member]

With the Maximum Concurrency was set to '1' but this lead to errors at run-time.

Later we changed it to '10' and things worked well.

Thank you for all the help/advice.

Rakesh.

[former_member4985]

Hi,

Have a look on note #831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter,

point 28 about maximum concurrency.

You may have to increase that value in order to "free" the resources for your system to process more messages.

Regards,

Caio Cagnani

[Former Member]

Hello,

You could also refer to the following notes:

831162 FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter

question 28. Effect of setting Maximum Concurrency and poolWaitingTime

1136474 XI 3.0/7.0: Setting Timeout for acquiring DB/FTP resources

1473299 Setting Maximum Concurrency and poolWaitingTime in File/Jdbc

The following blog has some more details -

Kind regards,

Sarah

[Former Member]

Hi Rakesh,

See, the suggest averege value for maximum concurrency is 5 to 8. If you increase more than this value it will affect your system and it may lead to Out of Memory (OOM) error, if enough heap memory and JDBC data source are not there. So please careful with setting this value, in long run it may give lot of production issue. I have faced this issue, so keep as optimal as possible.

Thanks,

RK

[former_member854360]

Hi,

Processing Tab Page

Maximum Concurrency

Enter the number of messages to be processed in parallel by the receiver channel. For example, if you enter the value 2, then two messages are processed in parallel. Default value is 1 and this means only one message can be processed at a time by the receiver channel.

Refer this

http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm