Apigee JavaCallout policy throwing an error "access denied ("java.io.FilePermission" "/tmp/mono-aggregator.log.10" "read")"

When you using java callout policy, in one instance, the following error is thrown from the policy.

Apigee JavaCallout policy throwing an error "access denied ("java.io.FilePermission" "/tmp/mono-aggregator.log.10" "read")" 
Solved Solved
2 1 256
1 ACCEPTED SOLUTION

While using java callout policy, the policy will not have all unlimited access especially when running in the Edge Cloud environment for obvious reasons.

For more information about what permissions are available and restricted visit this link.

If java callout policy uses any third-party libraries which manipulate message processor file system by creating new files (or) reading files etc then the policy will fail with java.io.FilePermission exception.

In one instance, the javacallout policy was using a third-party library apigateway-client-1.0.0-jar-with-dependencies.jar which was trying to read the file /tmp/mono-aggregator.log. This operation was failing and thus failing the policy as well.

These operations are not allowed on the Edge cloud.

View solution in original post

1 REPLY 1

While using java callout policy, the policy will not have all unlimited access especially when running in the Edge Cloud environment for obvious reasons.

For more information about what permissions are available and restricted visit this link.

If java callout policy uses any third-party libraries which manipulate message processor file system by creating new files (or) reading files etc then the policy will fail with java.io.FilePermission exception.

In one instance, the javacallout policy was using a third-party library apigateway-client-1.0.0-jar-with-dependencies.jar which was trying to read the file /tmp/mono-aggregator.log. This operation was failing and thus failing the policy as well.

These operations are not allowed on the Edge cloud.