Result returned by AWS Lambda python function execution in “”Null“”











up vote
0
down vote

favorite












I have a python script which connects to AWS MQ and collect message. All my connections are perfectly aligned and Execution result is success. But result returned by my function execution is "null".
Updated error logs:-



    {
"errorType": "ConnectFailedException",
"stackTrace": [
" File "/var/task/one_purchasing.py", line 21, in lambda_handlern conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)n",
" File "/var/task/stomp/connect.py", line 164, in connectn Protocol11.connect(self, *args, **kwargs)n",
" File "/var/task/stomp/protocol.py", line 340, in connectn self.transport.wait_for_connection()n",
" File "/var/task/stomp/transport.py", line 327, in wait_for_connectionn raise exception.ConnectFailedException()n"
]
}


Updated Python Lambda function:-



import time
import boto3
import stomp
import json

kinesis_client = boto3.client('kinesis')


class Listener(stomp.ConnectionListener):
def on_error(self, headers, message):
print('received an error "%s"' % message)
kinesis_client.put_record(
StreamName='OnePurchasing',
Data=u'{}rn'.format(message).encode('utf-8'),
PartitionKey='0'
)

def on_message(self, headers, message):
print('received a message "%s"' % message)
def lambda_handler(event, context):
conn = stomp.Connection(host_and_ports=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()
print('CONNECTION Started')
conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)
print('CONNECTION established')
conn.subscribe(destination='/queue/OnePurchasing', id=1, ack='auto')
print('CONNECTION Subscribed')
time.sleep(10)
conn.disconnect()
return


Could anyone tell me how can I debug more to get the message from MQ



MQ URL message screen shot



MQ home page



Messages under queue










share|improve this question
























  • Not sure it's the cause of your problem but according to github.com/jasonrbriggs/stomp.py/issues/33 you should make your port a string rather than int , '61614')]) to make the strange warning disappear. Curious to see if it makes a difference.
    – Eric Darchis
    Nov 22 at 12:09










  • @EricDarchis I tested, it does not make a difference, the strange warning remains.
    – Rob Bricheno
    Nov 22 at 13:20












  • @EricDarchis .. Yes.. it did not make any difference..
    – Tinku
    Nov 22 at 13:30










  • @Tinku regarding your edit to my answer, you probably want to change that in your question too :-)
    – Rob Bricheno
    Nov 23 at 10:26










  • @RobBricheno-- I have posted different question- stackoverflow.com/questions/53445120/…
    – Tinku
    Nov 23 at 10:42















up vote
0
down vote

favorite












I have a python script which connects to AWS MQ and collect message. All my connections are perfectly aligned and Execution result is success. But result returned by my function execution is "null".
Updated error logs:-



    {
"errorType": "ConnectFailedException",
"stackTrace": [
" File "/var/task/one_purchasing.py", line 21, in lambda_handlern conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)n",
" File "/var/task/stomp/connect.py", line 164, in connectn Protocol11.connect(self, *args, **kwargs)n",
" File "/var/task/stomp/protocol.py", line 340, in connectn self.transport.wait_for_connection()n",
" File "/var/task/stomp/transport.py", line 327, in wait_for_connectionn raise exception.ConnectFailedException()n"
]
}


Updated Python Lambda function:-



import time
import boto3
import stomp
import json

kinesis_client = boto3.client('kinesis')


class Listener(stomp.ConnectionListener):
def on_error(self, headers, message):
print('received an error "%s"' % message)
kinesis_client.put_record(
StreamName='OnePurchasing',
Data=u'{}rn'.format(message).encode('utf-8'),
PartitionKey='0'
)

def on_message(self, headers, message):
print('received a message "%s"' % message)
def lambda_handler(event, context):
conn = stomp.Connection(host_and_ports=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()
print('CONNECTION Started')
conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)
print('CONNECTION established')
conn.subscribe(destination='/queue/OnePurchasing', id=1, ack='auto')
print('CONNECTION Subscribed')
time.sleep(10)
conn.disconnect()
return


Could anyone tell me how can I debug more to get the message from MQ



MQ URL message screen shot



MQ home page



Messages under queue










