D
dbeavon
Guest
By that definition, are you saying that multiple distinct _progres processes share a single AVM? Your second paragraph didn't use this TLA enough. It wasn't clear where you draw a boundary between one AVM and another. I suppose I wasn't very clear myself, for that matter. When I think of a JVM, it is an executing process that contains shared resources. See the following link... www.javaworld.com/.../what-is-the-jvm-introducing-the-java-virtual-machine.html ... "When developers talk about the JVM, we usually mean the process running on a machine ..." In my mind a JVM (or AVM), it is defined by an execution context with resources that are being shared. For example an AVM would create only *one* instance of a shared singleton; and it will only run a static constructor *once*. If there are static constructors being run on *every* ABL session, then it seems to me that each of them should be considered *separate* AVM. >> the agent process has one copy of the avm code I'm assuming you are talking about the $DLC installation, rather than custom r-code. I'm quite certain that each ABL session within PASOE has its own copy of ABL r-code. Consider this scenario for example, you use the "-q" startup parameter and you deploy new r-code, and trim a subset of sessions (inactive ones). That would allow the new sessions to pick up different r-code files - since changes were made to r-code in the underlying PROPATH.
Continue reading...
Continue reading...