Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2005

DB2 throws warning about inability to verify tables

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • AMQ 7.2.2.GA
    • AMQ 7.2.1.GA
    • jdbc
    • None
    • Release Notes
    • Hide
      Cause:
      IBM DB2 is not relieable while querying metadata for table existence (table exists, but any attempts to query it will fail) regardless the requests are being concurrent with any other DB operation
      Consequence:
      Checking for table presence on start up of the broker raise several scary warnings even if there isn't any real issue.
      Fix:
      Lower the level of the warning logs while checking for table presence.
      Result:
      Upon table presence checking there won't be any scary logs with IBM DB2.
      Show
      Cause: IBM DB2 is not relieable while querying metadata for table existence (table exists, but any attempts to query it will fail) regardless the requests are being concurrent with any other DB operation Consequence: Checking for table presence on start up of the broker raise several scary warnings even if there isn't any real issue. Fix: Lower the level of the warning logs while checking for table presence. Result: Upon table presence checking there won't be any scary logs with IBM DB2.
    • AMQ Broker 1839, AMQ Broker 1842

    Description

      At the start of the broker with DB2 as JDBC store, there are warnings about Can't verify the initialization of table LARGE_MESSAGES_TABLE due to...

      They do not seem to impact usage.
      fnigro might have already some fix for this upstream.

      2018-09-25 10:09:22,049 INFO  [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server
2018-09-25 10:09:22,290 INFO  [org.apache.activemq.artemis.core.server] AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,jdbcDriverClassName=com.ibm.db2.jcc.DB2Driver,jdbcConnectionUrl=jd
bc:db2://db2-111.databse.redhat.com:50000/dballo:user=user;password=userpw;,messageTableName=MESSAGE_TABLE,bindingsTableName=BINDINGS_TABLE,largeMessageTableName=LARGE_MESSAGES_TABLE,pageStoreTableName=PG_TBL,)
2018-09-25 10:09:28,002 WARN  [org.apache.activemq.artemis.jdbc.store.drivers.AbstractJDBCDriver] Can't verify the initialization of table LARGE_MESSAGES_TABLE due to:
SQL STATEMENTS:
SELECT COUNT(*) FROM LARGE_MESSAGES_TABLE
SQL EXCEPTIONS:
SQLState: 42704 ErrorCode: -204 Message: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBALLO02.LARGE_MESSAGES_TABLE, DRIVER=4.24.92
 SQLState: 56098 ErrorCode: -727 Message: DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-204;42704;DBALLO02.LARGE_MESSAGES_TABLE, DRIVER=4.24.92
2018-09-25 10:09:29,508 WARN  [org.apache.activemq.artemis.jdbc.store.drivers.AbstractJDBCDriver] Can't verify the initialization of table PG_TBL due to:
SQL STATEMENTS:
SELECT COUNT(*) FROM PG_TBL
SQL EXCEPTIONS:
SQLState: 42704 ErrorCode: -204 Message: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBALLO02.PG_TBL, DRIVER=4.24.92
 SQLState: 56098 ErrorCode: -727 Message: DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-204;42704;DBALLO02.PG_TBL, DRIVER=4.24.92
2018-09-25 10:09:30,156 INFO  [org.apache.activemq.artemis.core.server] AMQ221057: Global Max Size is being adjusted to 1/2 of the JVM max size (-Xmx). being defined as 1,073,741,824
2018-09-25 10:09:30,212 INFO  [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
2018-09-25 10:09:30,213 INFO  [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
2018-09-25 10:09:30,213 INFO  [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
2018-09-25 10:09:30,213 INFO  [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found: [artemis-mqtt-protocol]. Adding protocol support for: MQTT
2018-09-25 10:09:30,214 INFO  [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found: [artemis-openwire-protocol]. Adding protocol support for: OPENWIRE
2018-09-25 10:09:30,214 INFO  [org.apache.activemq.artemis.core.server] AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
2018-09-25 10:09:31,588 WARN  [org.apache.activemq.artemis.jdbc.store.drivers.AbstractJDBCDriver] Can't verify the initialization of table BINDINGS_TABLE due to:
SQL STATEMENTS:
SELECT COUNT(*) FROM BINDINGS_TABLE
SQL EXCEPTIONS:
SQLState: 42704 ErrorCode: -204 Message: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBALLO02.BINDINGS_TABLE, DRIVER=4.24.92
 SQLState: 56098 ErrorCode: -727 Message: DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-204;42704;DBALLO02.BINDINGS_TABLE, DRIVER=4.24.92
2018-09-25 10:09:33,303 WARN  [org.apache.activemq.artemis.jdbc.store.drivers.AbstractJDBCDriver] Can't verify the initialization of table MESSAGE_TABLE due to:
SQL STATEMENTS:
SELECT COUNT(*) FROM MESSAGE_TABLE
SQL EXCEPTIONS:
SQLState: 42704 ErrorCode: -204 Message: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBALLO02.MESSAGE_TABLE, DRIVER=4.24.92
 SQLState: 56098 ErrorCode: -727 Message: DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-204;42704;DBALLO02.MESSAGE_TABLE, DRIVER=4.24.92
2018-09-25 10:09:35,235 INFO  [org.apache.activemq.artemis.core.server] AMQ221034: Waiting indefinitely to obtain live lock
2018-09-25 10:09:35,235 INFO  [org.apache.activemq.artemis.core.server] AMQ221035: Live Server Obtained live lock
2018-09-25 10:09:37,889 INFO  [org.apache.activemq.artemis.core.server] AMQ221080: Deploying address DLQ supporting [ANYCAST]
2018-09-25 10:09:38,737 INFO  [org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue test on address DLQ
2018-09-25 10:09:39,231 INFO  [org.apache.activemq.artemis.core.server] AMQ221080: Deploying address ExpiryQueue supporting [ANYCAST]
2018-09-25 10:09:39,564 INFO  [org.apache.activemq.artemis.core.server] AMQ221003: Deploying ANYCAST queue ExpiryQueue on address ExpiryQueue
2018-09-25 10:09:41,258 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:61616 for protocols [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
2018-09-25 10:09:41,303 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:5445 for protocols [HORNETQ,STOMP]
2018-09-25 10:09:41,338 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:5672 for protocols [AMQP]
2018-09-25 10:09:41,374 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:1883 for protocols [MQTT]
2018-09-25 10:09:41,417 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:61613 for protocols [STOMP]
2018-09-25 10:09:43,936 INFO  [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
2018-09-25 10:09:43,936 INFO  [org.apache.activemq.artemis.core.server] AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.6.3.redhat-00004 [amq-10-37-145-197, nodeID=4f433072-c09a-11e8-ad81-5254007dbf7e]
2018-09-25 10:09:45,129 INFO  [io.hawt.branding.plugin.PluginContextListener] Initialized hawtio-redhat-fuse-branding plugin
2018-09-25 10:09:45,437 INFO  [org.apache.activemq.hawtio.plugin.PluginContextListener] Initialized artemis-plugin plugin
2018-09-25 10:09:46,214 INFO  [org.apache.qpid.dispatch.PluginContextListener] Initialized dispatch-hawtio-console plugin
2018-09-25 10:09:48,652 INFO  [io.hawt.system.ConfigManager] Configuration will be discovered via system properties
2018-09-25 10:09:48,674 INFO  [io.hawt.jmx.JmxTreeWatcher] Welcome to hawtio 1.4.0.redhat-630329 : http://hawt.io/ : Don't cha wish your console was hawt like me? ;-)
2018-09-25 10:09:48,675 INFO  [io.hawt.jmx.UploadManager] Using file upload directory: /home/jamq/ci-cluster-amq7/tmp/uploads
2018-09-25 10:09:48,728 INFO  [io.hawt.web.AuthenticationFilter] Starting hawtio authentication filter, JAAS realm: "activemq" authorized role(s): "amq" role principal classes: "org.apache.activemq.artemis.spi.core.security.jaas.RolePrincipal"
2018-09-25 10:09:48,893 INFO  [io.hawt.web.JolokiaConfiguredAgentServlet] Jolokia overridden property: [key=policyLocation, value=file:/home/jamq/ci-cluster-amq7/etc/jolokia-access.xml]

      Attachments

        Activity

          People

            fnigro Francesco Nigro
            mtoth@redhat.com Michal Toth
            Oleg Sushchenko Oleg Sushchenko
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: