Hello, It seems that I have bad vibes....
If I create some actions, all is fine (I can add the risk, who is responsible,...) but when I try to set a due date and save the action, I have the "infinite spinner" and if I try to change the screen, I can see a pop-up "request in progress, please wait". The only solution is to close my browser. Of course the action is not updated, I have the same issue with an admin account and no entry in the log file (configured in Debug mode) except this :
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] Exception-[HY000] SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] For query : update action set initialDueDate='2022-09-30' , actualDueDate='2022-09-30' where id=4
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] Strack trace :
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] #0 Sql->query called at [/var/www/projeqtor/model/persistence/SqlElement.php:1849]
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] #1 SqlElement->updateSqlElement called at [/var/www/projeqtor/model/persistence/SqlElement.php:1303]
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] #2 SqlElement->saveSqlElement called at [/var/www/projeqtor/model/persistence/SqlElement.php:848]
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] #3 SqlElement->save called at [/var/www/projeqtor/model/ActionMain.php:208]
2022-09-09 18:29:43.077 ** ERROR ** [V10.0.5] #4 ActionMain->save called at [/var/www/projeqtor/tool/saveObject.php:122]
Any good idea to identify the problem ?
Thanks.
It is a "Lock wait timeout".
It means the program waited for a lock to be freed, but it was not before a defined time (tmeout)
This means either someoune was doing a very long transaction on the DB when you updated the data
or you have some persistant lock in the db.
Restart the DB will fix the latest case.
DB restarted and the issue is still present.
I try to add on actions an initial date or due date but when I save, the app is blocked. I have the issue if I create an action from scratch with a date or if I update an action and add a date. No extra log...
Otherwise, I can change the status of the action, modify the other fields without worries
Here is a DESC for the action table. Maybe it can help !
MariaDB [projeqtor]> DESC action; +-------------------+------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------------------+------------------+------+-----+---------+----------------+ | id | int(12) unsigned | NO | PRI | NULL | auto_increment | | idProject | int(12) unsigned | YES | MUL | NULL | | | name | varchar(100) | YES | | NULL | | | description | mediumtext | YES | | NULL | | | creationDate | date | YES | | NULL | | | idUser | int(12) unsigned | YES | MUL | NULL | | | idStatus | int(12) unsigned | YES | MUL | NULL | | | idResource | int(12) unsigned | YES | MUL | NULL | | | initialDueDate | date | YES | | NULL | | | actualDueDate | date | YES | | NULL | | | idleDate | date | YES | | NULL | | | result | mediumtext | YES | | NULL | | | comment | varchar(4000) | YES | | NULL | | | idle | int(1) unsigned | YES | | 0 | | | done | int(1) unsigned | YES | | 0 | | | doneDate | date | YES | | NULL | | | idActionType | int(12) unsigned | YES | MUL | NULL | | | idPriority | int(12) unsigned | YES | | NULL | | | handled | int(1) unsigned | YES | | 0 | | | handledDate | date | YES | | NULL | | | reference | varchar(100) | YES | | NULL | | | externalReference | varchar(100) | YES | | NULL | | | idEfficiency | int(12) unsigned | YES | | NULL | | | cancelled | int(1) unsigned | YES | | 0 | | | isPrivate | int(1) unsigned | YES | | 0 | | | idContact | int(12) unsigned | YES | | NULL | | +-------------------+------------------+------+-----+---------+----------------+ 26 rows in set (0.01 sec)
I did some more digging and I think I found the problem !
I have found in the forum the following thread. It talks about indicators. As written in the solution, if I close the indicator all is fine without errors....
I have re-created the indicator and the problem still occurs, but if I change the alert condition from 1 working hour to 1 working day, I do not have issues anymore, I can use the duedate on actions and having an indicator.
Still strange behavior.....
Regards.
Can you show the definition of your indicator ?
Here it is !
Hi,
I think I found the issue.
You define an indicator you "open hours" but possibly your definition for open hours is empty on Global PArameters
Try and define the values, it should fix the issue.
Hi,
the working hours are defined since the beginning.
Here is a screenshot.
When I have filled the forms, I had a doubt with the number of hours per day : 7,5. I was asking me if it was possible.
OK,
I found the issue.
It is due to bas management of munutes.
If you change 13:30 to 14:00, all will work fine.
We'll fix this.
Confirmed, it's working but not aligned with my real working hours. Not a big issue.
Thanks.