>> Currently our configuration is jsp/servlets in Jetty -> Jonas with
Jeremie
>> -> Interbase. Jetty and Jonas are running in the same VM. Jeremie has
made
>> the whole system about 3 times faster which solved our problem for now,
but
>> RMI was major bottleneck and some transactions were taking forever. What
we
>> want to preferable do is to set longer default timeout for all
transactions
>> in the system. We would like to set this when Jonas is started so that
all
>> transactions are created with this longer timeout. We couldn't find any
way
>> how to do it, except changing the hardcoded constant in Current.java
(what
>> we did for RMI_jonas). Is there any other way? The example I sent you was
>> just workaround, where we explicitly coded transaction and set the
timeout
>> around operation which was causing us most problems, but this is not
>> desirable solution. We chose CMP and container demarcated transaction
>> boundaries so we don't have to worry (at least at this point) about
>> persistence and transactions and it would be quite painful to code
>> transactions like this for every operation which can potentially take
longer
>> time (system has at present time 40-50 beans and will grow rapidly in
next
>> couple of weeks). Thanks for your help.
>It is not possible today to modify the default timeout value. You can only
do
>it for all transaction started by the calling thread.
>We could do this easyly by introducing a property tm.timeout dans
jonas.properties
>I will consider this for the next version...
That's what I thought. The problem is that in J2EE environment when the
beans are called from the servlet you have no guarantee from which thread
the servlets are invoked.
This brings another question, security context/authentication. As I
understand from my experiences with Weblogic, the security context is
established by creating JNDI context with proper credentials (username and
password). Weblogic (last researched for release 4.51) always associates the
thread with the security context of the last created JNDI context (with
supplied credential) in that thread. This imply that in environment with web
browser as the client and servlets interfacing with EJBs, the servlets has
to create JNDI context each time there is request from the client to
establish the proper security context for that user (if we want to use
security roles/method permissions enforced by app server). Do you have any
idea, how expensive is such possible frequent creation of JNDI context? What
are your plans for implementing security roles/method permissions in Jonas?
Thanks,
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".
