In most cases, that's OK. But we meet problem when our permission-service
need to access new record created in main transaction. It cause dead
locking in Derby database.
I find the following code piece:
resp = dispatcher.runSync(permission.name, ctx, 300, true); //
In most cases, that's OK. But we meet problem when our permission-service
need to access new record created in main transaction. It cause dead
locking in Derby database.
I find the following code piece:
resp = dispatcher.runSync(permission.name, ctx, 300, true); //
In most cases, that's OK. But we meet problem when our permission-service
need to access new record created in main transaction. It cause dead
locking in Derby database.
I find the following code piece:
resp = dispatcher.runSync(permission.name, ctx, 300, true); //
Same question. No body interests?
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Adjustment-functionality-in-Quote-Order-module-tp4634189p4644286.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
hi, Jacqies.
I'm using latest groovy plugin which version is 2.6.1, groovy runtime plugin
1.7.10 and 1.8.6.
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Unable-to-debug-groovy-script-called-by-screen-widget-tp4533949p4536704.html
Sent from the OFBiz - User mailing list