Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-23510

[GSS](7.4.z) NPE when EJB Database Timer Persistence adjustCreateAutoTimerStatement is called

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.4.6.CR1, 7.4.6.GA
    • 7.4.4.GA
    • EJB
    • None
    • False
    • None
    • False
    • +
    • Hide

      remove the database="oracle" (or other database), and it will check the metadata of the database connection to try to determine the database.  

      Show
      remove the database="oracle" (or other database), and it will check the metadata of the database connection to try to determine the database.  

    Description

      When setting the 'database' to db2 or oracle 

                  <timer-service thread-pool-name="default" default-data-store="store">
                <data-stores>
                    <database-data-store name="store" database="oracle" datasource-jndi-name="java:jboss/datasources/ExampleDS" partition="ejb_timer_part" refresh-interval="30000"/>
                </data-stores>
            </timer-service>

      A null pointer exception occurs:

      10:55:20,905 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.ejb3.timer-service.timer-persistence-service.store: org.jboss.msc.service.StartException in service org.wildfly.ejb3.timer-service.timer-persistence-service.store: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.adjustCreateAutoTimerStatement(DatabaseTimerPersistence.java:323)
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.identifyDialect(DatabaseTimerPersistence.java:311)
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.investigateDialect(DatabaseTimerPersistence.java:280)
at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.start(DatabaseTimerPersistence.java:187)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
... 6 more

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. WFLY-16290 NPE when EJB Database Timer Persistence adjustCreateAutoTimerStatement is called

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-22995 [GSS](7.4.z) WFLY-15569 - Database persistent auto timer are created twice

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. JBEAP-23974 [QE](7.4.z) WFLY-16290 - Test-case - NPE when EJB Database Timer Persistence adjustCreateAutoTimerStatement is called

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              rhn-support-bmaxwell Brad Maxwell
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: