Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0008885Openbravo ERP01. General setuppublic2009-05-04 22:452010-01-05 14:07
elopio 
marvintm 
normalmajorrandom
closedno change required 
30
2.50 
 
Core
No
0008885: ** instead of the name of installed modules
In General Setup || Application || Module Management || Module Management > Installed Modules.
The first box lists the names of installed modules. It shows only ** (see attached image).
This doesn't happen in the other QA machine that uses oracle.

install working pi context
Then use 'ant create.database -Dapply.on.create=true' to recreate the db
Do not recompile but just restart tomcat
Go to mmc see the issue hapennening
Problem is that the data in the ad_table does not contain a correct valid value for the generated field which stores the column_identifier sql code.

A single run of this pl-function updates this field:

SELECT ad_update_table_identifier(null,'N');

Afterwards the display is immediately correct.

As this function is called on compilation (start of wad) a recompile does 'fix' the problem.

Adding a call to some ant target executed on -Dapply.on.create=true' should fix it.
250MP1, Modularity
related to defect 0011416 closed mtaal ad_update_table_identifier fails silently after a new table trigger change 
png core.png (22,566) 2009-05-04 22:45
https://issues.openbravo.com/file_download.php?file_id=1253&type=bug
png
Issue History
2009-05-04 22:45elopioNew Issue
2009-05-04 22:45elopioAssigned To => rafaroda
2009-05-04 22:45elopioFile Added: core.png
2009-05-04 22:45elopioRegression testing => No
2009-05-04 23:01elopioNote Added: 0016029
2009-05-04 23:08elopioTag Attached: 250MP1
2009-05-05 12:17psarobeTag Attached: Modularity
2009-05-05 12:18psarobeNote Added: 0016043
2009-05-05 12:19psarobeAssigned Torafaroda => alostale
2009-05-05 12:19psarobeSeveritycritical => major
2009-05-05 12:19psarobeReproducibilityalways => random
2009-05-05 12:19psarobeStatusnew => scheduled
2009-05-06 10:52pjuvaraversion => 2.50
2009-05-11 13:00alostaleNote Added: 0016258
2009-05-11 13:00alostaleStatusscheduled => feedback
2009-05-11 19:09elopioNote Added: 0016276
2009-05-12 09:54plujanStatusfeedback => new
2009-05-12 09:56plujanNote Added: 0016285
2009-05-12 09:56plujanPriorityurgent => normal
2009-05-12 09:56plujanStatusnew => scheduled
2009-05-12 09:56plujanfix_in_branch => pi
2009-05-18 10:58alostaleNote Added: 0016414
2009-05-18 10:58alostaleStatusscheduled => feedback
2009-05-19 17:58elopioNote Added: 0016472
2009-05-29 09:35psarobeNote Added: 0016748
2009-05-29 09:40alostaleNote Added: 0016749
2009-05-29 10:46psarobeStatusfeedback => scheduled
2009-06-01 22:32elopioNote Added: 0016829
2009-07-16 11:55alostaleStatusscheduled => closed
2009-07-16 11:55alostaleResolutionopen => unable to reproduce
2009-07-16 12:14psarobeNote Added: 0018307
2009-07-16 17:55anonymoussf_bug_id0 => 2822541
2009-10-20 17:25shuehnerAssigned Toalostale => marvintm
2009-10-20 17:25shuehnerStatusclosed => new
2009-10-20 17:25shuehnerResolutionunable to reproduce => open
2009-10-20 17:26shuehnerNote Added: 0021221
2009-10-20 17:28shuehnerfix_in_branchpi =>
2009-10-20 17:28shuehnerProposed Solution updated
2009-10-20 17:28shuehnerSteps to Reproduce Updated
2009-10-22 09:04psarobeNote Added: 0021306
2009-10-22 09:04psarobeStatusnew => scheduled
2009-10-22 09:04psarobefix_in_branch => pi
2009-11-19 14:20iperdomoRelationship addedrelated to 0011416
2010-01-05 14:07iciordiaNote Added: 0023238
2010-01-05 14:07iciordiaStatusscheduled => closed
2010-01-05 14:07iciordiaResolutionopen => no change required

Notes
(0016029)
elopio   
2009-05-04 23:01   
I used module manager to rebuild the application in order to have the newly installed module working. Now the names are properly shown.
(0016043)
psarobe   
2009-05-05 12:18   
This happens randomly, down the severity to major
(0016258)
alostale   
2009-05-11 13:00   
This does not happen with a clean instance, could you specify the steps you did to get this behavior?
(0016276)
elopio   
2009-05-11 19:09   
It was with a clean instance. But I can't reproduce it.
As Pablo said, this happens randomly. I've seen the ** in other windows, but I haven't found a step-by-step or something in common.
(0016285)
plujan   
2009-05-12 09:56   
Lowering priority since it could not be reproduced. MP1 label should be removed also.
(0016414)
alostale   
2009-05-18 10:58   
I'm not able to reproduce it.

Is it possible you followed this steps?:
-You had an up and running instance
-You created database, but you didn't recompile the instance
-Then you see the **

If this is true, the problem is that when creating database identifiers for records are not created. They are created when building the application, you should run "ant smartbuild" in order to do that.

Please confirm it, because in this case it wouldn't be a bug.
(0016472)
elopio   
2009-05-19 17:58   
Hello. I'm sure I didn't create the database. However somebody else might have. I'll try to reproduce it following your steps.
(0016748)
psarobe   
2009-05-29 09:35   
Reminder sent to: alostale

Any update on this?
(0016749)
alostale   
2009-05-29 09:40   
I'm not able to reproduce it, elopio should confirm whether he did create database.
(0016829)
elopio   
2009-06-01 22:32   
Sorry, I forgot to add the note.
I followed Asier's steps and I got the **.

I can't know if somebody else did the create.database before my execution on 2009-05-04. However I haven't seen them again, so at this momment that's the only possible cause.
(0018307)
psarobe   
2009-07-16 12:14   
Closed by engineering since they cannot reproduce following other steps than Asier's ones.
(0021221)
shuehner   
2009-10-20 17:26   
Steps to reproduce:

install working pi context
Then use 'ant create.database -Dapply.on.create=true' to recreate the db
Do not recompile but just restart tomcat
Go to mmc see the issue hapennening
(0021306)
psarobe   
2009-10-22 09:04   
Thanks Stefan
(0023238)
iciordia   
2010-01-05 14:07   
Elopio, Stefan, Psarobe,

this bug is not a bug anymore. First, now the system checks for consistency (so db and source code matches). Second, it makes no sense to report developer actions to lead the system to inconsistency, since it is impossible to guarantee consistency in a developer environment (at the end, a developer can modify code to make the system inconsistent). The steps to reproduce this issue are not allowed for a users, and a developer should know what he is doing.

Clean-up done by iciordia.

Ismael