| Re: [eclipselink-users] transactions in singleton EJBs - pulling NXA resources in GFV3 |
Posting to Glassfish may be better. What do you mean by NXA? What are you seeing exactly? Most application servers optimize JTA transaction to not use XA if only a single resource is involved in the transaction. meetoblivion wrote: > > Hey all > > I'm not sure if this would be classified as an eclipse link issue or > another > component in glassfish. > > I've noticed recently and confirmed today that singleton EJBs in glassfish > v3 attempt to use NXA resources when the transaction commits. This seems > like a very odd behavior, and I didn't see anything reading over EJB 3.1 > that would indicate this non transactional behavior; in fact it seems like > it should be transactional. > > Any ideas on why this might be happening? Or should I be sending this off > to > the glassfish team? > > Thanks! > ----- http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland http://www.eclipse.org/eclipselink/ EclipseLink , http://www.oracle.com/technology/products/ias/toplink/ TopLink Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink , http://wiki.oracle.com/page/TopLink TopLink Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink , http://www.nabble.com/EclipseLink-f26430.html EclipseLink Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence -- View this message in context: http://old.nabble.com/transactions-in-singleton-EJBs---pulling-NXA-resources-in-GFV3-tp28009696p28082923.html Sent from the EclipseLink - Users mailing list archive at Nabble.com.