Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-16233

Fix quartz cluster datasource configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 6.0
    • Fix Version/s: 6.0-HF03, 7.1
    • Component/s: Core

      Description

      If quartz is configured in cluster mode, it fails to look up its datasource:

      12:17:00,383 ERROR [JNDIConnectionProvider] Error looking up datasource: Name [jdbc/nxquartz_no_tx] is not bound in this Context. Unable to find [jdbc].
javax.naming.NameNotFoundException: Name [jdbc/nxquartz_no_tx] is not bound in this Context. Unable to find [jdbc].
	at org.apache.naming.NamingContext.lookup(NamingContext.java:819)
	at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
	at org.apache.naming.NamingContext.lookup(NamingContext.java:830)
	at org.apache.naming.NamingContext.lookup(NamingContext.java:153)
	at org.apache.naming.NamingContext.lookup(NamingContext.java:830)
	at org.apache.naming.NamingContext.lookup(NamingContext.java:167)
	at org.apache.naming.SelectorContext.lookup(SelectorContext.java:156)
	at javax.naming.InitialContext.lookup(InitialContext.java:411)
	at org.quartz.utils.JNDIConnectionProvider.init(JNDIConnectionProvider.java:124)
	at org.quartz.utils.JNDIConnectionProvider.<init>(JNDIConnectionProvider.java:102)
	at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:969)
	at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1509)
	at org.nuxeo.ecm.core.scheduler.SchedulerServiceImpl.setupScheduler(SchedulerServiceImpl.java:91)
	at org.nuxeo.ecm.core.scheduler.SchedulerServiceImpl.applicationStarted(SchedulerServiceImpl.java:131)

      We should contribute a custom connection provider, which is possible (see PROP_CONNECTION_PROVIDER_CLASS in org.quartz.impl.StdSchedulerFactory.

        Attachments

          Issue Links

          depends on

          Clean up - NXP-13688 JDBC connection should be obtained through a managed datasource

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: