java.lang.RuntimeException: java.io.IOException: Unable to serialize com.xti.jenkins.plugin.awslambda.callable.InvokeCallable@3357275a

GitHub | bruceharrison1984 | 11 months ago
tip
Do you find the tips below useful? Click on the to mark them and say thanks to Rafael Fischer Viola . Or join the community to write better ones.
  1. 0

    AWS Response

    GitHub | 11 months ago | bruceharrison1984
    java.lang.RuntimeException: java.io.IOException: Unable to serialize com.xti.jenkins.plugin.awslambda.callable.InvokeCallable@3357275a
  2. 0

    Java Heap Space error when deploying lambda function

    GitHub | 7 months ago | aaron-kumar
    com.amazonaws.AmazonClientException: Unable to marshall request to JSON: Java heap space
  3. 0
    samebug tip
    This bug happens on jenkins 2.1 with gitLab plugin 1.2.2, try updating plugin to 1.2.3 or further.
    via GitHub by vills
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    When using "use instance credentials" I get the following exception: =========================== Starting lambda deployment procedure Copying zip file File Name: awslambda-942813613263363530.zip Absolute Path: /tmp/awslambda-942813613263363530.zip File Size: 10388 Lambda function existence check: {FunctionName: alex_test,} Lambda function does not exist Lambda create function request: {FunctionName: alex_test,Runtime: python2.7,Role: arn:aws:iam::763429161784:role/lambda_hipchat_pr_digest,Handler: lambda_handler,Code: {ZipFile: java.nio.HeapByteBuffer[pos=0 lim=10388 cap=10388],},Description: Hipchat PR Digest,Timeout: 60,MemorySize: 256,Publish: true} com.amazonaws.AmazonServiceException: Cross-account pass role is not allowed. (Service: AWSLambda; Status Code: 403; Error Code: null; Request ID: bb814e04-bb96-11e5-88fa-b56203d5b166) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1239) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:823) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:506) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:318) at com.amazonaws.services.lambda.AWSLambdaClient.invoke(AWSLambdaClient.java:1925) at com.amazonaws.services.lambda.AWSLambdaClient.createFunction(AWSLambdaClient.java:686) at com.xti.jenkins.plugin.awslambda.service.LambdaDeployService.createLambdaFunction(LambdaDeployService.java:162) at com.xti.jenkins.plugin.awslambda.service.LambdaDeployService.deployLambda(LambdaDeployService.java:82) at com.xti.jenkins.plugin.awslambda.upload.LambdaUploader.upload(LambdaUploader.java:51) at com.xti.jenkins.plugin.awslambda.upload.LambdaUploadBuildStep.perform(LambdaUploadBuildStep.java:81) at com.xti.jenkins.plugin.awslambda.upload.LambdaUploadBuildStep.perform(LambdaUploadBuildStep.java:66) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Build step 'AWS Lambda deployment' changed build result to FAILURE Finished: FAILURE =========================== The jenkins node that is running that this job has all the credentials it needs to talk to lambda. For instance, I can create a function via the AWS CLI: # aws lambda create-function --function-name alex-foo --runtime python2.7 --role arn:aws:iam::763429161784:role/lambda_hipchat_pr_digest --handler lambda_handler --region us-west-2 --zip-file fileb://foo.zip { "FunctionName": "alex-foo", "CodeSize": 170, "MemorySize": 128, "FunctionArn": "arn:aws:lambda:us-west-2:763429161784:function:alex-foo", "Handler": "lambda_handler", "Role": "arn:aws:iam::763429161784:role/lambda_hipchat_pr_digest", "Timeout": 3, "LastModified": "2016-01-15T14:44:20.353+0000", "Runtime": "python2.7", "Description": "" } The IAM policy on the instance has full lambda and iam:PassRole (This role also has a trust relationship with another account, which may play a role in this error): { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1452706481000", "Effect": "Allow", "Action": [ "lambda:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "iam:PassRole" ], "Resource": [ "*" ] } ] }

    Jenkins JIRA | 1 year ago | Alex Gray
    com.amazonaws.AmazonServiceException: Cross-account pass role is not allowed. (Service: AWSLambda; Status Code: 403; Error Code: null; Request ID: bb814e04-bb96-11e5-88fa-b56203d5b166)
  6. 0

    When using "use instance credentials" I get the following exception: =========================== Starting lambda deployment procedure Copying zip file File Name: awslambda-942813613263363530.zip Absolute Path: /tmp/awslambda-942813613263363530.zip File Size: 10388 Lambda function existence check: {FunctionName: alex_test,} Lambda function does not exist Lambda create function request: {FunctionName: alex_test,Runtime: python2.7,Role: arn:aws:iam::763429161784:role/lambda_hipchat_pr_digest,Handler: lambda_handler,Code: {ZipFile: java.nio.HeapByteBuffer[pos=0 lim=10388 cap=10388],},Description: Hipchat PR Digest,Timeout: 60,MemorySize: 256,Publish: true} com.amazonaws.AmazonServiceException: Cross-account pass role is not allowed. (Service: AWSLambda; Status Code: 403; Error Code: null; Request ID: bb814e04-bb96-11e5-88fa-b56203d5b166) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1239) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:823) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:506) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:318) at com.amazonaws.services.lambda.AWSLambdaClient.invoke(AWSLambdaClient.java:1925) at com.amazonaws.services.lambda.AWSLambdaClient.createFunction(AWSLambdaClient.java:686) at com.xti.jenkins.plugin.awslambda.service.LambdaDeployService.createLambdaFunction(LambdaDeployService.java:162) at com.xti.jenkins.plugin.awslambda.service.LambdaDeployService.deployLambda(LambdaDeployService.java:82) at com.xti.jenkins.plugin.awslambda.upload.LambdaUploader.upload(LambdaUploader.java:51) at com.xti.jenkins.plugin.awslambda.upload.LambdaUploadBuildStep.perform(LambdaUploadBuildStep.java:81) at com.xti.jenkins.plugin.awslambda.upload.LambdaUploadBuildStep.perform(LambdaUploadBuildStep.java:66) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Build step 'AWS Lambda deployment' changed build result to FAILURE Finished: FAILURE =========================== The jenkins node that is running that this job has all the credentials it needs to talk to lambda. For instance, I can create a function via the AWS CLI: # aws lambda create-function --function-name alex-foo --runtime python2.7 --role arn:aws:iam::763429161784:role/lambda_hipchat_pr_digest --handler lambda_handler --region us-west-2 --zip-file fileb://foo.zip { "FunctionName": "alex-foo", "CodeSize": 170, "MemorySize": 128, "FunctionArn": "arn:aws:lambda:us-west-2:763429161784:function:alex-foo", "Handler": "lambda_handler", "Role": "arn:aws:iam::763429161784:role/lambda_hipchat_pr_digest", "Timeout": 3, "LastModified": "2016-01-15T14:44:20.353+0000", "Runtime": "python2.7", "Description": "" } The IAM policy on the instance has full lambda and iam:PassRole (This role also has a trust relationship with another account, which may play a role in this error): { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1452706481000", "Effect": "Allow", "Action": [ "lambda:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "iam:PassRole" ], "Resource": [ "*" ] } ] }

    Jenkins JIRA | 1 year ago | Alex Gray
    com.amazonaws.AmazonServiceException: Cross-account pass role is not allowed. (Service: AWSLambda; Status Code: 403; Error Code: null; Request ID: bb814e04-bb96-11e5-88fa-b56203d5b166)

  1. batwalrus76 14 times, last 3 weeks ago
  2. treefolk 12 times, last 1 month ago
  3. Hronom 1 times, last 1 month ago
  4. kjhdofjosvs 1 times, last 3 months ago
  5. filpgame 4 times, last 3 months ago
