Re: Latency during send

Okay, so apparently someone in my group figured out what it was, or at least 
what we can most accurately hypothesize that it was. It seems there's a 
binary flat file called openjms.db that lives in one of openjms' 
directories, like bin. But apparently that file is created in whatever 
directory you start up openjms from. So somehow one got into the init.d. So 
every time you boot it was trying to read that file, to no avail. That was 
one thing. 

The other thing was that, though our messages are not persistent, the 
correct openjms.db had been storing whatever it stores and had grown to 200 
MB or so. We're guessing it's traversed linearly, so that'd take up a bit of 
time. So probably every time we sent it was trying to write something to 
openjms.db but before it could do that it had to figure out where the bottom 
of the file was, or some such thing. 

They switched to an acutal database in lieu of the flat file and removed the 
extraneous openjms.db and the send time came down to 70-100ms, which is much 
shorter than 500-600ms.

Rebecca