Brokers and WebServices Intermittently Failing

We have two sources feeding message IHE Pix V3 and HL7 message both brokers are turned on we are encountering errors when processing messages from both services. There were no changes to the engine. Why may that be?

1 reply

It may be that brokers connected to the engine but the engine was unable to connect to the database and complete the request resulting in the error. A setting you should review is Context pool size (ContextPoolSize) which is the number of operational server threads that are started concurrently. Each context pool has its own connection to the database and can operate independently of the others. If you have your context pool set at 5, for example, you can send in five searches or gets or puts at the exact same millisecond, and they are all processed concurrently. If six are sent, then the first five process while the sixth waits for the next free context. You have this at 10 and that seems a very low number esp since you have 10 inbound brokers. This is set using the contextPoolSize variable using com.initiate.server.net.cfg file. Set it to a higher value and restart.

If that doesn't help, then we need more details like patterns on when and how we get the error e.g. at peak load or when both run together etc. More detailed logging may also help. Other-wise your DBA may need to check why the connections to the database are failing.