Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DEC2C9597 for ; Fri, 15 Jun 2012 08:05:52 +0000 (UTC) Received: (qmail 80165 invoked by uid 500); 15 Jun 2012 08:05:51 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 79062 invoked by uid 500); 15 Jun 2012 08:05:49 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 78768 invoked by uid 99); 15 Jun 2012 08:05:47 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2012 08:05:47 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id F3A5F141BF8 for ; Fri, 15 Jun 2012 08:05:46 +0000 (UTC) Date: Fri, 15 Jun 2012 08:05:46 +0000 (UTC) From: "licheng (JIRA)" To: dev@jackrabbit.apache.org Message-ID: <1129841869.18112.1339747547003.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (JCR-3344) Multhireads hang issue occurs because of oracle database socket read blocks forever MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 licheng created JCR-3344: ---------------------------- Summary: Multhireads hang issue occurs because of oracle database socket read blocks forever Key: JCR-3344 URL: https://issues.apache.org/jira/browse/JCR-3344 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Affects Versions: 2.2 Environment: Winxp+oracle+JBoss Reporter: licheng Fix For: 2.2 Attachments: dead lock_mr1.log, deak lock_mr2.log During our test, the network between JBoss and Oracle has some problem for a while. At that time, one JR thread which holding Global ISM lock is doing socket read with Oracle. Unfortunately, this blocking socket read doesn't return anymore. Meanwhile, some other threads are warting for the global ISM lock. As a result, many threads are blocked. Although we only hit it once, but it is really a serious problem. To workarount it, we have to restart our application server. To our custom, it is not acceptable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira