Threads Assigned/Working in engine status table

[Former Member]

Hi everyone,

we have a problem with our own adapter. This adapter is deployed on a PI 7.11 SPS05 (this is an sps, you should not use) with two server nodes. We've found out in the "rwb --> component monitoring --> adapter engine --> engine status --> aditional data (Queues)", that our adapter has been assigned all threads on server node 0. But on the other server node, the adapter is working just like the other adapters listed in the table.

Queue Name -

---

Started----Number of Entries in Queue -

---

Threads Assigned/Working -

---

Maximum Number of Threads

http://TranslatorRecv -

---

Yes -

---

0---5 / 5---5 (server node 0)

http://TranslatorRecv -

---

Yes -

---

0---0 / 0---5 (server node 1)

We don't know what happened to the adapter. So we just un-deployed it and refreshed the table. But it shows that there are still 5 threads assigned to the adapter and working. Could some one please tell us, what for a high technology from Mars has been used by SAP on this position? How can we configure the (max.) threads assigned to the adapter? How can we delete/stop the threads assigned to the adapter?

best regards

Xiang

[former_member4985 · Accepted solution]

Hi,

To increase the parameter of MaxThreadCount, follow the instructions below:

1. In the left frame choose Server -> Kernel -> ApplicationThreadManager

2. In the tab Display Configuration (right frame) choose Switch between

view and edit mode to activate the edit mode.

3. The parameter MaxThreadCount must be set to 350 (no higher).

4. You will then need to restart the J2ee

For reference see note #937159 - XI Adapter Engine is stuck

For specific setting to the adapter can be done by going to the Visual

Administrator -> Services -> SAP XI AF Messaging

Look at the property 'Messaging connections' here you will see the

following queues:

Send.maxConsumers (asynchronous sending - outbound)

Recv.maxConsumers (asynchronous receipt - inbound)

Call.maxConsumers (synchronous sending - outbound)

Rqst.maxConsumers (synchronous receipt - inbound)

Depending on where the bottleneck is occurring (i.e. too many entries in

the Send.maxConsumers) you can increase these parameters.

Exemple of parameter value syntax (example for FILE adapter):

(name=FILE_http://sap.com/xi/XI/System, Send.maxConsumers=10, Recv.

maxConsumers=10, Call.maxConsumers=10, Rqst.maxConsumers=10)

For reference see note:

#791655 - Documentation of the XI Messaging System Service Properties

And see the link:

/people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11

For failed messages, check:

#813029 - Automatic processing of failed XI messages

Regards,

Caio Cagnani

[Former Member · Accepted solution]

Hi,

thanks a lot for your help. It solved my problem.

best regards

Xiang