Hi Phillipe,
thanks for looking at my problem.
> I'm not sure to understand what you do. You have replaced REQUIRED by
> SUPPORTS for those methods that are read-only: Ok. You never start
> transaction by yourself with UserTransaction interface, correct ?
Yes this is correct
> If this is correct, with JOnAS 2.0, you should get about the same
> effects:
> FOr each REQUIRED method, the container will create a transaction and
> commit it after the request. For each "read-only" method, no transaction
> will be created if the SUPPORTS attribute is chosen, but the bean state
> is read before the request, and written after, so this should not
> be optimized. This has been changed in jonas 2.1: now the bean state is
> kept in memory if the bean instance is not implied in a transaction
> (entity beans only).
This is exactly what is happening, exept the beans are read-only so we never
change them so they are never written back to the database. Basically our
client
makes one call to the server to fetch some data. In the case of REQUIRED
this
call to session bean creates the transaction and all the data collating is
done
within boundaries of this transaction. Once we changed the attribute to
SUPPORTS
no transaction is being created and the data processing should be the same.
> Concerning addConnection and removeConnection, they are called only when
> you are outside a transaction, but I don't think it takes a long time.
> (???) The reason for that is to keep track of the connections open outside
> transactions to be able to enlist them later when a transaction is
started.
I understand this. The only reason I asked about this was that this is
operation
I see in the trace file to be executed frequently.
> A good way to speed up your application with jonas 2.0 (and also 2.1)
> is to use the isModify() facility in your entity beans: for each
> read-only method, the bean state will not be written in the database any
more.
This is exactly what we are using. All our beans have build in support to
set
modified flag and we use isModify method to signal this to Jonas.
> You can also speed up by creating transaction yourself and committing it
> after many requests (long transactions instead of 1 transaction per
> request)
When we need transactions because the beans are being modifies Jonas
transactions work for us perfectly.
If I can I'll try to send you two trace files, one would transaction and one
withour
and I would greatly appreciate if you can take a look at it and maybe you
will notice something
else we missed which is causing this slow down.
Thanks a lot,
Miroslav Halas
Software Engineer
Compuware Corp.
15305 Dallas Parkway Suite 900
Addison, TX 75001
phone: 9720-960-0960
fax: 972-960-8489
email: [EMAIL PROTECTED]
----
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".
