[ 
https://issues.apache.org/jira/browse/HIVE-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617189#comment-13617189
 ] 

Teddy Choi commented on HIVE-4257:
----------------------------------

If you get "java.lang.SecurityException: sealing violation" message, please 
remove derby-10.4.2.0.jar file from your target directories. 
(build/ivy/lib/default/, build/ivy/lib/compile/, build/ivy/lib/test/)
                
> java.sql.SQLNonTransientConnectionException on JDBCStatsAggregator
> ------------------------------------------------------------------
>
>                 Key: HIVE-4257
>                 URL: https://issues.apache.org/jira/browse/HIVE-4257
>             Project: Hive
>          Issue Type: Bug
>          Components: Statistics
>    Affects Versions: 0.11.0
>            Reporter: Teddy Choi
>             Fix For: 0.11.0
>
>         Attachments: HIVE-4257.1.patch.txt
>
>
> java.sql.SQLNonTransientConnectionException occurs on JDBCStatsAggregator 
> after executing dozens of Hive queries periodically, which inserts thousands 
> of rows. It may have a relation with DERBY-5098. To avoid this error, Hive 
> should use a more recent version of Derby(10.6.2.3, 10.7.1.4, 10.8.2.2, 
> 10.9.1.0 or later). Hive 0.11.0-SNAPSHOT uses Derby 10.4.2.0.
> {noformat}
> 2013-03-24 15:54:30,487 ERROR jdbc.JDBCStatsAggregator 
> (JDBCStatsAggregator.java:aggregateStats(168)) - Error during publishing 
> aggregation. java.sql.SQLNonTransientConnectionException: No current 
> connection.
> 2013-03-24 15:54:30,487 ERROR jdbc.JDBCStatsAggregator 
> (JDBCStatsAggregator.java:aggregateStats(168)) - Error during publishing 
> aggregation. java.sql.SQLNonTransientConnectionException: No current 
> connection.
> 2013-03-24 15:54:30,487 ERROR jdbc.JDBCStatsAggregator 
> (JDBCStatsAggregator.java:cleanUp(249)) - Error during publishing 
> aggregation. java.sql.SQLNonTransientConnectionException: No current 
> connection.
> {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

Reply via email to