Error in JDBC receiver Communication Channel

[Former Member]

Hi,

I am facing a problem at receiver communication channel of JDBC adapter. I am gettting the error as,

"com.sap.aii.af.ra.ms.api.RecoverableException: Channel has reached maximum concurrency(5,000 concurrent Messages) and no free resourse found within 5,000 milliseconds; Increase the maximum Concurrency Level."

I am having the configuration on 4 different nodes. but suddenly only 1 out of 4 is working fine but remaining 3 are throwing this exception. It says to increase Maximum Concurrency level but i want to send only one message through one channel.

Is there a way to rectify this error. I am in deep trouble.

can anyone help me out in solving this issue, Its very greatfull if you do the needy.

Thanks,

Soorya,

[former_member187437 · Accepted solution]

Hi,

See this thread on the same issue.

[Former Member · Accepted solution]

Hello Aarthi,

I have gone through the link which you have provided for me in this regard. But i am not clear why those values,

AFW.Call.maxConsumers 10

AFW.Recv.maxConsumers 5

AFW.Rqst.maxConsumers 10

AFW.Send.maxConsumers 5

JDBC_http://sap.com/xi/XI/System.Call.maxConsumers 20

JDBC_http://sap.com/xi/XI/System.Recv.maxConsumers 10

JDBC_http://sap.com/xi/XI/System.Rqst.maxConsumers 20

JDBC_http://sap.com/xi/XI/System.Send.maxConsumers 10

These are concerned to MS only but not at JDBC adpater.

We have to look at JDBC prospective but not at the MS prospective.

So can you please look into the issue as JDBC adapter perspective.

Its like this that, there are 5000 messages are waiting for the free resource with in the next 5secs and as it is reached maximum concurrency of 1.

So my question here is,

Is there only one option to increase this value to 2 or more?

Or else do we have any other option to overcome this problem.

Please reply to this ASAP.

Thanks,

Soorya.

[Former Member · Accepted solution]

hi

if You are Using PI 7.0 SP 12, You can set the maximum concurrency level for Receiver File & JDBC Adapter.

By Default Maximum Concurrency level=1.

You can the level as per your requirements

regards

krishna

[Former Member · Accepted solution]

Hi,

I am at XI 3.0 SP20.

Is our SP level of XI 3.0 is similar to SP12 of PI 7.0 ?

Previously the messages were processed properly but suddenly in 3 nodes out of 4 are suddenly stuck throwing that error in the auditlog file.

We want the exact reason behind this problem so that we can increase that value as you mentioned.

Thanks,

Soorya

[Former Member · Accepted solution]

Surya,

As of XI3.0 SPS20 (I think it is 20 or 21, can't remember), a new property is available for JDBC receiver adapter to process multiple messages in a concurrent way ... Increasing it could help you (it can need a max thread increase if you set it to a high value)

In your scenario you seem to create a lot of msgs in a short period of time, is that right ? Are those msgs processed quickly at the database level ? We have a quite similar scenario (with less messages but db lookups performed in java mappings), and we ran thru lot of perf issues, mostly due to db performing slowly

Rgds

Chris