Return-Path: 
 <dev-return-27622-apmail-zookeeper-dev-archive=zookeeper.apache.org@zookeeper.apache.org>
X-Original-To: apmail-zookeeper-dev-archive@www.apache.org
Delivered-To: apmail-zookeeper-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 DAA7810C4A
	for <apmail-zookeeper-dev-archive@www.apache.org>;
 Mon, 23 Sep 2013 22:58:18 +0000 (UTC)
Received: (qmail 34609 invoked by uid 500); 23 Sep 2013 22:58:12 -0000
Delivered-To: apmail-zookeeper-dev-archive@zookeeper.apache.org
Received: (qmail 34405 invoked by uid 500); 23 Sep 2013 22:58:06 -0000
Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@zookeeper.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@zookeeper.apache.org>
List-Post: <mailto:dev@zookeeper.apache.org>
List-Id: <dev.zookeeper.apache.org>
Reply-To: dev@zookeeper.apache.org
Delivered-To: mailing list dev@zookeeper.apache.org
Received: (qmail 34360 invoked by uid 99); 23 Sep 2013 22:58:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Sep 2013 22:58:04 +0000
Date: Mon, 23 Sep 2013 22:58:04 +0000 (UTC)
From: "Jeffrey Zhong (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.12644355.1366810763200.5585.1379977084923@arcas>
In-Reply-To: <JIRA.12644355.1366810763200@arcas>
References: <JIRA.12644355.1366810763200@arcas>
Subject: [jira] [Updated] (ZOOKEEPER-1696) Fail to run zookeeper client on
 Weblogic application server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey Zhong updated ZOOKEEPER-1696:
-------------------------------------

    Attachment: zookeeper-1696-v2.patch

[~fpj] Ok. In the v2 patch, only Security(existing) and IllegalArgumentException are handled without catching other types of runtime exception to be conservative for now. Thanks.
                
> Fail to run zookeeper client on Weblogic application server
> -----------------------------------------------------------
>
>                 Key: ZOOKEEPER-1696
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1696
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.4.5
>         Environment: Java version: jdk170_06
> WebLogic Server Version: 10.3.6.0 
>            Reporter: Dmitry Konstantinov
>            Assignee: Jeffrey Zhong
>            Priority: Critical
>             Fix For: 3.4.6
>
>         Attachments: zookeeper-1696.patch, zookeeper-1696-v1.patch, zookeeper-1696-v2.patch
>
>
> The problem in details is described here: http://comments.gmane.org/gmane.comp.java.zookeeper.user/2897
> The provided link also contains a reference to fix implementation.
> {noformat}
> ####<Apr 24, 2013 1:03:28 PM MSK> <Warning> <org.apache.zookeeper.ClientCnxn> <devapp090> <clust2> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (devapp090:2182)> <internal> <> <> <1366794208810> <BEA-000000> <WARN  org.apache.zookeeper.ClientCnxn - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
> java.lang.IllegalArgumentException: No Configuration was registered that can handle the configuration named Client
>                 at com.bea.common.security.jdkutils.JAASConfiguration.getAppConfigurationEntry(JAASConfiguration.java:130)
>                 at org.apache.zookeeper.client.ZooKeeperSaslClient.<init>(ZooKeeperSaslClient.java:97)
>                 at org.apache.zookeeper.ClientCnxn$SendThread.startConnect(ClientCnxn.java:943)
>                 at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:993)
> >
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira