node.js - AWS Lambda function never calls the callback -


i've created node lambda function simple call aurora database. when test function in console, query returns, can see results in log, callback never seems called , lambda function times out. can't figure out problem is. here can point me problem.

var mysql = require("mysql");  module.exports.handler = function(event, context, cb) {   console.log('start\n');   var con = mysql.createconnection({     ...   });   console.log('call data\n');    con.query('select * tags', function(err, rows) {     console.log('data received db:\n');     console.log(rows);      console.log('calling callback');      cb(null, 'success');      console.log('callback called');   });   console.log('data called\n'); };

the resulting cloudwatch log follows...

2016-07-25t14:20:05.343z    daf5cd6b-5272-11e6-9036-e73ad17006df    start   2016-07-25t14:20:05.398z    daf5cd6b-5272-11e6-9036-e73ad17006df    call data   2016-07-25t14:20:05.405z    daf5cd6b-5272-11e6-9036-e73ad17006df    data called   2016-07-25t14:20:05.440z    daf5cd6b-5272-11e6-9036-e73ad17006df    data received db:   2016-07-25t14:20:05.440z    daf5cd6b-5272-11e6-9036-e73ad17006df    [      rowdatapacket {         id: 1,         externalid:         'a87ead34de7e',         orgid: 1,         name: 'lacinia sapien',         createddate: 1448598369,         modifieddate: 0     },     ...,     rowdatapacket {         id: 50,         externalid: '9ebaaab372e3',         orgid: 1,         name: 'et commodo',         createddate: 1451551837,         modifieddate: 0     } ] 2016-07-25t14:20:05.483z    daf5cd6b-5272-11e6-9036-e73ad17006df    calling callback  2016-07-25t14:20:05.483z    daf5cd6b-5272-11e6-9036-e73ad17006df    callback called  end requestid: daf5cd6b-5272-11e6-9036-e73ad17006df  report requestid: daf5cd6b-5272-11e6-9036-e73ad17006df  duration: 300000.12 ms  billed duration: 300000 ms memory size: 1024 mb max memory used: 52 mb    2016-07-25t14:25:05.341z daf5cd6b-5272-11e6-9036-e73ad17006df task timed out after 300.00 seconds

thanks question...

lambda timing out after calling callback

i found problem. node mysql module keeps connection open until server closes unless explicitly closed handler logic.

so node event loop never empties , never returns callback. in above code, did ...

con.end();

before calling callback , worked.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more