# ES 2.0 strange java.io.StreamCorruptedException **URL:** \ **Category:** Elasticsearch\ **Created:** [November 12, 2015, 1:20pm UTC](https://discuss.elastic.co/t/es-2-0-strange-java-io-streamcorruptedexception/34417 "2015-11-12T13:20:24Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![zdeseb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zdeseb/32/42106_2.png) [@zdeseb](https://discuss.elastic.co/u/zdeseb)\ **Post date:** [November 12, 2015, 1:20pm UTC](https://discuss.elastic.co/t/es-2-0-strange-java-io-streamcorruptedexception/34417/1 "2015-11-12T13:20:25Z")
When I start ES 2.0 as is extracted from ZIP file on my Windows 7 x64 computer, I get multiple (12x) WARNINGS like following: ` [2015-11-12 13:34:08,248][WARN][transport.netty] [Lorelei II] exception caught on transport layer [[id: 0xf9e16854, /127.0.0.1:3940 => /127.0.0.1:9300]], closing connection java.io.StreamCorruptedException: invalid internal transport message format, got (48,54,54,50) ... ` After these warnings, starting continues and ES eventually stays running. I tried this with different Java versions }for example jdk1.7.0\_71, jre1.8.0\_65 or jdk1.8.0\_65] but with exactly the same result. **If I try the same test with ES 1.7.3 ZIP file, no WARNING appears.** I know it is something specific for my PC, for when I tried it on one of our test servers, it worked fine. But I am little bit nervous. I would like to understand this WARNING before I start with cluster upgrade. Any idea what is this WARNING about? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 12, 2015, 1:38pm UTC](https://discuss.elastic.co/t/es-2-0-strange-java-io-streamcorruptedexception/34417/2 "2015-11-12T13:38:13Z")
A first guess is that you have another node running using another elasticsearch version which is trying to connect to this node... ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 12, 2015, 11:12pm UTC](https://discuss.elastic.co/t/es-2-0-strange-java-io-streamcorruptedexception/34417/3 "2015-11-12T23:12:47Z")
I'll second that assessment! 🙂 ---
**Author:** ![cching](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cching/32/44800_2.png) [@cching](https://discuss.elastic.co/u/cching)\ **Post date:** [November 13, 2015, 1:16am UTC](https://discuss.elastic.co/t/es-2-0-strange-java-io-streamcorruptedexception/34417/4 "2015-11-13T01:16:41Z")
Sorry to jump on the pile, but I'll third it. Just ran into this last night, swore up and down that I had my storm deployment right only to find that I'd been deploying a stale build artifact that included the old 1.7 client for ES 😒 ---
**Author:** ![zdeseb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zdeseb/32/42106_2.png) [@zdeseb](https://discuss.elastic.co/u/zdeseb)\ **Post date:** [November 13, 2015, 7:57am UTC](https://discuss.elastic.co/t/es-2-0-strange-java-io-streamcorruptedexception/34417/5 "2015-11-13T07:57:04Z")
I did fresh boot of my system and the only thing I did was that I unzipped original Elasticsearch distribution package and executed elasticearch.bat Before this, I had checked that no java process was running. Ss you can see from log, communication is within local computer and default configuration of Elasticsearch doesn't allow remote connections anyway. So I can't imagine what communication is going on ☹ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:38pm UTC](https://discuss.elastic.co/t/es-2-0-strange-java-io-streamcorruptedexception/34417/6 "2017-07-05T23:38:42Z")