0005131: Transaction Problems with high-performance option

ID	Project	Category	View Status	Date Submitted	Last Update

0005131	OXID eShop (all versions)	4.05. Performance	public	2013-05-29 16:48	2013-06-05 14:04

Reporter	manuel	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	resolved	Resolution	fixed
Product Version	4.7.3 / 5.0.3 revision 54408
Fixed in Version	4.7.4 / 5.0.4 revision 57063

Summary	0005131: Transaction Problems with high-performance option
Description	Currently, the high-performance option contains several orders with missing transaction data when Paypal or Saferpay was used. In my opinion, the reason for this is that during checkout oxid loads objects such as oxuser, oxaddress, etc. from the database and that this query runs against the slave. For example, if a new user is created, this happens in several steps and generates multiple writing processes on the master. If the object is loaded from the slave shortly afterwards, it is possible that the data has not yet been replicated and one receives an empty user-object. If the billing information from this is used for the order, one receives an order without a billing address. Apparently, a similar process happens with objects such as oxuserpayments. Normally Oxid should change all objects during checkout, keep it completely in the session or run the queries for this objects during the checkout against the master. (which the high-performance option might question).
Tags	No tags attached.

Theme	Both
Browser	All
PHP Version	5.3
Database Version	any

Linas Kukulskis 2013-05-30 09:12 reporter ~0008729	User (and default object) creation moved to master with a fix 0004891. Recheck checkout process and possible other object creation which has creation in several steps.

aurimas.gladutis 2013-06-05 14:02 reporter ~0008751	These problems should have been fixed with 0004891, as it not only fixes oxuser object, but also problems with saving objects extending oxbase class. If you are still experiencing any problems, please give some more details on what are the conditions for the problem to occur, what data is missing in orders etc.