Hi,
I would like to ask you about your opinion. We are still using Jonas 2.0 and
not planning to move to 2.1.x before most of the bugs are resolved and we
are able to modify our code to be fully EJB 1.1 compliant. In between to
speed up our application and get around the connection-underflow problem we
see sometimes in Jonas we modified all our read-only methods to have
TX_SUPPORTS instead of TX_REQUIRED attribute. In the first case the first
call to our app server created one transaction and all subsequent calls were
within this transaction. After the modification no transaction is created at
all (which is what we wanted) but the whole processing takes about 3 times
longer. Using trace levels 4,5,6,12,14,15,16,17,31 I can see in the first
case creation of the single transaction and all the context synchronization.
In the second case no transaction is created but I see calls to
Current.addConnection() and Current.removeConnection() being executed
extrememly frequently. I assume this is the problem of our slow down
(because in first case it looks like much more code gets executed). So my
question is, is this normal behaviour to call
addConnection()/removeConnection() so often or is it a problem in our
configuration? Coan this cause this problem? Is there some workaround
available to speed this up (I assume that the connections are cached).
Our configuration: Jonas 2.0. Jeremie, Windows 2000, JDK. 1.2.2.006 ,
Interbase 6.0.1, Interclient 1.6.1
Best Regards,
Miroslav Halas
Software Engineer
Compuware Corp.
15305 Dallas Parkway
Suite 900
Addison, TX 75001
phone 9720-960-0960 x 1333
fax 972-960-8489
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
