It seems that calling a method of a session bean with transaction attribute "NotSupported" takes much more time (up to 10x) then calling the same method with transaction attribute "Required". I'd expected that execution of method without having to create and maintain transaction context will save some time but results are very surprising. Is it normal and known behavior or something was wrong with my test?
The session bean was hosted on JBoss 3.0.0 and was accessed using remote interface (the client and server were on the same machine).
Any ideas and help would be greatly appreciated.
What does your session bean do?
It is likely that it is doing work that
should be done in the one transaction
to allow the caching to work.
Have you tried a method like
public void noop()