13 more registered users
50 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.io.NotSerializableException

    com.xti.jenkins.plugin.awslambda.invoke.JsonParameter

    at java.io.ObjectOutputStream.writeObject0()
  2. Java RT
    ObjectOutputStream.writeObject
    1. java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1183)
    2. java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347)
    3. java.util.ArrayList.writeObject(ArrayList.java:742)
    4. sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source)
    5. sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    6. java.lang.reflect.Method.invoke(Method.java:606)
    7. java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:1028)
    8. java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1495)
    9. java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431)
    10. java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
    11. java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547)
    12. java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508)
    13. java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431)
    14. java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
    15. java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547)
    16. java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508)
    17. java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431)
    18. java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
    19. java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347)
    19 frames
  3. Hudson :: Remoting Layer
    Channel.call
    1. hudson.remoting.UserRequest._serialize(UserRequest.java:157)
    2. hudson.remoting.UserRequest.serialize(UserRequest.java:166)
    3. hudson.remoting.UserRequest.<init>(UserRequest.java:62)
    4. hudson.remoting.Channel.call(Channel.java:779)
    4 frames
  4. com.xti.jenkins
    LambdaInvokePublisher.perform
    1. com.xti.jenkins.plugin.awslambda.invoke.LambdaInvokePublisher.perform(LambdaInvokePublisher.java:99)
    2. com.xti.jenkins.plugin.awslambda.invoke.LambdaInvokePublisher.perform(LambdaInvokePublisher.java:75)
    2 frames
  5. Hudson
    Executor.run
    1. hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
    2. hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
    3. hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
    4. hudson.model.Build$BuildExecution.post2(Build.java:185)
    5. hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
    6. hudson.model.Run.execute(Run.java:1763)
    7. hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    8. hudson.model.ResourceController.execute(ResourceController.java:98)
    9. hudson.model.Executor.run(Executor.java:410)
    9 frames