SQS plugin fails to access queue when inside jar file
Description
Gliffy Diagrams
Activity
louis z January 11, 2013 at 2:56 PM
I can confirm this issue is fixed in 1.1.8 however I encountered another critical issue with SQS input when it tries to receive a message...
JonathanQ January 4, 2013 at 12:20 AM
That definitely worked. I haven't actually given it an SQS message - but the errors on start-up are gone. So this issue is resolved by it. I was just trying to figure out how to patch this myself - but you beat me to it.
I'll use this dev built to finish my testing, but will wait fo the full 1.1.8 release to use in Production (unless its a month or so away that is).
Thanks!
Jordan Sissel January 4, 2013 at 12:11 AM
fixed in master with a workaround patching OpenSSL.
Can you try this build? http://r.logstash.net/jenkins/job/logstash.jar.daily/76/artifact/build/logstash-1.1.8.dev-monolithic.jar
It works for me.
Jordan Sissel January 3, 2013 at 11:05 PM
not yet, i'll see what I can do.
JonathanQ January 3, 2013 at 11:03 PM
Jordan - did you get a chance to code a workaround for this? I tried 1.1.7 (monolithic and flatjar) to see if that would work but the error is still present.
If I run logstash with
java -jar logstash-1.1.5-monolithic.jar agent -f logstash.conf
I get the following error:
Unable to access SQS queue 'logstash': jar:file:/opt/logstash/logstash-1.1.5-monolithic.jar!/gems/aws-sdk-1.7.1/ca-bundle.crt {:level=>:error}
However extracting the jar and running with
java -cp top/dir/of/unzip/ logstash.runner agent -f logstash.conf
It works fine.
This is the same for both the input and output plugin.