You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Alice Chen (JIRA)" <ji...@apache.org> on 2015/07/22 20:14:25 UTC
[jira] [Created] (TRAFODION-156) LP Bug: 1252790 - getConnection()
returns Zookeeper not in connecting state error
Alice Chen created TRAFODION-156:
------------------------------------
Summary: LP Bug: 1252790 - getConnection() returns Zookeeper not in connecting state error
Key: TRAFODION-156
URL: https://issues.apache.org/jira/browse/TRAFODION-156
Project: Apache Trafodion
Issue Type: Bug
Components: connectivity-dcs
Reporter: Weishiun Tsai
Assignee: Tharak Capirala
Priority: Critical
Fix For: 0.9 (pre-incubation)
When running a program that does lots of connections/disconnections, that program would see the following error every now and then. This has been seen on both a VM and a cluster machine. It always happens at the JDBC call:
conn = DriverManager.getConnection(url, props);
java.lang.AssertionError: Trafodian Internal error: Zookeeper entry not in connecting state. Current state is AVAILABLE
This is not easy to reproduce. Sometimes you have to run phoenix tests several times to run into one, but it has happened frequently enough that it may cause phoenix tests to fail once Jenkins start to run the tests automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)