Re: [openjms-user] Latency during send

[Rebecca W. <rap...@gm...>]

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

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

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

Rebecca