share|improve this question
























  • Not sure it's the cause of your problem but according to github.com/jasonrbriggs/stomp.py/issues/33 you should make your port a string rather than int , '61614')]) to make the strange warning disappear. Curious to see if it makes a difference.
    – Eric Darchis
    Nov 22 at 12:09










  • @EricDarchis I tested, it does not make a difference, the strange warning remains.
    – Rob Bricheno
    Nov 22 at 13:20












  • @EricDarchis .. Yes.. it did not make any difference..
    – Tinku
    Nov 22 at 13:30










  • @Tinku regarding your edit to my answer, you probably want to change that in your question too :-)
    – Rob Bricheno
    Nov 23 at 10:26










  • @RobBricheno-- I have posted different question- stackoverflow.com/questions/53445120/…
    – Tinku
    Nov 23 at 10:42













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a python script which connects to AWS MQ and collect message. All my connections are perfectly aligned and Execution result is success. But result returned by my function execution is "null".
Updated error logs:-



    {
"errorType": "ConnectFailedException",
"stackTrace": [
" File "/var/task/one_purchasing.py", line 21, in lambda_handlern conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)n",
" File "/var/task/stomp/connect.py", line 164, in connectn Protocol11.connect(self, *args, **kwargs)n",
" File "/var/task/stomp/protocol.py", line 340, in connectn self.transport.wait_for_connection()n",
" File "/var/task/stomp/transport.py", line 327, in wait_for_connectionn raise exception.ConnectFailedException()n"
]
}


Updated Python Lambda function:-



import time
import boto3
import stomp
import json

kinesis_client = boto3.client('kinesis')


class Listener(stomp.ConnectionListener):
def on_error(self, headers, message):
print('received an error "%s"' % message)
kinesis_client.put_record(
StreamName='OnePurchasing',
Data=u'{}rn'.format(message).encode('utf-8'),
PartitionKey='0'
)

def on_message(self, headers, message):
print('received a message "%s"' % message)
def lambda_handler(event, context):
conn = stomp.Connection(host_and_ports=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()
print('CONNECTION Started')
conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)
print('CONNECTION established')
conn.subscribe(destination='/queue/OnePurchasing', id=1, ack='auto')
print('CONNECTION Subscribed')
time.sleep(10)
conn.disconnect()
return


Could anyone tell me how can I debug more to get the message from MQ



MQ URL message screen shot



MQ home page



Messages under queue










share|improve this question















I have a python script which connects to AWS MQ and collect message. All my connections are perfectly aligned and Execution result is success. But result returned by my function execution is "null".
Updated error logs:-



    {
"errorType": "ConnectFailedException",
"stackTrace": [
" File "/var/task/one_purchasing.py", line 21, in lambda_handlern conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)n",
" File "/var/task/stomp/connect.py", line 164, in connectn Protocol11.connect(self, *args, **kwargs)n",
" File "/var/task/stomp/protocol.py", line 340, in connectn self.transport.wait_for_connection()n",
" File "/var/task/stomp/transport.py", line 327, in wait_for_connectionn raise exception.ConnectFailedException()n"
]
}


Updated Python Lambda function:-



import time
import boto3
import stomp
import json

kinesis_client = boto3.client('kinesis')


class Listener(stomp.ConnectionListener):
def on_error(self, headers, message):
print('received an error "%s"' % message)
kinesis_client.put_record(
StreamName='OnePurchasing',
Data=u'{}rn'.format(message).encode('utf-8'),
PartitionKey='0'
)

