haha okay... it is primarily a file server, also has some other software running on it, another database engine (Microsoft SQL, I think, but that's not my software), that database engine is accessed by client software on laptops connected to the LAN as well as remote connection (windows remote desktop connection)...
outside of that...i really don't understand why @Stateless EJB referencing other @Stateless EJB to perform database operations (insert into multiple tables...'long' transaction)...does 'not' perform well at all, introduces database locks when users are logged in the web app CDI/JSF 'managed bean' referencing @Stateless EJB to perform database operations has been the 'norm' in my web app, and this never introduce database locks, deadlock situation, or people seeing exceptions with eclipselink SQL in their Facesmessage after a long long wait... :) i'm going with the managed bean --> @Stateless EJB approach, just need to change around my code to do so. will keep you posted. On Thu, Dec 13, 2012 at 9:31 AM, Romain Manni-Bucau <rmannibu...@gmail.com>wrote: > that's not the usage of the machine :p > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2012/12/13 Howard W. Smith, Jr. <smithh032...@gmail.com>: > > same machine > > > > On Thu, Dec 13, 2012 at 8:05 AM, José Luis Cetina <maxtorz...@gmail.com > >wrote: > > > >> Where is your database, localhost? >
