Well, the guy in "stackoverflow" was experience connection timeout. This looks like a firewall issue or some edge case connection issue. If you could just run "telnet sqs.us-east-1.amazonaws.com 80" command and verify if you are able to hit the publicly exposed SQS endpoint. I don't think JMeter had anything to do with the connection issues.
I feel creating a BeanShell is fairly easy given that the entire Java code for generating the signature is provided here: http://docs.aws.amazon.com/general/latest/gr/signature-version-2.html If you want to take the route of creating custom Java Request. You could use this. https://github.com/coolcodr/jmeter-aws-sqs Thanks Chaitanya M Bhatt On Thu, Apr 14, 2016 at 11:49 AM, Hui Ai Chan <[email protected]> wrote: > Thank you for your quick response. I looked into using HTTP Requests, it > requires AUTHPARAMS to be generated and frankly looks too complicated to > implement with BeanShell pre processor. That's why I opted to use JMS > request because the AWS SDK is supposed to have that piece done for us. ( > http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/Query_QueryAuth.html > ) > Also found another thread on Stackoverflow where someone else tried the > HTTP Request and ran into different problems. ( > http://stackoverflow.com/questions/33194219/using-jmeter-to-load-test-amazon-sqs-not-all-messages-making-it-through > ) > > I think my next approach is to follow the Amazon SDK and build my own Java > application to send the messages and then use either Java Request or Junit > Request in JMeter to generate the load. > > I'm open to suggestions. > > ________________________________________ > From: chaitanya bhatt <[email protected]> > Sent: Wednesday, April 13, 2016 8:06 PM > To: JMeter Users List > Subject: Re: Using JMS Publisher for Amazon SQS > > AWS SQS has a HTTP end points for topics/queues. You do not have to build > the request using JMS sampler. In my opinion, the Http sampler should work > for constructing messaging requests. > > > http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/MakingRequests_MakingQueryRequestsArticle.html > > Thanks > Chaitanya M Bhatt > > On Wed, Apr 13, 2016 at 1:43 PM, Hui Ai Chan <[email protected]> wrote: > > > Hi, I'm trying to publish messages to Amazon SQS. Following the > > instructions in the user manual ( > > > http://jmeter.apache.org/usermanual/component_reference.html#JMS_Publisher > ), > > I have downloaded the JMS implementation jar ( > > https://github.com/awslabs/amazon-sqs-java-messaging-lib) and put it in > > the lib directory. > > > > From the jar, I can tell the Connection Factory is > > "com.amazon.sqs.javamessaging.SQSConnectionFactory" and so I have entered > > that under the Connection Factory field in the JMS Publisher. > Unfortunately > > it doesn't look like the SQS lib implements the Initial Context Factory. > > And I can't figure out what to put in a JNDI.properties, or how to pass > in > > the AWS Credentials. > > > > Has anyone else used the JMS samplers with Amazon SQS before? I'd > > appreciate a few tips. Thanks! > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
