1) How you are integrating with MA systems (Sync or Async) ?
if it’s a Sync call, increase global transaction timeout , by default it will be 180 sec.
or
if it’s Async - you need to check your design that it’s really required to go with Async , as you said your transaction is waiting for long time. In ESB's you can set callout time.
At the moment, WPS making Sync calls to the backend system, and global transaction timeout in WPS server is 120 secs.
2) Have you guys did performance testing ?
No, there was no performance testing done on WPS server.
3) Connection pool size 10 is very low. Min 50 is recommended.
Yes, we are looking for the recommendation and can be considered. Can you please let us know , by increasing the connection pool size will there be any other issues like performance that may arise. As mentioned, WPS server is a stand-alone at the moment.
4) what is the connection pool type
Recommended to use non-XA data source if your data is not critical and you don't have auto roll back mechanism.
By default it was enabled in the WPS server, and we are logging each and every transaction in WPS server.
5) you need to increase maximum heap size to get rid of Out of Memory exceptions . 768 mb is recommended you can increase to 2 GB if you have enough RAM.
Currently we have minimum heap size as 4 GB and maximum heap size as 10 GB. And our current RAM is 42 GB and looking for some recommendation on this.
6) Ask WPS admin to increase thread pool size. It can also be the reason for hung threads/out of memory exception.
Web Container thread pool size is minimum 50 and maximum 50 and MQ thread pool size is minimum is 1 and maximum is 40. But we are looking for the recommendation here to increase the thread pool size.
