-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin does not work with Logstash 5.0.2 #14
Comments
Same problem here with LS 5.1.1 clone |
Hi,
So I tried updating it, I get,
This doesn't work as well
Can you please help me. Thanks, |
@arun-a-nayagam what version of Logstash are you using? I just tried with 5.2.0 and it worked fine as well. |
I installed a 2.0.3 before, on top of it I tried installing like this, And I am seeing errors I have listed above. |
@arun-a-nayagam The question was about the version of Logstash, not the logstash-input-jms plugin. This doesn't seem to be an issue with the plugin itself. Do you have internet access via proxy or directly? You can't update a plugin without an access to internet. See elastic/logstash#6619 in case of proxy. If it doesn't help, try to use
to check the plugin version,
to start with clean table and then
|
Please post all product and debugging questions on our forum. Your questions will reach our wider community members there, and if we confirm that there is a bug, then we can open a new issue here.
For all general issues, please provide the following details for fast resolution:
jms {
yaml_file => "/opt/monitoring/logstash/conf/jmsConf.yml"
yaml_section => "perf"
include_header => true
include_properties => true
include_body => true
use_jms_timestamp => false
destination => "Company.WOR.Service.Public.Notify.Utility.Monitoring.ElasticSearch.1"
interval => 3
runner => async
}
Sample Data:
Steps to Reproduce:
Attributes: {:jms_correlation_id=>"", :jms_delivery_mode_sym=>:persistent, :jms_destination=>"Queue[Company.BEL.Service.Public.Notify.Utility.Monitoring.ElasticSearch.1]", :jms_expiration=>0, :jms_message_id=>"ID:perf_instance_B_9602.7F285797493C1:13B734CB6", :jms_priority=>4, :jms_redelivered=>false, :jms_reply_to=>nil, :jms_timestamp=>1481899929616, :jms_type=>nil}
Properties: {"JMSXDeliveryCount"=>1, "scaOperationName"=>"publishNotification", "JMS_TIBCO_COMPRESS"=>true, "messageId"=>"9975035464", "clientTransactionId"=>"6807135713"}, :exception=>#<NoMethodError: Direct event field references (i.e. event['field'] = 'value') have been disabled in favor of using event get and set methods (e.g. event.set('field', 'value')). Please consult the Logstash 5.0 breaking changes documentation for more details.>, :backtrace=>["/opt/monitoring/logstash/5.0.2/logstash-core-event-java/lib/logstash/event.rb:44:in `method_missing'", "/opt/monitoring/logstash/5.0.2/vendor/bundle/jruby/1.9/gems/logstash-input-jms-2.0.3-java/lib/logstash/inputs/jms.rb:160:
Appreciate your help.
Thanks,
Arun
The text was updated successfully, but these errors were encountered: