Fabien Viale
Fabien Viale
Are you trying to connect the node to a scheduler with a pamr url ? (like on try/trydev, etc). In which case it's normal
Another possibility is that multi-protocol pnp/pamr is enabled on the server. In that case, even if the node tries to connect with pnp, the server will respond with both protocols.
:+1: Log4j seems to be frozen and not evolving any more. But won't this change be a bit painful ?
Classpath parameter needs to be escaped, it looks like this is the issue here, otherwise wild cards will be expanded by the Cygwin shell
I reopened this issue as following #2523, the ParallelEnvironment with nb-nodes=1 does not behave as expected for SingleHostExclusive, MultipleHostExclusive and DifferentHostExclusive topologies. For example, where the whole machine should be...
The only workaround I see is to add a fork environment script which contains the following code: forkEnvironment.addJVMArgument("-Dlog4j.configuration=file:" + System.getProperty("proactive.home") + "/config/log/node.properties") The problem is that the log4j configuration defined...
The problem persists even if python is installed on the machine.
fixed by work on server-side pagination
Hello @febael, I analysed the heap dump you provided using Eclipse Memory Analyser and it does not show anything special. Like you said, the scheduler seems to be quite empty....
Thank you for your detailed explanation, and I indeed observes what you describe in JVisualVM. Apparently, one frame decoded by PNPServerFrameDecoder (part of the low-level proactive network protocol) seems excessively...