def on_message(self, headers, message):
print('received a message "%s"' % message)
def lambda_handler(event, context):
conn = stomp.Connection(host_and_ports=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-fa99d7c5-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()
print('CONNECTION Started')
conn.connect(login='test_mq', passcode='test_secure_mq',wait=True)
print('CONNECTION established')
conn.subscribe(destination='/queue/OnePurchasing', id=1, ack='auto')
print('CONNECTION Subscribed')
time.sleep(10)
conn.disconnect()
return


Could anyone tell me how can I debug more to get the message from MQ



MQ URL message screen shot



MQ home page



Messages under queue







python python-3.x python-2.7 amazon-web-services amazon-mq






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 at 14:07

























asked Nov 22 at 11:47









Tinku

337




337












  • Not sure it's the cause of your problem but according to github.com/jasonrbriggs/stomp.py/issues/33 you should make your port a string rather than int , '61614')]) to make the strange warning disappear. Curious to see if it makes a difference.
    – Eric Darchis
    Nov 22 at 12:09










  • @EricDarchis I tested, it does not make a difference, the strange warning remains.
    – Rob Bricheno
    Nov 22 at 13:20












  • @EricDarchis .. Yes.. it did not make any difference..
    – Tinku
    Nov 22 at 13:30










  • @Tinku regarding your edit to my answer, you probably want to change that in your question too :-)
    – Rob Bricheno
    Nov 23 at 10:26










  • @RobBricheno-- I have posted different question- stackoverflow.com/questions/53445120/…
    – Tinku
    Nov 23 at 10:42


















  • Not sure it's the cause of your problem but according to github.com/jasonrbriggs/stomp.py/issues/33 you should make your port a string rather than int , '61614')]) to make the strange warning disappear. Curious to see if it makes a difference.
    – Eric Darchis
    Nov 22 at 12:09










  • @EricDarchis I tested, it does not make a difference, the strange warning remains.
    – Rob Bricheno
    Nov 22 at 13:20












  • @EricDarchis .. Yes.. it did not make any difference..
    – Tinku
    Nov 22 at 13:30










  • @Tinku regarding your edit to my answer, you probably want to change that in your question too :-)
    – Rob Bricheno
    Nov 23 at 10:26










  • @RobBricheno-- I have posted different question- stackoverflow.com/questions/53445120/…
    – Tinku
    Nov 23 at 10:42
















Not sure it's the cause of your problem but according to github.com/jasonrbriggs/stomp.py/issues/33 you should make your port a string rather than int , '61614')]) to make the strange warning disappear. Curious to see if it makes a difference.
– Eric Darchis
Nov 22 at 12:09




Not sure it's the cause of your problem but according to github.com/jasonrbriggs/stomp.py/issues/33 you should make your port a string rather than int , '61614')]) to make the strange warning disappear. Curious to see if it makes a difference.
– Eric Darchis
Nov 22 at 12:09












@EricDarchis I tested, it does not make a difference, the strange warning remains.
– Rob Bricheno
Nov 22 at 13:20






@EricDarchis I tested, it does not make a difference, the strange warning remains.
– Rob Bricheno
Nov 22 at 13:20














@EricDarchis .. Yes.. it did not make any difference..
– Tinku
Nov 22 at 13:30




@EricDarchis .. Yes.. it did not make any difference..
– Tinku
Nov 22 at 13:30












@Tinku regarding your edit to my answer, you probably want to change that in your question too :-)
– Rob Bricheno
Nov 23 at 10:26




@Tinku regarding your edit to my answer, you probably want to change that in your question too :-)
– Rob Bricheno
Nov 23 at 10:26












@RobBricheno-- I have posted different question- stackoverflow.com/questions/53445120/…
– Tinku
Nov 23 at 10:42




@RobBricheno-- I have posted different question- stackoverflow.com/questions/53445120/…
– Tinku
Nov 23 at 10:42












1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










The reason that response is null is because you don't ever return a value, you just return. It's the same response as if you run this:



def lambda_handler(event, context):
return


You probably want to return something, like the example built in to lambda:



import json

def lambda_handler(event, context):
# TODO implement
return {
'statusCode': 200,
'body': json.dumps('Hello from Lambda!')
}


Regarding the rest of your problem, it looks like you are never receivng a message at all. You see from the web console of your MQ instance if there are messages on the queue, if a message has been consumed, and so on.



All the examples I have seen involve using the wait=True option e.g. conn.connect(wait=True) so you should try adding that to your conn.connect unless there's a good reason you aren't using it.



Edit: I tested this, I don't think you are ever establishing a connection. If you add wait=True then you will probably see that the connection fails with a ConnectFailedException as mine did. This is probably the first thing to debug.



Edit 2: I solved it, you need to use SSL for your connection to the AWS MQ instance as follows:



conn = stomp.Connection(host_and_ports=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()





share|improve this answer























  • I have updated response and code as well. MQ does has messages in it. Updated with proper URL of MQ with credentials. Please suggest
    – Tinku
    Nov 22 at 13:34












  • @Tinku did you try wait=True?
    – Rob Bricheno
    Nov 22 at 13:40










  • Yeah.. Even I received "errorType": "ConnectFailedException", error
    – Tinku
    Nov 22 at 13:42










  • How can I proceed from here. As I have given all the right values which I have
    – Tinku
    Nov 22 at 13:46










  • @Tinku check latest edit, I solved it, you need to use SSL :-)
    – Rob Bricheno
    Nov 22 at 14:00











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430332%2fresult-returned-by-aws-lambda-python-function-execution-in-null%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










