You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, accessing files can also throw AccessControlException if a Java Security Policy is in place. If those aren't caught at this level, the MessageBehaviour crashes and is removed from the ShellAgent. So the Agent can't respond to any more messages.
1632115867860|WARNING|org.arl.fjage.shell.ShellAgent/yoda@33:executeBehavior|Exception in agent: websh
For example, doing a GetFileReq on a file file-without-permissions.txt to which JVM doesn't have permissions based on the security policy will return this error.
notthetup
changed the title
ShellAgent should catch java.security.AccessControlException as well as IOException when handling file access requests
ShellAgent should catch java.security.AccessControlException as well when handling file access requests
Sep 20, 2021
Currently, the ShellAgent specifically catches IOExceptions when handling file access requests (GetFileReq, PutFileReq).
However, accessing files can also throw
AccessControlException
if a Java Security Policy is in place. If those aren't caught at this level, the MessageBehaviour crashes and is removed from the ShellAgent. So the Agent can't respond to any more messages.For example, doing a
GetFileReq
on a filefile-without-permissions.txt
to which JVM doesn't have permissions based on the security policy will return this error.After this error, no other
GetFileReq
/PutFileReq
get any responses.The text was updated successfully, but these errors were encountered: