cancel
Showing results for 
Search instead for 
Did you mean: 

Messages are in Tobedelivered...

former_member190681
Active Participant
0 Kudos

Dear Experts,

I am getting an issue in Engine status, messages are in Tobedelivered State, Engine status --> backlog Monitoring also shows so many messages.

After some time those are going, but here when i am checking Addition Data--> Threads those are fully utilized 15/15.

We maintained Thread count is 250 and We are assigned worker threads for asyn and sync 15,15,12,12.

suggest me how to resolve this issue.

Regards,

Kiran Polani


Accepted Solutions (1)

Accepted Solutions (1)

former_member190681
Active Participant
0 Kudos

Dear,

Some times we are getting so many queues in engine backlogs, but is going automatically. thread count is 300 only but as per those sap note that is not mentioned 350 to more. how much value i can increase.

Please suggest what can i do for this.

Regards,

Kiran Polani

former_member190681
Active Participant
0 Kudos

Dear all,

Thanks for your support, i found this error in SAP Idoc level and those are checked with processing inorder check box in SAP side. that's why Queues are going slowly one by one.

After unchecking that check box queues are going smoothly and increased worker threads for fastning Queues and given priority for that interface as per SAP Labs Suggestion.

Regards,

Kiran Polani

Answers (7)

Answers (7)

former_member190681
Active Participant
0 Kudos

Dear Hiren,

Currently we are having Thread count in java is 250 and worker threads are 15,15,12, 12.

Please find the Messaging system screen shot.

Regards,

Kiran polani.

Former Member
0 Kudos

Hello Kiran,

Check the Thread's for each adapter, which i think you would see in technical details.
See the scenario for which you have high volume of messages (for e.g. - File Adapter has high volume) you need to increase that thread count. Also when you are facing with such slow processing issue, kindly take snapshot and check if the Adapter threads are available or not. Usually these would be fully consumed.

Regards,

Hiren

Former Member
0 Kudos

Hi Sri,

what is SAP PI version and  do you have any third party components deployed in PI system like seeburger etc..?

how many java nodes in the PI system? what is the max heap memory allocated to Jlaunch processes? check for any memory leaks.

how many threads allocated to the queue ?

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

Cheers

Hidayat

former_member190681
Active Participant
0 Kudos

Dear Ansari,

We are currently in sap pi 7.0, we are using only AtoA applications. like jdbc,rfc,soap,proxies. java nodes are one.

Yes00 / 015
File_http://sap.com/xi/XI/SystemCallYes00 / 012
File_http://sap.com/xi/XI/SystemRecvYes00 / 015
File_http://sap.com/xi/XI/SystemRqstYes00 / 012
File_http://sap.com/xi/XI/SystemSend


RFC_http://sap.com/xi/XI/SystemCallYes00 / 012
RFC_http://sap.com/xi/XI/SystemRecvYes00 / 015
RFC_http://sap.com/xi/XI/SystemRqstYes01 / 112

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

Yes00 / 015

SOAP_http://sap.com/xi/XI/SystemCallYes04 / 412
SOAP_http://sap.com/xi/XI/SystemRecvYes00 / 015
SOAP_http://sap.com/xi/XI/SystemRqstYes00 / 012
SOAP_http://sap.com/xi/XI/SystemSendYes00 / 015

JDBC_http://sap.com/xi/XI/SystemCallYes00 / 012
JDBC_http://sap.com/xi/XI/SystemRecvYes12115 / 1515
JDBC_http://sap.com/xi/XI/SystemRqstYes00 / 012
JDBC_http://sap.com/xi/XI/SystemSendYes00 / 015

1) we are allocating thread count is 250, what is the maximum value we can increase threadcount?

2) worker threads are assigend for system call is 12, systemRqst is 12 and system Recv 15 and SystemSend is 15. is these values are ok. or we can change.?

3) from which value we can change and can we change the value adapter wise.?

