Forum

error on recalculat...
 
Notifications
Retirer tout

error on recalculate project

9 Posts
2 Utilisateurs
0 Reactions
9,516 Vu
Evgueni Kolossov
(@ekolossov)
Posts: 566
Contributor
Début du sujet
 
[#1300]

Please see attachment


 
Posté : 31 Juil PM 18:077
(@babynus)
Posts: 14952
Membre Admin
 

It seems clear : Out of Memory.

Maybe you tried to plan too many activities in one step.
=> try planning project by project or allocate more memory to PHP server.


 
Posté : 31 Juil PM 19:077
Evgueni Kolossov
(@ekolossov)
Posts: 566
Contributor
Début du sujet
 

more memory allocation not help at all.
some more errors from log:
2013-08-01 11:17:10 ** ERROR ** Exception-[42000] SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1
2013-08-01 11:17:10 ** ERROR ** For query : select * from dependency where successorId in (0,)
2013-08-01 11:17:10 ** ERROR ** Strack trace :
2013-08-01 11:17:10 ** ERROR ** #0 Sql->query called at [/var/www/localhost/htdocs/projectorria/model/persistence/SqlElement.php:1268]
2013-08-01 11:17:10 ** ERROR ** #1 SqlElement->getSqlElementsFromCriteria called at [/var/www/localhost/htdocs/projectorria/model/PlanningElement.php:854]
2013-08-01 11:17:10 ** ERROR ** #2 PlanningElement->initializeFullList called at [/var/www/localhost/htdocs/projectorria/model/PlannedWork.php:135]
2013-08-01 11:17:10 ** ERROR ** #3 PlannedWork->plan called at [/var/www/localhost/htdocs/projectorria/tool/plan.php:18]
2013-08-01 11:17:16 ** ERROR ** Exception-[42000] SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1
2013-08-01 11:17:16 ** ERROR ** For query : select * from dependency where successorId in (0,)
2013-08-01 11:17:16 ** ERROR ** Strack trace :
2013-08-01 11:17:16 ** ERROR ** #0 Sql->query called at [/var/www/localhost/htdocs/projectorria/model/persistence/SqlElement.php:1268]
2013-08-01 11:17:16 ** ERROR ** #1 SqlElement->getSqlElementsFromCriteria called at [/var/www/localhost/htdocs/projectorria/model/PlanningElement.php:854]
2013-08-01 11:17:16 ** ERROR ** #2 PlanningElement->initializeFullList called at [/var/www/localhost/htdocs/projectorria/model/PlannedWork.php:135]
2013-08-01 11:17:16 ** ERROR ** #3 PlannedWork->plan called at [/var/www/localhost/htdocs/projectorria/tool/plan.php:18]

and additional screenshot


 
Posté : 1 Août PM 15:088
(@babynus)
Posts: 14952
Membre Admin
 

Hi,

Strange issue.
It seems you are planning no activity...

1) can you check table planningelement : check that idProject is never 0, and that refType and refId are always set (not null)

2) can you try this patch :
in /model/PlanningElement.php, replace line 851 with :

    $crit='successorId in (0' . (($idList and count($idList)>0)?',' . implode(',',$idList):'') . ')';

 
Posté : 1 Août PM 16:088
Evgueni Kolossov
(@ekolossov)
Posts: 566
Contributor
Début du sujet
 

Looking like we found an issue and fixed it. we have moved group of tasks from one project to another and this have caused the problem


 
Posté : 1 Août PM 16:088
(@babynus)
Posts: 14952
Membre Admin
 

Sorry, I don't understand your message.

Did the action to move the tasks "create" or "fix" the issue ?


 
Posté : 1 Août PM 16:088
Evgueni Kolossov
(@ekolossov)
Posts: 566
Contributor
Début du sujet
 

It created an issue. When moved back it fixed an issue. After these tasks been moved one by one everything is ok. Looking like it is possible to move group of tasks under one common task (one level) to another project but if you have more then one level - it will create a problem we have seen...


 
Posté : 1 Août PM 17:088
(@babynus)
Posts: 14952
Membre Admin
 

thnaks for the description.
I recorded Ticket #1154, and will try and reproduce thanks to your description of tests case.
thanks for reporting.


 
Posté : 1 Août PM 18:088
(@babynus)
Posts: 14952
Membre Admin
 

After first analysis, it seems to be some dependency loop issue.
When moving group of activities, it may happen that control of dependency loop does not correctly trigger error on sub-activity, to forbid the move.
So you may get a dependency loop that will generate the error you're facing when calculating planning.
I'll investigate to :
- avoid dependency loop
- detect these loop on planning calculation to avoid error message


 
Posté : 2 Août AM 01:088
Share:
Retour en haut