Fabien Viale
Fabien Viale
The attached thread dump show how renewSession calls are blocked whenever a database problem occurs. Sessions and session renewal should be independant from this kind of operation. [SchedulerThreadDump.txt](https://github.com/ow2-proactive/scheduling/files/2941030/SchedulerThreadDump.txt)
The issue can be reproduced using the scheduler portal, task centric view, and filtering by Tag The following exception appears in the log: ``` [2019-03-07 12:24:18,804 de45983347 WARN o.o.p.d.TransactionHelper] Database...
This serious issue freezes the scheduler, where all database operation seems to be dangling forever. Attached is a resulting thread dump, and some scheduler logs.
When a user runs a ProActive task defined using the cmd script engine, the user can normally watch the streaming output in the scheduler portal. When the same task is...
The following error occurs in the serialization when calling the getJobState method: To me, it does not look like a proactive-programming issue, as the jobState object should not be modified...
Steps to reproduce: Execute the following workflow ```xml ``` After all 3 attempts are executed, the task will be in In-Error state. When trying to retrieve the output of this...
When the scheduler is configured with ldap and password contains some special characters, login fails. Example character: ²
The unexpected following outputs appear systematically in tasks logs, on a clean scheduler 7.33 installation (Windows): [email protected];18:51:48] log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies). [[email protected];18:51:48] log4j:WARN Please initialize...
The following errors are printed over and over on some windows machine. ``` 2018-01-03 14:26:01,985 - org.hyperic.sigar.SigarException: Array index 20 out of bounds 16 2018-01-03 14:26:01,985 - at org.hyperic.sigar.SigarInvoker.invoke(SigarInvoker.java:267) 2018-01-03...
Errors occur in netty websocket protocol, this implies systematic web socket disconnections between client and server. The problem can be shown in the following reconnection stack trace: ``` at org.ow2.proactive.scheduler.smartproxy.common.AbstractSmartProxy.syncAwaitedJobs(AbstractSmartProxy.java:411)...