failed to execute javaapicallout policy in apigee 4.51 edge private cloud

[Sirisha_n]

Getting below error when using javaapicallout policy in apigee 4.51. however it is working okay on other 4.51 environments. Was wondeering if any permissions to the files causing this issue..

Apigee-Main-27 ERROR MESSAGING.FLOW - AbstractAsyncExecutionStrategy$AsyncExecutionTask.logException() : Exception caught
com.apigee.kernel.exceptions.spi.UncheckedException: Failed to execute JavaCallout. Could not initialize class com.fanniemae.sharedservices.evas.VaultFactory
at com.apigee.steps.javacallout.JavaCalloutStepDefinition$SecurityWrappedExecution.execute(JavaCalloutStepDefinition.java:315)
at com.apigee.steps.javacallout.JavaCalloutStepDefinition$CallOutWrapper.execute(JavaCalloutStepDefinition.java:169)
at com.apigee.messaging.runtime.steps.StepExecution.execute(StepExecution.java:157)
at com.apigee.flow.execution.AbstractAsyncExecutionStrategy$AsyncExecutionTask.call(AbstractAsyncExecutionStrategy.java:83)
at com.apigee.flow.execution.AbstractAsyncExecutionStrategy$AsyncExecutionTask.call(AbstractAsyncExecutionStrategy.java:48)
at com.apigee.threadpool.CallableWrapperForMDCPreservation.call(CallableWrapperForMDCPreservation.java:26)
at com.apigee.threadpool.ThreadPoolManager$QueueAwareCallableTask.call(ThreadPoolManager.java:567)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.fanniemae.sharedservices.evas.VaultFactory
at com.fanniemae.apigee.ApigeeSecretManager.execute(ApigeeSecretManager.java:37)
at com.apigee.steps.javacallout.JavaCalloutStepDefinition$ClassLoadWrappedExecution.execute(JavaCalloutStepDefinition.java:235)
at com.apigee.steps.javacallout.JavaCalloutStepDefinition$SecurityWrappedExecution$1.run(JavaCalloutStepDefinition.java:302)
at com.apigee.steps.javacallout.JavaCalloutStepDefinition$SecurityWrappedExecution$1.run(JavaCalloutStepDefinition.java:300)
at java.security.AccessController.doPrivileged(Native Method)
at com.apigee.steps.javacallout.JavaCalloutStepDefinition$SecurityWrappedExecution.execute(JavaCalloutStepDefinition.java:300)
... 12 common frames omitted

[API-Evangelist]

Looks like dependencies are missing..Further debug following below document for Java callout failures..

https://cloud.google.com/apigee/docs/api-platform/troubleshoot/policies/deployment/java-callout-depl...

[dchiesa1]

Yes, it seems the two 4.51 environments are not the same!  Check your dependencies.

[Sirisha_n]

yes,  the property conf_security-policy_enable.security.manager=true is casuing the issue.

it wasn't enabled in the other environment where Javacallout policy isworking okay.

we commented out this property for now on message processor.properties file as a workaround. probably this is an issue with 4.51? 

[API-Evangelist]

Correct. Thanks for confirmation.

Good Read - https://docs.apigee.com/api-platform/reference/java-permission-reference