Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 67D6BCF6C for ; Thu, 5 Jun 2014 17:52:47 +0000 (UTC) Received: (qmail 63616 invoked by uid 500); 5 Jun 2014 17:52:47 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 63582 invoked by uid 500); 5 Jun 2014 17:52:47 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 63575 invoked by uid 99); 5 Jun 2014 17:52:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 17:52:47 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [207.46.163.183] (HELO na01-bn1-obe.outbound.protection.outlook.com) (207.46.163.183) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 17:52:41 +0000 Received: from BL2FFO11FD013.protection.gbl (10.173.160.33) by BL2FFO11HUB065.protection.gbl (10.173.161.165) with Microsoft SMTP Server (TLS) id 15.0.959.15; Thu, 5 Jun 2014 17:52:15 +0000 Received: from CPHUB1.canoga.com (74.62.37.82) by BL2FFO11FD013.mail.protection.outlook.com (10.173.160.221) with Microsoft SMTP Server (TLS) id 15.0.959.15 via Frontend Transport; Thu, 5 Jun 2014 17:52:15 +0000 Received: from vserver1.canoga.com ([169.254.2.31]) by CPHUB1.canoga.com ([172.16.1.93]) with mapi; Thu, 5 Jun 2014 10:51:19 -0700 From: "Bergquist, Brett" To: Derby Discussion Date: Thu, 5 Jun 2014 10:52:11 -0700 Subject: RE: Apache Derby - Locks up. Thread-Topic: Apache Derby - Locks up. Thread-Index: Ac9/z+4lKjFUW8MESWyEeJPqNpi0DABFsdWg Message-ID: <97EB699F861AD841B5908C7CA9C9565602BB097DAB6E@VSERVER1.canoga.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-tm-as-product-ver: SMEX-10.2.0.3176-7.500.1017-20738.005 x-tm-as-result: No--36.016700-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No Content-Type: multipart/alternative; boundary="_000_97EB699F861AD841B5908C7CA9C9565602BB097DAB6EVSERVER1can_" MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:74.62.37.82;CTRY:US;IPV:NLI;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(6009001)(428001)(377454003)(189002)(199002)(53416003)(74662001)(69596002)(80022001)(19580405001)(19580395003)(74502001)(46102001)(6806004)(19300405004)(83322001)(81342001)(4396001)(71186001)(81542001)(19625215002)(76482001)(15202345003)(87936001)(101416001)(79102001)(77982001)(64706001)(20776003)(512954002)(55846006)(2656002)(84326002)(86362001)(44976005)(81156002)(83072002)(76176999)(92726001)(85852003)(21056001)(54356999)(104016001)(33656002)(50986999)(15975445006)(99396002)(16236675004)(80792004);DIR:OUT;SFP:;SCL:1;SRVR:BL2FFO11HUB065;H:CPHUB1.canoga.com;FPR:;MLV:sfv;PTR:rrcs-74-62-37-82.west.biz.rr.com;MX:1;A:1;LANG:en; X-OriginatorOrg: canogaperkins.onmicrosoft.com X-Microsoft-Antispam: BL:0;ACTION:Default;RISK:Low;SCL:0;SPMLVL:NotSpam;PCL:0;RULEID: X-Forefront-PRVS: 0233768B38 Received-SPF: None (: canoga.com does not designate permitted sender hosts) Authentication-Results: spf=none (sender IP is 74.62.37.82) smtp.mailfrom=BBergquist@canoga.com; X-Virus-Checked: Checked by ClamAV on apache.org --_000_97EB699F861AD841B5908C7CA9C9565602BB097DAB6EVSERVER1can_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Chris, can you get a stack trace from the Network Server process when this = occurs? From: Chris Olver [mailto:chris.olver@3plearning.com] Sent: Wednesday, June 04, 2014 4:42 AM To: derby-user@db.apache.org Subject: Apache Derby - Locks up. Hi, We are looking to use Apache Derby (Network Server) as a Caching Layer for = our ETL process. Unfortunately we are finding that it locks up quite freque= ntly. We have two tables which have around 10 million rows, two indexes in = each. We can be reading (straight SELECT * FROM) or writing updates when it= happens. CPU will spike to 100% (its on a rather powerful box) and then all existing= and new JDBC clients are unable to connect. Running runtimeinfo (when it l= ocks up, issuing this command can take a few minutes to get a response): --- Derby Network Server Runtime Information --- ---------- Session Information --------------- Session # :116 Database :etl User : abc # Statements:1 Prepared Statement Information: Stmt ID SQLText ------------- ----------- SYSLH0001 SELECT * FROM APP.USERS Session # :117 ------------------------------------------------------------- # Connection Threads : 4 # Active Sessions : 2 # Waiting Sessions : 0 Total Memory : 1756889088 Free Memory : 306272128 No errors can be seen in the log. I am rather confused as it seems like the= perfect solution Derby just locks up. Thoughts or advise appreciated. OS: Windows 8.1 Java Runtime: 1.8.0_05-b13 Derby: 10.10.2.0 Regards, -Chris --_000_97EB699F861AD841B5908C7CA9C9565602BB097DAB6EVSERVER1can_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Chris, can you get a stack trace from the Network Ser= ver process when this occurs?

 

From: Chris Olver [mailto:chris.olver@3plearning.com]
= Sent: Wednesday, June 04, 2014 4:42 AM
To: derby-user@db.apac= he.org
Subject: Apache Derby - Locks up.

 

Hi,

 

W= e are looking to use Apache Derby (Network Server) as a Caching Layer for o= ur ETL process. Unfortunately we are finding that it locks up quite frequen= tly. We have two tables which have around 10 million rows, two indexes in e= ach. We can be reading (straight SELECT * FROM) or writing updates when it = happens.

 

CPU will sp= ike to 100% (its on a rather powerful box) and then all existing and new JD= BC clients are unable to connect. Running runtimeinfo (when it locks up, is= suing this command can take a few minutes to get a response):

 

--- Derby Network Server Runtime I= nformation ---

---------- Session Information ---------------

Session # :116

Database :etl

User : abc

# Statements:1

Prepared Statement Information:=

    =     Stmt ID         = SQLText

 =        -------------   -----------<= o:p>

  &n= bsp;     SYSLH0001       = SELECT * FROM APP.USERS

 

Session # :117

-------------------------------------------------------------

# Connection Threads : = 4

# Active Ses= sions : 2

# Wa= iting  Sessions : 0

 

Total Memory : 1756889088       Free Memo= ry : 306272128

 

No err= ors can be seen in the log. I am rather confused as it seems like the perfe= ct solution Derby just locks up.

=  

Thoughts or advise appreciated.

 

OS: Windows 8.1

Java Runtime: 1.8.0_05-b13

=

Derby: 10.10.2.0<= /p>

 

Regards,

 

-Chris

= --_000_97EB699F861AD841B5908C7CA9C9565602BB097DAB6EVSERVER1can_--