From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 740E617DEDC3 for ; Sat, 4 Apr 2015 19:43:01 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (smtp.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id EFBD1B5D901 for ; Sat, 4 Apr 2015 19:52:31 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 4DC4D97A82B for ; Sat, 4 Apr 2015 19:52:34 +0900 (JST) X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp Authentication-Results: funfun.nagaokaut.ac.jp (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sendgrid.me Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqV_n_y1K_5R for ; Sat, 4 Apr 2015 19:52:34 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 2197F97A820 for ; Sat, 4 Apr 2015 19:52:34 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id A41D7952439 for ; Sat, 4 Apr 2015 19:52:30 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 7E5291204C8; Sat, 4 Apr 2015 19:52:29 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o10.shared.sendgrid.net (o10.shared.sendgrid.net [173.193.132.135]) by neon.ruby-lang.org (Postfix) with ESMTPS id 4F163120488 for ; Sat, 4 Apr 2015 19:52:26 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=NHOAyr/rB1NVCw8ET7T2E2mmWso=; b=vR5vGLKFsxRJ2bMsTA 3dhE+0V/wvsQbk4FzfwRFYuQozTJXU9MhTXpLMSvDv4gfZWb/B+9c8OvjJ+9Xb0A 4Vpprsj2RUGXcsyPylSjDmVSBj/YT/KyFd6sYiRGX6TqzFpF/khV1aZWmIt0KzQQ wvQgoPkKsyOVj9lC2o1oPI4zc= Received: by filter0370p1mdw1.sendgrid.net with SMTP id filter0370p1mdw1.24534.551FC2661 2015-04-04 10:52:22.112039024 +0000 UTC Received: from herokuapp.com (ec2-23-22-203-240.compute-1.amazonaws.com [23.22.203.240]) by ismtpd-023 (SG) with ESMTP id 14c840f5eb3.621d.a12b72 for ; Sat, 04 Apr 2015 10:52:22 +0000 (UTC) Date: Sat, 04 Apr 2015 10:52:22 +0000 From: mail@tknerr.de To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 43162 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11033 X-Redmine-Issue-Author: tknerr X-Redmine-Sender: tknerr X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: OOF Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS4mgnVSuVTIprXkuwE8nlgaxqh4thmDcQ9NO0 W7cdBuNz7Ykp3wet1makrh/3qZh/wdXDV3eYp9/OwclkptLMsH3UUTKaHtljpbHosPAMvJO3ZlPqKS m2znMuVqy6QZwyHUZwnxTsnSIOqkJhjvkHWP X-SendGrid-Contentd-ID: {"test_id":"1428144743"} X-ML-Name: ruby-core X-Mail-Count: 68754 Subject: [ruby-core:68754] [Ruby trunk - Bug #11033] OpenSSL related threading issues in Ruby 2.1 and 2.2 X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11033 has been updated by Torben Knerr. Just double-checked whether it might be a RubyGems issue. So I downgraded Rubygems to 2.4.4 (the version that ships with Ruby 2.0, where everything works), but still the same behaviour => not related to RubyGems, more likely a core issue ---------------------------------------- Bug #11033: OpenSSL related threading issues in Ruby 2.1 and 2.2 https://bugs.ruby-lang.org/issues/11033#change-52037 * Author: Torben Knerr * Status: Open * Priority: Normal * Assignee: * ruby -v: 2.1.5p273, 2.2.1p85 * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- I'm experiencing some problems with multiple https connections in Ruby 2.1 and 2.2, whilst in Ruby 2.0 everything is working fine. This happens on a Windows 7 (64-bit) box in the context of installing multiple gems in parallel via bundlers `BUNDLE_JOBS=` setting. What I see are multiple `OpenSSL::SSL::SSLError: SSL_read: cert already in hash table` warnings and at some more or less random point it bails out because it cannot install a gem. When I repeat the `bundle install` command it will get past that gem and fail at a later one. I can repeat until all gems are installed. This is the stacktrace I get for every of the ssl warnings: ``` ... Installing polyglot 0.3.5 4: polyglot (0.3.5) from X:/home/.gem/ruby/2.2.0/specifications/polyglot-0.3.5.gemspec OpenSSL::SSL::SSLError: SSL_read: cert already in hash table X:/tools/ruby-2.2.1/lib/ruby/2.2.0/openssl/buffering.rb:182:in `sysread_nonblock' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/openssl/buffering.rb:182:in `read_nonblock' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/protocol.rb:153:in `rbuf_fill' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/protocol.rb:134:in `readuntil' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/protocol.rb:144:in `readline' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/http/response.rb:39:in `read_status_line' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/http/response.rb:28:in `read_new' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:1414:in `block in transport_request' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:1411:in `catch' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:1411:in `transport_request' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/net/http.rb:1384:in `request' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/request.rb:154:in `perform_request' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/request.rb:109:in `fetch' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/remote_fetcher.rb:346:in `request' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/remote_fetcher.rb:231:in `fetch_http' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/remote_fetcher.rb:247:in `fetch_http' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/remote_fetcher.rb:267:in `fetch_path' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/remote_fetcher.rb:302:in `cache_update_path' X:/tools/ruby-2.2.1/lib/ruby/2.2.0/rubygems/remote_fetcher.rb:168:in `download' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/rubygems_integration.rb:544:in `download_gem' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/fetcher.rb:63:in `download_gem_from_uri' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/source/rubygems.rb:370:in `fetch_gem' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/source/rubygems.rb:98:in `install' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/installer.rb:107:in `install_gem_from_spec' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/installer.rb:287:in `block in install_in_parallel' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/worker.rb:55:in `call' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/worker.rb:55:in `apply_func' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/worker.rb:50:in `block in process_queue' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/worker.rb:47:in `loop' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/worker.rb:47:in `process_queue' X:/tools/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/bundler-1.9.2/lib/bundler/worker.rb:22:in `block (2 levels) in initialize' ... ``` This is originally reported here (with a bit more details): https://github.com/bundler/bundler/issues/3545 Any ideas? Might it be a regression of #8386? -- https://bugs.ruby-lang.org/