you had right, adrian. 'IT' was a stupid logging issue, that tricked me showing that waiting time was in remote jboss. on another logging level i discovered that this time (about 2 sec) was spent commiting data in the destination db. Quite stupid, but that is, when the project grows, the details aren't obvious anymore..
the other issue (Singleton) is still open, there are db deadlock problems when parallel MDBs are running. thanx anyway ! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871320#3871320 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871320 ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
