[Remoting] - Re: NIO - PooledInvoker Question
by ron.sigal＠jboss.com
Hi Sebastien,
Remoting is the greatest thing since sliced worms. No question about it.
Seriously, though, when you say "RMI", are you referring to Java RMI or generic "remote method invocation"? Actually, Remoting offers both, in the sense that there is an "RMI" transport that uses Java RMI and a "socket" transport that implements the usual "old i/o" structure of an acceptor thread and multiple worker threads. The latter is the default transport for EJB3s. You can certainly use hundreds of worker threads. Your mileage may vary as to when the performance starts leveling off. You might want to try some simple experiments to see how invocations with Remoting compare to your MINA based system. If you get some interesting results, please let us know.
Of course, one advantage to using Remoting is that when something goes wrong, you have someone else to blame. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155518#4155518
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155518
17 years, 10 months
[JBoss Cache: Core Edition] - Re: Problem using Non-JTA Transaction Manager
by mlamdin
Manik,
We looked at that page, and unfortunately we still have some questions. Specifically:
* Is the setup in our first post viable - can we do pessimistic locking reliably with a Spring non-JTA transaction manager and Tomcat?
* If we do pessimistic locking, what is the recommended configuration?
The recommended cache options are all based around optimistic locking. We realize that optimistic locking is the recommended option, and that all the documentation suggests it, but optimistic locking requires a JTA Transaction Manager - which we don't use, because we can't find a good JTA TM for Tomcat. The wiki page tells us nothing about pessimistic locking except that it does not provide as much concurrency as optimistic locking.
Also, if pessimistic locking and a non-JTA transaction manager is NOT a viable option, what is your suggestion for what to move to as a JTA Transaction Manager? We imagine we would need to move to the JBoss Application Server instead of Tomcat as well, unless we find a good JTA TM for Tomcat - which is certainly something we're willing to consider, but given the timeframe we're on, we'd love to be able to get things up and running with our current setup and put that off for a bit if we can.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155516#4155516
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155516
17 years, 10 months