java.lang.Exception: Unique index 'catenode_uniq= ue_idx' cannot be added to table 'category_node' because 502 rows are not = unique. See the install guide for details on how to correct this problem. = You can use the following SQL to see which rows are not unique: SELECT * FROM category_node WHERE ( categoryId, nodeId ) IN ( SELECT = categoryId, nodeId FROM category_node GROUP BY categoryId, nodeId HAVING = count(categoryId) > 1 ORDER BY categoryId, nodeId ) ORDER BY categoryId, = nodeId at org.opennms.netmgt.dao.db.InstallerDb.checkIndexUniqueness(Insta= llerDb.java:2135)

sourceforge.net | 4 months ago
  1. 0

    OpenNMS / Mailing Lists

    sourceforge.net | 4 months ago
    java.lang.Exception: Unique index 'catenode_uniq= ue_idx' cannot be added to table 'category_node' because 502 rows are not = unique. See the install guide for details on how to correct this problem. = You can use the following SQL to see which rows are not unique: SELECT * FROM category_node WHERE ( categoryId, nodeId ) IN ( SELECT = categoryId, nodeId FROM category_node GROUP BY categoryId, nodeId HAVING = count(categoryId) > 1 ORDER BY categoryId, nodeId ) ORDER BY categoryId, = nodeId at org.opennms.netmgt.dao.db.InstallerDb.checkIndexUniqueness(Insta= llerDb.java:2135)
  2. 0

    OpenNMS / Mailing Lists

    sourceforge.net | 6 months ago
    java.lang.Exception: property "importer.requisition.dir" not set from bundled installer.properties file
  3. 0

    OpenNMS / Mailing Lists

    sourceforge.net | 6 months ago
    java.lang.Exception: property "importer.requisition.dir" not set from bundled installer.properties file
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    HikariCP detects connectionleak even though all of my code has a call to close method

    Stack Overflow | 2 months ago | JRojo
    java.lang.Exception: Apparent connection leak detected I already checked and made sure all my sql codes has a call to close method. Here's my HikariConfig : private HikariConfig hikariConfig() { HikariConfig config = new HikariConfig(); config.setDriverClassName(CLASS_FOR_NAME); config.setJdbcUrl(HOST); config.setUsername(USER); config.setPassword(PASS); config.addDataSourceProperty("cachePrepStmts", "true"); config.addDataSourceProperty("prepStmtCacheSize", "250"); config.addDataSourceProperty("prepStmtCacheSqlLimit", "2048"); config.setLeakDetectionThreshold(TimeUnit.SECONDS.toMillis(30)); config.setValidationTimeout(TimeUnit.MINUTES.toMillis(1)); config.setMaximumPoolSize(40); config.setMinimumIdle(0); config.setMaxLifetime(TimeUnit.MINUTES.toMillis(2)); // 120 seconds max life time config.setIdleTimeout(TimeUnit.MINUTES.toMillis(1)); // minutes config.setConnectionTimeout(TimeUnit.MINUTES.toMillis(5)); // millis config.setConnectionTestQuery("/* ping */ SELECT 1"); return config; } here's how my queries look like : public ArrayList<LocationType> getLocationTypes() { ArrayList<LocationType> locationTypes = new ArrayList<>(); Connection connection = null; PreparedStatement pstmt = null; ResultSet resultSet = null; try { connection = DataSource.getInstance().getConnection(); pstmt = connection.prepareStatement("SELECT\n" + " location_type_id,\n" + " location_type_name\n" + "FROM tablename;"); resultSet = pstmt.executeQuery(); while (resultSet.next()) { locationTypes.add(new LocationType(resultSet.getInt("location_type_id"), resultSet.getString("location_type_name"))); } } catch (Exception e) { e.printStackTrace(); } finally { if (resultSet != null) try { resultSet.close(); } catch (SQLException e) { } if (pstmt != null) try { pstmt.close(); } catch (SQLException e) { } if (connection != null) try { connection.close(); } catch (SQLException e) { } } return locationTypes; } I've already tried increasing the connectionLeakDetection, max connection and minimum idle but none of that solved the issue. I have read that it could be caused by the machine(low resources) and connections being closed, I think however, none of these causes the issue. I noticed that some long queries in my code are now being detected as connection leak, even though I am not calling their methods. I hope you guys could help. This is the stack trace : at com..database.DataSource.getConnection(DataSource.java:148)
  6. 0

    Bug Reports/Unresolved - JAMWiki Java Wiki Engine

    jamwiki.org | 4 months ago
    java.lang.Exception: Failure while executing BEGIN DECLARE @COUNT int DECLARE @TOP int DECLARE @OFFSET int DECLARE @LIMIT int DECLARE @SQL varchar(300) SET @LIMIT = ? SET @OFFSET = ? SET @TOP = @LIMIT SET @COUNT = (select count(*) from jam_wiki_user_info) IF (@OFFSET > @COUNT) SET @OFFSET = @COUNT IF (@COUNT < @OFFSET + @LIMIT) SET @TOP = @COUNT - @OFFSET SET @SQL = 'select * from ( ' + 'select top '+CONVERT(VARCHAR, @TOP)+' * from ( ' + 'select top '+CONVERT(VARCHAR, @OFFSET + @LIMIT)+' login ' + 'from jam_wiki_user_info + 'order by login ' + ') a ' + 'order by login desc ' + ') b ' + ' order by login ' EXEC(@SQL) END

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.Exception

      Unique index 'catenode_uniq= ue_idx' cannot be added to table 'category_node' because 502 rows are not = unique. See the install guide for details on how to correct this problem. = You can use the following SQL to see which rows are not unique: SELECT * FROM category_node WHERE ( categoryId, nodeId ) IN ( SELECT = categoryId, nodeId FROM category_node GROUP BY categoryId, nodeId HAVING = count(categoryId) > 1 ORDER BY categoryId, nodeId ) ORDER BY categoryId, = nodeId at org.opennms.netmgt.dao.db.InstallerDb.checkIndexUniqueness(Insta= llerDb.java:2135)

      at org.opennms.install.Installer.install()
    2. org.opennms.install
      Installer.main
      1. org.opennms.install.Installer.install(Installer.java:221)
      2. org.opennms.install.Installer.main(Installer.java:679)
      2 frames