"Recurrence" unit test errors in server environment post-Jade upgrade

[Tommy Butt]

Hi There,

We have applied NexJ Finance 7.2.0.2 721.1305.146.46_jade upgrade followed by nexj_contact_jade_ga_sp1_7.2.1.1.

Since the upgrade, the “Recurrence” unit test run has been encountering optimistic lock errors. This error has affected test cases from “testWeeklySeries” onward. Attempts to re-organized the test script by re-arranging read, commit and reset-context, and clearing up test data in the initializer has received mixed results.

Subsequently the unit test mode was changed from “dirty” to “sequential”. This has resulted in successful runs on my local environment. After checking in the changes, Recurrence was executed as part of the full suite run on the development server environment using Bamboo. The test would successfully run the first Recurrence test case “testStartTimePatternRegenFromEnd”, but before the second test case could commence, would always fail with various errors (see attached files). The error would terminate the run stream, leaving subsequent unit tests un-ran.

Recurrence was ran on its own in the server environment using command line, but error continues to occur after the first test case, presumably in the database recreate stage before the next test case run.

A suggestion was provided to put (((invocation-context)’interceptor)’complete ‘() 0 0) in the Finalizer to see if that works around this issue, by disabling data rollback for this test and just reset the database. However the error continues to happen in the server environment.

Any suggestions on how to resolve either the optimistic lock errors in “dirty” mode, or the recreate error in “sequential” mode, would be appreciated.

Thanks.

Tommy

ANZ

 

0

Attachments:

You must be logged in to view attached files.

[Ed Shaw]

This is a project environment specific case and will be handled by the services team.

0

[Ed Shaw]

This is a project environment specific case and will be handled by the services team.

0

[Author]

Posts