Interesting article!

I encountered Business Process variation of this issue recently and would like to add that setting  SKIPMESSAGEHISTORY parameter is not always a complete solution. It disables sent/received reference history, but pending messages are still stored in a collection (no way around it).

In cases where one BP instance waits on more than ~10 000 messages simultaneously same issue occurs (I got a journal file per minute on 50 000 pending messages).

The recommended approach would be to change architecture layout so that one process would wait on a more reasanable amount of messages.

Does ensemble can limit request speed at Business Service?  too many requests slowdown my service.

InterSystems IRIS comes with InterSystems API Manager which is designed for these kind of tasks.

But at the message trace page. I can't found any source address .  

You can use $$$TRACE to capture additional information. Also CSP Gateway has additional request tracing facilities. Here's how you can enable tracing there.

But most importantly as I said in your previous post it looks like you're running Ensemble service on a custom port. First thing you need to do is:

  • Install public web server
  • Adjust web server configuration for better performance
  • Connect it to Ensemble
  • Switch Ensemble Business Service to use public web server

Values looks correct (I assume Ipaddress is in fact replaced by an ip address or a hostname).

I think the issue is the access to the driver library.

Check that the user you're running the app has access.

Maybe you need to specify the path with double slashes.

Also try copying the jar file into your app directory.

On the other hand InterSystems offers a very flexible and powerful full text search solution, as a part of InterSystems Cache - iFind (Also known as InterSystems SQL Search for InterSystems IRIS). Try it out to add full text search to your application.