The reason that response is null is because you don't ever return a value, you just return. It's the same response as if you run this:



def lambda_handler(event, context):
return


You probably want to return something, like the example built in to lambda:



import json

def lambda_handler(event, context):
# TODO implement
return {
'statusCode': 200,
'body': json.dumps('Hello from Lambda!')
}


Regarding the rest of your problem, it looks like you are never receivng a message at all. You see from the web console of your MQ instance if there are messages on the queue, if a message has been consumed, and so on.



All the examples I have seen involve using the wait=True option e.g. conn.connect(wait=True) so you should try adding that to your conn.connect unless there's a good reason you aren't using it.



Edit: I tested this, I don't think you are ever establishing a connection. If you add wait=True then you will probably see that the connection fails with a ConnectFailedException as mine did. This is probably the first thing to debug.



Edit 2: I solved it, you need to use SSL for your connection to the AWS MQ instance as follows:



conn = stomp.Connection(host_and_ports=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()





share|improve this answer























  • I have updated response and code as well. MQ does has messages in it. Updated with proper URL of MQ with credentials. Please suggest
    – Tinku
    Nov 22 at 13:34












  • @Tinku did you try wait=True?
    – Rob Bricheno
    Nov 22 at 13:40










  • Yeah.. Even I received "errorType": "ConnectFailedException", error
    – Tinku
    Nov 22 at 13:42










  • How can I proceed from here. As I have given all the right values which I have
    – Tinku
    Nov 22 at 13:46










  • @Tinku check latest edit, I solved it, you need to use SSL :-)
    – Rob Bricheno
    Nov 22 at 14:00















up vote
1
down vote



accepted










The reason that response is null is because you don't ever return a value, you just return. It's the same response as if you run this:



def lambda_handler(event, context):
return


You probably want to return something, like the example built in to lambda:



import json

def lambda_handler(event, context):
# TODO implement
return {
'statusCode': 200,
'body': json.dumps('Hello from Lambda!')
}


Regarding the rest of your problem, it looks like you are never receivng a message at all. You see from the web console of your MQ instance if there are messages on the queue, if a message has been consumed, and so on.



All the examples I have seen involve using the wait=True option e.g. conn.connect(wait=True) so you should try adding that to your conn.connect unless there's a good reason you aren't using it.



Edit: I tested this, I don't think you are ever establishing a connection. If you add wait=True then you will probably see that the connection fails with a ConnectFailedException as mine did. This is probably the first thing to debug.



Edit 2: I solved it, you need to use SSL for your connection to the AWS MQ instance as follows:



conn = stomp.Connection(host_and_ports=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()





share|improve this answer























  • I have updated response and code as well. MQ does has messages in it. Updated with proper URL of MQ with credentials. Please suggest
    – Tinku
    Nov 22 at 13:34












  • @Tinku did you try wait=True?
    – Rob Bricheno
    Nov 22 at 13:40










  • Yeah.. Even I received "errorType": "ConnectFailedException", error
    – Tinku
    Nov 22 at 13:42










  • How can I proceed from here. As I have given all the right values which I have
    – Tinku
    Nov 22 at 13:46










  • @Tinku check latest edit, I solved it, you need to use SSL :-)
    – Rob Bricheno
    Nov 22 at 14:00













up vote
1
down vote



accepted







up vote
1
down vote



accepted






The reason that response is null is because you don't ever return a value, you just return. It's the same response as if you run this:



def lambda_handler(event, context):
return


You probably want to return something, like the example built in to lambda:



import json

def lambda_handler(event, context):
# TODO implement
return {
'statusCode': 200,
'body': json.dumps('Hello from Lambda!')
}


Regarding the rest of your problem, it looks like you are never receivng a message at all. You see from the web console of your MQ instance if there are messages on the queue, if a message has been consumed, and so on.



All the examples I have seen involve using the wait=True option e.g. conn.connect(wait=True) so you should try adding that to your conn.connect unless there's a good reason you aren't using it.



