cancel
Showing results for 
Search instead for 
Did you mean: 

Performance issue in adapter

Former Member
0 Kudos

Hi

I see that there is some performance issue in JDBC adapter.

we are log SQL Query true in receiver . I did not find anywhere that it would hinder the performance.

If someone has  encountered a similar issue, do let me know

Venkat.

Accepted Solutions (0)

Answers (4)

Answers (4)

naveen_chichili
Active Contributor
0 Kudos

Hi,

Could you please let us how the performance is effecting?

also please check the below note for JDBC adapter issues...

Note 831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 / PI 7.3 JDBC Adapter

Reg,

Naveen.

former_member192238
Participant
0 Kudos

venkat,

In RWB in communication channel go to engine status --->go to Queues check the number of threads for followingJDBC Queus

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

JDBC_http://sap.com/xi/XI/SystemRqst

JDBC_http://sap.com/xi/XI/SystemSend

by default max no of threads will be 5.

Genrally if there are more JDBC receiver channels you will face issue like messages will go in to schedule state becuase some times five threads may not be sufficient .

Increase the threads for this queue JDBC_http://sap.com/xi/XI/SystemRecv then you can see the performance improvemnt.

If you are using 7.1 version in NWA you can increase.

Regards

Praveen Reddy

Former Member
0 Kudos

Hi,

logSQLStatement to True should be used only in dev system and not encouraged to use in prod system..

Are you ending up messages in ToBeDelivered state for this interface ??

if so jdbc adapter can be tweaked to resolve the above..

as siad earlier provide more info on the issue facing..

HTH

Rajesh

rajasekhar_reddy14
Active Contributor
0 Kudos

what exactly your issue? JDBC adapter performance depends on many factors.

give more info about you design and problem.i will try to help you.

Former Member
0 Kudos

as process of performance improvement measures, I was wondering to remove this one.

has SAP provided any documentation that usage of this should be restricted to avoid performance issues?

~V