[progress Communities] [progress Openedge Abl] Forum Post: -rereadnolock For Oepas

[mroberts@rev.com.au]

Hi All, OE 11.7.1 We are using PASOE, and have just found that -rereadnolock is not working for us. We have user A updating a record status in a PAS based web app to "Confirmed". User B updates the status via classic appserver and a GUI UI to status "Cancelled" User A goes and gets the record again no-lock, and the status is still "Confirmed" Debug code in the PAS called code shows that the read of the record is returning the "Confirmed" status, even though the GUI app and an editor session show the new Cancelled status. Out thought has moved towards -rereadnolock, and whether it is set. We *thought* we had it set OK, adding it to the pf file that is referenced in the agentStartupParam agentStartupParam=-T ${catalina.base}/temp -pf ${catalina.base}/conf/startup.pf startup.pf has -rereadnolock in it We know that the pf file being read, as the db connections in there are being used OK, so that cant be the problem Looking at PAS migration for -rereadnolock https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/pasoe-migrate-develop/setting-the--rereadnolock-parameter.html It implies that the sessionStartupParam in openedge.propeties should be set. This is where the confusion sets in openedge.properties does not have a sessionStartupParam https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/pasoe-migrate-develop/migrating-classic-appserver-properties.html makes reference to AppServer.Agent.sessionStartupParam When I use oeprop to try to add sessionStartupParam, it returns Property not found When I add it manually, it does not seem to pick it up So my dilemma is 1) Do I have the -rereadnolock option in the wrong property for it to work (in agentStartupParam or sessionStartupParam) 2) Do I have it in the right spot, and for some reason rereadnolock is not working Anybody got any thoughts on this one? I'd like to clear up the confusion on the best place to set it before I dig deeper into whether it is not working at all. Thanks Mark

Continue reading...