|
Notes |
|
|
|
a.) Please to not hide the main error message or images in a zip file
b.) The Subject claims compile fails
c.) The description says an error message is shown (that is not compile fails)
b+c are very different things => Please clarify
d.) Please provide the full build output with context and not just 2 lines error message without knowing where they happen
That should include output of the buildvaliation step used in the update (which should have removed the OBRebuildAppender from the active config (see buildvalidation RemoveRebuildAppender) |
|
|
|
|
|
I attach a full log from our instance. It's an instance on Opb cloud. |
|
|
|
(0134535)
|
|
dromero
|
|
2022-01-24 19:06
|
|
|
I added the stacktrace error that the compilation yields (stacktrace_error.txt) |
|
|
|
|
|
I'm not very sure, but the error "ERROR: column column0_.is_child_property_in_parent does not exist" suggests an ant update.database is missing and should be done after the update. |
|
|
|
(0134559)
|
|
dromero
|
|
2022-01-25 17:17
|
|
Following cberner's suggestion I ran an ant update.database, it was successful (see attached file: updateDatabase_successful.txt). Next step, I ran an ant smartbuild and it was also successful (see attached file: smartbuild_successful.txt).
I am going to report this to Practics and if this solves their problem we can proceed to close this issue. |
|
|
|
(0134560)
|
|
dromero
|
|
2022-01-25 17:57
|
|
The problem still persists, unrelated to the above.
Now, to be more precise with what is happening I attach the stacktrace thrown from the client environment after executing the smartbuild (see attached file: stacktrace_error_gdc.txt). The compilation is successful but it still shows those two errors. |
|
|
|
|
Hello again => That could not have helped as it would maybe have fixed wrong commands run but is not related to the initial problem.
The initial problem we are trying to reproduce on our own as not having the required information here.
Below you can find steps to fix any affected instance and checking if an error exists in code exists or not we will continue in parallel.
What would have needed is:
- Output of very first update.database in version 19Q2 in the instance where the problem happened. Not some 2nd or later run the very first update.database.
Note: Most files above are from some developer system not the cloud instance in which the problem happened (probably gdc-u18-test)
Goal verify automated code works fine.
Working example is above in "updateDatabase_successful.txt"
- Once those 2 ERROR lines (to be ignored)
- Then " [java] Removed OBRebuildAppender from log4j2.xml"
- After that everything fine
To just fix the instance you can
- Edit the config/log4j2.xml
- Remove all 3 lines containing OBRebuildAppender (1 comment, 2 active lines)
- After
That buildvalidation RemoveRebuildAppender running on that 'very first update.database' will do that automatically which worked locally (updateDatabase_successful.txt). But for some reason did not work apparently in your cloud instance initially.
Important reminder:
- smartbuild cannot be used for release upgrade
- It cannot work in all cases (i.e. when files are deleted)
- A full recompile is required for any release upgrade
- For example: ant update.database compile.complete.deploy |
|
|
|
|
The issue can be closed because the underlying problem was solved here [1] and the environment where it was reproduced was fixed by updating the log configuration to remove the mention to OBRebuildAppender
[1] https://issues.openbravo.com/view.php?id=48488 [^] |
|
images.zip (72,685) 2022-01-21 22:03
stacktrace_error.txt (9,415) 2022-01-24 19:05