system.queueParallelism.maxReceivers overides maxconcurrency in JDBC Receiver

[Former Member]

All,

I tested one EOIO interface proxy to JDBC (SQL DATABASE).

Sceario 1: system.queueParallelism.maxReceivers 15

max concurrency 1

Java Nodes 4

JDBC_http://sap.com/xi/XI/SystemRecv 15.

Only the above mentioned interface is executed in teh environment. I know settings max receivers to 15 and JDBC System Recv to 15 as well does not make sense, neverthless I wanted to test the system the way it is handed over to me.

Result: I see 60 delivering messages at the same time i,e 15 System Recv threads on each node are being utilized fully.

Scenario 2:

system.queueParallelism.maxReceivers 15 

max concurrency 6

Java Nodes 4

JDBC_http://sap.com/xi/XI/SystemRecv 15.

Result: still the same result. No effect of changing max concurreny.

[Former Member]

Ok Now:

Sceario 3: system.queueParallelism.maxReceivers 5

max concurrency 1

Java Nodes 4

JDBC_http://sap.com/xi/XI/SystemRecv 15

Still I see 60 messages in delivering status for the interface being tested.

I was hoping to see 5 (max receivers) * 4 Java Nodes = 20 messages only being deleivered at any given time for a single interface.

[rajasekhar_reddy14]

Max Concurrency applicable to one JDBC communication channel like how many parllel transaction can perform at a time,when you increase the Max Receiver value to 15 means by defulat jDBC adapter can perform 15 parlelem transactions at a time but if you enter max concureency value 10 in one  JDBC channel then it uses maximum 10 thread to perform operations on data base and remaining 5 threads will be available to other channels.

[ambrish_mishra]

Hi Vicky,

Max Concurrency will come into play in live environment where other interfaces will also share the resources and the volume will be high. system.queueParallelism.maxReceivers is for the entire system and this will be shared across the landscape.

You can keep Max Concurrency to 4 or 5. SAP recommended value is 5 I believe.

Hope it helps!

Ambrish

[Former Member]

Ok Now:

Sceario 3: system.queueParallelism.maxReceivers 5

max concurrency 1

Java Nodes 4

JDBC_http://sap.com/xi/XI/SystemRecv 15

Still I see 60 messages in delivering status for the interface being tested.

I was hoping to see 5 (max receivers) * 4 Java Nodes = 20 messages only being deleivered at any given time for a single interface.

[baskar_gopalakrishnan2]

Both your case works as expected. If you want different behavior then you have to reduce maxreceiver values while increasing max concurrency..

[rajasekhar_reddy14]

Hi Vicky,

Max concurrency and Max receiver configurtaion has realtion, by defualt PI JDBC adapter support 5 parllel trasanctions, if you increase value to 15 (Max Receiver) then is supports 15 cals parllely.

In your same thing is happening,you have 4 nodes , so 4*15=60 .

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/12/14/decoding-max-concurrency-poolwait...

Thank you,

Raj