On Sat, Mar 23, 2013 at 5:35 PM, Romain Manni-Bucau <[email protected]>wrote:
> if the log line bother you but not the transaction just configure logs to > not write it. > > Understood. It's definitely not a bother to me; it's more of a 'nice-to-have'. :) > > about mdb/async: if async is needed you dont need the overhead introduced > by JMS/AMQ (serialization...) > > interesting... i see no overhead at all. JMS/AMQ handling multiple message queues for me already and hoping to add more. I have even decreased the amount of Xmx needed by my app (did that some months ago); had it at 4096, but now have it at 1024, and honestly, jvisualvm never tells me that app is coming close to 1024. i have experienced and seen a delay when @Schedule and JMS/AMQ is running as it is doing multiple things... IMAP connection to get emails and insert data into database. when i had my old production server, the database would deadlock, but since the new server is faster and we have faster internet connection now... i only see a slight delay, if i'm in web app while @Schedule and JMS/AMQ doing its thing. i think the database may be where the bottleneck is; it's definitely not the lack of CPU, network connection, etc... i still may have a thing or two i need to learn about @Stateless inserting data into database via @Schedule and JMS/AMQ...to avoid deadlock. I did set @AccessTimeout to 2 minutes on @Singleton bean, even though the lock never seems to take that long. With the code and configuration in place, this all is working well and I have seen 'no' deadlock errors in the log as I did when we had the older/slower server. :)
