phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3826) Exception stack trace is being logged in info mode when new phoenix connection is created
Date Wed, 03 May 2017 07:55:04 GMT


Hadoop QA commented on PHOENIX-3826:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit 5b099014446865c12779f3882fd8b407496717ea.
  ATTACHMENT ID: 12866137

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 javac{color}.  The patch appears to cause mvn compile goal to fail .

    Compilation errors resume:
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade
(default) on project phoenix-pig: Error creating shaded jar: null: NullPointerException ->
[Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following
[ERROR] [Help 1]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :phoenix-pig

Console output:

This message is automatically generated.

> Exception stack trace is being logged in info mode when new phoenix connection is created

> ------------------------------------------------------------------------------------------
>                 Key: PHOENIX-3826
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.11.0, 4.10.1
>            Reporter: Loknath Priyatham Teja Singamsetty 
>            Assignee: Loknath Priyatham Teja Singamsetty 
>            Priority: Minor
>         Attachments: PHOENIX-3826.patch
> Exception is being raised when new phoenix connection is created 
> 2017-05-03 05:51:39,898 INFO  [main] query.ConnectionQueryServicesImpl - An instance
of ConnectionQueryServices was created: java.lang.Exception
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl$
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl$
> 	at
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl.init(
> 	at org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(
> 	at org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.createConnection(
> 	at org.apache.phoenix.jdbc.PhoenixDriver.connect(
> 	at sqlline.DatabaseConnection.connect(
> 	at sqlline.DatabaseConnection.getConnection(
> 	at sqlline.Commands.connect(
> 	at sqlline.Commands.connect(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at sqlline.ReflectiveCommandHandler.execute(
> 	at sqlline.SqlLine.dispatch(
> 	at sqlline.SqlLine.initArgs(
> 	at sqlline.SqlLine.begin(
> 	at sqlline.SqlLine.start(
> 	at sqlline.SqlLine.main(
> We can simply log a message without printing the stack trace.

This message was sent by Atlassian JIRA

View raw message