Posted: Wed Mar 21, 2007 8:27 pm Post subject: Broker JVM Threading Model - In regard to Java Computes (v6)
Master
Joined: 16 May 2001 Posts: 200 Location: Green Bay Packer Country
I'm trying to get an understanding of how the broker's JVM does threading for java code invoked from a Java Compute. I understand the JVM is running inside the broker's PID. Does it consume/use one thread or multiple theads. Do you do something progromatically to make any of his happen? It looks shared and single threaded to us as we recently added a cache table to our code and could see it being updated from two different flows. We don't have any explicit thread related code in it. The doc talks quite a bit about an input node. This is NOT that. We are trying to understand from a Java Compute perspective in the middle of a flow. Is there any way to adjust these threads if there is just one or a pre-set number. Any code considerations for this? _________________ Thanks!!!
There's one JVM per EG. That means each EG is a separate runtime.
Each instance of a message flow is a thread in an EG. That means that all JCNs in a flow will run in the instance thread (or a thread tied to the instance thread). So you won't get one thread for all the ESQL, and then one thread for each JCN, you just get one thread. _________________ I am *not* the model of the modern major general.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum