I get this error, after Logstash (Shipper) runs for a while:

A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006e4c2105, pid=9052, tid=29460

    JRE version: Java(TM) SE Runtime Environment (7.0_76-b13) (build 1.7.0_76-b13)
    Java VM: Java HotSpot(TM) 64-Bit Server VM (24.76-b04 mixed mode windows-amd64 compressed oops)
    Problematic frame: C  [jffi-1.2.dll+0x2105]

This is my architecure:

Logstash (Shipper) => Redis => Logstash (Indexer) => ES => Kibana

Somebody any idea whats that jiffi-1.2.dll do or whats my problem?

input {
file {
type => "log4j"
path => "//1/logs//.log"
path => "//2/logs//
path => "//3/logs//.log"
start_position => beginning
sincedb_path => null
codec => plain { charset => "ISO-8859-1" }
output {
redis {
host => ["
shuffle_hosts => true
data_type => "list"
key => "logstash"
workers => 16
batch => true
codec => plain { charset => "ISO-8859-1" }

@diwertowski which version of logstash are you running and on what Windows version?


My logstash version: 2.2.0
I tried it on a Windows Server 2008 and on Windows 7.
Maybe its a Redis-Plugin problem?

In version 2.3.1 I get the exception_access_violation too.
But with version 2.3.0 everything is fine. So what does 2.3.0 better than 2.3.1?!
I didn't change anything in my configuration. I took the same configurations for all versions and started them in the same way.