Edit: I tested this, I don't think you are ever establishing a connection. If you add wait=True then you will probably see that the connection fails with a ConnectFailedException as mine did. This is probably the first thing to debug.



Edit 2: I solved it, you need to use SSL for your connection to the AWS MQ instance as follows:



conn = stomp.Connection(host_and_ports=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()





share|improve this answer














The reason that response is null is because you don't ever return a value, you just return. It's the same response as if you run this:



def lambda_handler(event, context):
return


You probably want to return something, like the example built in to lambda:



import json

def lambda_handler(event, context):
# TODO implement
return {
'statusCode': 200,
'body': json.dumps('Hello from Lambda!')
}


Regarding the rest of your problem, it looks like you are never receivng a message at all. You see from the web console of your MQ instance if there are messages on the queue, if a message has been consumed, and so on.



All the examples I have seen involve using the wait=True option e.g. conn.connect(wait=True) so you should try adding that to your conn.connect unless there's a good reason you aren't using it.



Edit: I tested this, I don't think you are ever establishing a connection. If you add wait=True then you will probably see that the connection fails with a ConnectFailedException as mine did. This is probably the first thing to debug.



Edit 2: I solved it, you need to use SSL for your connection to the AWS MQ instance as follows:



conn = stomp.Connection(host_and_ports=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
lst = Listener()
conn.set_listener('Listener', lst)
conn.set_ssl(for_hosts=[('b-4714-4441-8166-47aae158281a-1.mq.eu-central-1.amazonaws.com', 61614)])
conn.start()






share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 23 at 10:24









Tinku

337




337










answered Nov 22 at 12:37









Rob Bricheno

2,305218




2,305218












  • I have updated response and code as well. MQ does has messages in it. Updated with proper URL of MQ with credentials. Please suggest
    – Tinku
    Nov 22 at 13:34












  • @Tinku did you try wait=True?
    – Rob Bricheno
    Nov 22 at 13:40










  • Yeah.. Even I received "errorType": "ConnectFailedException", error
    – Tinku
    Nov 22 at 13:42










  • How can I proceed from here. As I have given all the right values which I have
    – Tinku
    Nov 22 at 13:46










  • @Tinku check latest edit, I solved it, you need to use SSL :-)
    – Rob Bricheno
    Nov 22 at 14:00


















  • I have updated response and code as well. MQ does has messages in it. Updated with proper URL of MQ with credentials. Please suggest
    – Tinku
    Nov 22 at 13:34












  • @Tinku did you try wait=True?
    – Rob Bricheno
    Nov 22 at 13:40










  • Yeah.. Even I received "errorType": "ConnectFailedException", error
    – Tinku
    Nov 22 at 13:42










  • How can I proceed from here. As I have given all the right values which I have
    – Tinku
    Nov 22 at 13:46










  • @Tinku check latest edit, I solved it, you need to use SSL :-)
    – Rob Bricheno
    Nov 22 at 14:00
















I have updated response and code as well. MQ does has messages in it. Updated with proper URL of MQ with credentials. Please suggest
– Tinku
Nov 22 at 13:34






I have updated response and code as well. MQ does has messages in it. Updated with proper URL of MQ with credentials. Please suggest
– Tinku
Nov 22 at 13:34














@Tinku did you try wait=True?
– Rob Bricheno
Nov 22 at 13:40




@Tinku did you try wait=True?
– Rob Bricheno
Nov 22 at 13:40












Yeah.. Even I received "errorType": "ConnectFailedException", error
– Tinku
Nov 22 at 13:42




Yeah.. Even I received "errorType": "ConnectFailedException", error
– Tinku
Nov 22 at 13:42












How can I proceed from here. As I have given all the right values which I have
– Tinku
Nov 22 at 13:46




How can I proceed from here. As I have given all the right values which I have
– Tinku
Nov 22 at 13:46












@Tinku check latest edit, I solved it, you need to use SSL :-)
– Rob Bricheno
Nov 22 at 14:00




@Tinku check latest edit, I solved it, you need to use SSL :-)
– Rob Bricheno
Nov 22 at 14:00


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430332%2fresult-returned-by-aws-lambda-python-function-execution-in-null%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Calculate evaluation metrics using cross_val_predict sklearn

Insert data from modal to MySQL (multiple modal on website)