Lambda POJO job fails with "No such method invokeLambda"

Products

• Workload Automation Agent

Issue/Introduction

When attempting to run a Lambda POJO job type, the job fails immediately upon starting. The `autorep -d` command shows a "FAILURE" status with the specific error message `<No such method invokeLambda>`.

No logs are generated in the job's spool directory, and the job status transitions to "JOBFAILURE" without successful execution.

Cause

The error usually happens because of Invalid Job Definition syntax

Resolution

The error <No such method invokeLambda> indicates that the Workload Automation Agent Lambda plugin is unable to properly instantiate or execute the required method due to an incomplete Job Information Language (JIL) definition.

To resolve this issue, ensure your job definition includes all mandatory `j2ee_parameter` attributes. The Lambda plugin requires specific parameters for authentication, environment configuration, and invocation type. Refer to the AWS Lambda link

Review your JIL and ensure it contains the necessary parameters as shown in the example below. Replace all placeholder values with your specific environment credentials and settings:

insert_job: [JOB_NAME]
job_type: POJO
machine: [AGENT_MACHINE]
class_name: com.broadcom.pojo.lambda.Lambda
method_name: invokeLambda
j2ee_parameter: lambda.Endpoint=[AWS_ENDPOINT]
j2ee_parameter: lambda.Region=[REGION]
j2ee_parameter: lambda.LambdaFunctionName=[FUNCTION_NAME]
j2ee_parameter: lambda.InvocationType=RequestResponse
j2ee_parameter: lambda.LogType=None
j2ee_parameter: lambda.LogLevel=8
j2ee_parameter: lambda.Payload="[PAYLOAD_JSON]"
j2ee_parameter: lambda.AccessKey=[YOUR_ACCESS_KEY]
j2ee_parameter: lambda.AccessKeySecret=[YOUR_SECRET_KEY]
j2ee_parameter: lambda.ClientContext=[CONTEXT_STRING]
j2ee_parameter: lambda.Qualifier=[QUALIFIER_VALUE]

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.