We are facing issue for soap and jdbc adapters those are using all resource from given.

Please suggest me what we can do for this.?

Regards,

Kiran polani

Former Member
0 Kudos

Hello Kiran,

Kindly check the below notes and you would have to use Poolwaiting time parameter.

Note 937159 – To be used for the stating our point of failure and increasing ThreadCount.

Note 821267 and 1473299– To be used for suggesting poolWaitingtime parameter.

This should fix your problem.

Regards,

Hiren

former_member190681
Active Participant
0 Kudos


Dear,

As per that doc those parameter are set with proper values. but issue is not resolved. when load is come we are getting issue in XI.

Please advise.

Regards,

Kiran Polani

Former Member
0 Kudos

Hello Kiran,

Can you give screenshot of the messaging system. You would have to increase the thread count of the particular adapter for which you have high volume.

Regards,

Hiren A.

former_member190681
Active Participant
0 Kudos

Dear Harish,

It is not coming to all interface few particular business systems(3,4 BS at receiver end).

Regards,

Kiran Polani

Harish
Active Contributor
0 Kudos

Hi Kiran,

If it is happening for SOAP receiver then you need to identify which pipe line step is taking more time.

Most of the cases performance issue is occure in transformation step (mapping), please check if you have any lookup (RFC/JDBC) in mapping. or because of large message size.

Please check the below document

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f...

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2016a0b1-1780-2b10-97bd-be3ac6221...

blog

regards,

Harish

former_member190681
Active Participant
0 Kudos

Dear Team,

I checked in Pipeline steps, we are getting delay in DB_ENTRY_QUEUING taking longer time to execute for few messages and for few DB_SPLITTER_QUEUING.

Please find the below screenshots for reference.

screen 1:

Screen 2:

Please suggest me what we can do for this.

We are maintained

In J2EE Visual Administrator --> messaging.connections

Messaging System parameters :

Send.maxConsumers=15

Recv.maxConsumers=15

Call.maxConsumers=12

Rqst.maxConsumers=12

is there any change required. Please suggest me.

Regards,

Kiran Polani

Harish
Active Contributor
0 Kudos

Hi Kiran,

Please check the below discussion

The below blog will also useful

regards,

Harish

former_member190681
Active Participant
0 Kudos

Dear Harish,

We unchecked in we20 "Queue Processing" in sap R/3 end for Idoc and unchecked in "Maintain Order at Runtime" in inteface Determination in XI level for avoiding EOIO format. Now those are going EO only with in XBT* Queues. But some times queues are going slowly and at a time in smq2 2000 messages are coming to XI end from R/3 Server, those signals going with 4, 5mins, but why suddently singals are coming to XI End & in Engine status Backlogs also we are able to see 1000 queues those are going but taking some time.

Regards,

Kiran Polani

Harish
Active Contributor
0 Kudos

Hi Kiran,

I believe this is performance problem with server if it is happening for all interfaces.

Please check the SAP note 894509 - PI Performance Check.

Please also check below blog

regards,

Harish

former_member190681
Active Participant
0 Kudos

Dear,

All interfaces are getting this issue, those are Idoc to soap, Proxy to jdb, jdbc to proxy. It is not stucking long time but "Processing Backlog (without errors)" each Business service/system having 500 to 1200 messages. it is going slowly.

Please suggest..

Regards,

Kiran Polani

Harish
Active Contributor
0 Kudos

Hi Kiran,

Do you configured EOIO for scenario?

regards,

Harish

Harish
Active Contributor
0 Kudos

Hi Kiran,

Please check the below blog

regards,

Harish

former_member190624
Active Contributor
0 Kudos

Hi Kiran,

Message ToBeDeliver means that the message is sitting in the queue waiting to be processed.

In most situations, when this happens and stays there for a long time is because 1st message is the queue is being held up by an error.

BTW, what is your scenario ?  what is your receiver system ?

Thanks

Hari.