joerg1985

@diemol At this time the exception is raised the session is allready timed out. So i would expect a NoSuchSessionException and not something that indicates an grid bug.

It is raised here: https://github.com/SeleniumHQ/selenium/blob/2b5999625744adccf2a0ad30cdd18d503044603b/java/src/org/openqa/selenium/grid/web/RoutableHttpClientFactory.java#L60-L68 Here the session map still returns the session, but the following ownership check fails: https://github.com/SeleniumHQ/selenium/blob/2b5999625744adccf2a0ad30cdd18d503044603b/java/src/org/openqa/selenium/grid/node/Node.java#L149-L151

@johnny are you using the selenium server configuration to enable basic auth or some kind of reverse proxy?

@theswordsmahin Could you share the server log output? If it fails while writing JSON this might be an easy / small change. I think most of the processing takes ~...

@theswordsmahin looks like the ErrorFilter does catch it on the grid and send it to the client without logging. You should get the remote stack when debugging into the response...

I tried synchronizing the selenium manager calls without success. I also tried to repace the File.canExecute with Files.isExecutable, also no success. So i hat a look at the javadoc and...

@titusfortner i removed the try catch in the commit https://github.com/joerg1985/selenium/commit/829fa6347b579f219795d7abca4cfcdc2d178770 this revealed the `...driver, can not be executed` error message.

Look at [this](https://github.com/joerg1985/selenium/actions/runs/5684783524/job/15408741516#step:14:202) run where, i polled until the file gets executable and it is getting executable after some ms.

I think there is no warrenty that changes in file attributes are instantly visible and this might be implementation specific for all the filesystems out there?

We could try to create the file with the correct permissions and not modify them, as far as i understand the rust code :D https://stackoverflow.com/a/28673836