- Make sure the number of HTTP Listener threads is configured high enough in GlassFish to support making multiple simultaneous calls to both Mirth Results and Mirth Match. This is important especially if Mirth Match is running in the same GF instance as Mirth Results.
- Making the channel that posts to Mirth Results unsynchronized can greatly increase performance. However, the tradeoff is that messages will not be delivered in order. In the future, the application should not care about order, and instead, look at the timestamps of the messages.
- Connection pool size for Glassfish Database pools
- domain.xml should specify an Xmx parameter for Glassfish that is sufficiently high for your environment and available RAM
Labels: