[Logo] Terracotta Discussion Forums
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
[Expert]
Quartz Manager configuration and setup  XML
Forum Index -> Quartz
Author Message
cedar715

neo

Joined: 08/02/2011 05:55:57
Messages: 2
Offline

Hi,

I am a newbie learning Quartz for a POC. I have the trial version of Quartz manager and I am trying to get it running but unable to get pass the initial connection setup screen. Looks like I am missing something but am unable to figure out the issue.
When I try to create a new connection with my host IP and 1099 as port (without any username/passwd as they are not set as jmx properties) I am getting error "Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: jmxrmi"

Please let me know where/what is the issue.

Here is my Quartz.properties:

# Configure Main Scheduler Properties
#======================================
org.quartz.scheduler.instanceName = SampleDBJobScheduler
org.quartz.scheduler.instanceId = AUTO

org.quartz.scheduler.rmi.export: true
org.quartz.scheduler.rmi.registryHost: XX.XXX.XXX.XXX
org.quartz.scheduler.rmi.registryPort: 1099
org.quartz.scheduler.rmi.createRegistry: true

# Enable JMX features
org.quartz.scheduler.jmx.export = true
org.quartz.scheduler.jmx.objectName = quartz:type=SampleDBJobScheduler,name=JmxScheduler, instanceId=NONE_CLUSTER


org.quartz.scheduler.skipUpdateCheck: true
#======================================
# Configure ThreadPool
#======================================
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 25
org.quartz.threadPool.threadPriority = 5
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = true
#======================================
# Configure JobStore
#======================================
org.quartz.jobStore.misfireThreshold = 60000
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.jobStore.useProperties = false
org.quartz.jobStore.dataSource = myDS
org.quartz.jobStore.tablePrefix = qrtz_
org.quartz.jobStore.isClustered = false
org.quartz.jobStore.clusterCheckinInterval = 20000
#======================================
# Configure Datasources
#======================================
org.quartz.dataSource.myDS.driver = oracle.jdbc.driver.OracleDriver
org.quartz.dataSource.myDS.URL =jdbc:oracle:thin:@(DESCRIPTION=myDatabase_details...)
org.quartz.dataSource.myDS.user = username
org.quartz.dataSource.myDS.password = passwd
org.quartz.dataSource.myDS.maxConnections = 20


Here is the console output when I start my scheduler:

[INFO] 02 Aug 06:13:57.149 PM main [com.mchange.v2.log.MLog]
MLog clients using log4j logging.

[INFO] 02 Aug 06:13:57.258 PM main [com.mchange.v2.c3p0.C3P0Registry]
Initializing c3p0-0.9.1.1 [built 15-March-2007 01:32:31; debug? true; trace: 10]

[INFO] 02 Aug 06:13:57.290 PM main [org.quartz.impl.StdSchedulerFactory]
Using default implementation for ThreadExecutor

[INFO] 02 Aug 06:13:57.290 PM main [org.quartz.simpl.SimpleThreadPool]
Job execution threads will use class loader of thread: main

[INFO] 02 Aug 06:13:57.305 PM main [org.quartz.core.SchedulerSignalerImpl]
Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

[INFO] 02 Aug 06:13:57.305 PM main [org.quartz.core.QuartzScheduler]
Quartz Scheduler v.2.0.2 created.

[INFO] 02 Aug 06:13:57.305 PM main [org.quartz.impl.jdbcjobstore.JobStoreTX]
Using thread monitor-based data access locking (synchronization).

[INFO] 02 Aug 06:13:57.305 PM main [org.quartz.impl.jdbcjobstore.JobStoreTX]
JobStoreTX initialized.

[INFO] 02 Aug 06:13:58.477 PM main [org.quartz.core.QuartzScheduler]
Scheduler bound to RMI registry under name 'SampleDBJobScheduler_$_NON_CLUSTERED'

[INFO] 02 Aug 06:13:58.477 PM main [org.quartz.core.QuartzScheduler]
Scheduler meta-data: Quartz Scheduler (v2.0.2) 'SampleDBJobScheduler' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - access via RMI.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 25 threads.
Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreTX' - which supports persistence. and is not clustered.


[INFO] 02 Aug 06:13:58.477 PM main [org.quartz.impl.StdSchedulerFactory]
Quartz scheduler 'SampleDBJobScheduler' initialized from default file in current working dir: 'quartz.properties'

[INFO] 02 Aug 06:13:58.508 PM main [org.quartz.impl.StdSchedulerFactory]
Quartz scheduler version: 2.0.2

[INFO] 02 Aug 06:13:58.524 PM main [com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource]
Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName -> 2x7kv98h12fnn24kx0shu|4741d6, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> oracle.jdbc.driver.OracleDriver, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 2x7kv98h12fnn24kx0shu|4741d6, idleConnectionTestPeriod -> 50, initialPoolSize -> 3, lastAcquisitionFailureDefaultUser -> null, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 20, maxStatements -> 0, maxStatementsPerConnection -> 120, minPoolSize -> 1, numHelperThreads -> 3, numThreadsAwaitingCheckoutDefaultUser -> 0, properties -> {user=******, password=******}, propertyCycle -> 0, testConnectionOnCheckin -> true, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false ]

[INFO] 02 Aug 06:13:59.821 PM main [org.quartz.impl.jdbcjobstore.JobStoreTX]
Freed 0 triggers from 'acquired' / 'blocked' state.

[INFO] 02 Aug 06:13:59.883 PM main [org.quartz.impl.jdbcjobstore.JobStoreTX]
Recovering 0 jobs that were in-progress at the time of the last shut-down.

[INFO] 02 Aug 06:13:59.883 PM main [org.quartz.impl.jdbcjobstore.JobStoreTX]
Recovery complete.

[INFO] 02 Aug 06:13:59.883 PM main [org.quartz.impl.jdbcjobstore.JobStoreTX]
Removed 0 'complete' triggers.

[INFO] 02 Aug 06:13:59.899 PM main [org.quartz.impl.jdbcjobstore.JobStoreTX]
Removed 0 stale fired job entries.

[INFO] 02 Aug 06:13:59.899 PM main [org.quartz.core.QuartzScheduler]
Scheduler SampleDBJobScheduler_$_NON_CLUSTERED started.

Thanks,
S.
rajoshi

seraphim

Joined: 07/04/2011 04:36:10
Messages: 1465
Offline

Hi,

I think there is some issue with your configuration.
Try this one in Enabling JMX features:

org.quartz.scheduler.jmx.objectName = quartz:type=QuartzScheduler,name=SampleDBJobScheduler, instanceId=NONE_CLUSTER .

Rakesh Joshi
Terracotta.
cedar715

neo

Joined: 08/02/2011 05:55:57
Messages: 2
Offline

Hi,

Thanks for your reply.

I tried with the changes you mentioned and got this exception -

Failed to retrieve RMIServer stub: javax.naming.ConfigurationException [Root exception is java.rmi.UnknownHostException: Unknown host: SampleDBJobScheduler; nested exception is:
java.net.UnknownHostException: SampleDBJobScheduler]

Any inputs will be very helpful.

Thanks,
S
gkeim

ophanim

Joined: 12/05/2006 10:22:37
Messages: 685
Location: Terracotta, Inc.
Offline

Did you run your application with the following settings?

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=1099
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Also, I would recommend you not override the jmx.objectName.

I'm not sure how rmi.registryPort interacts with the jmxremote.port... you may need to change one of them.

Gary Keim (terracotta developer) Want to post to this forum? Join the Terracotta Community
jpmorgan

neo

Joined: 02/29/2012 09:17:51
Messages: 5
Offline

Hi,

Can you let me know if your issue get fixed? I also have the similar issue. I installed the Quartz Scheduler into JBoss and configure for JMX access. Then try to use Quartz Manager to manage it. Unfortunately, it never succeeds.

Please the following link for more detail.

I just feel that this Quartz Manager is not a good product as it is very difficult to setup without any documentation support.

If you have any clue how to fix it, please help.

http://forums.terracotta.org/forums/posts/list/6728.page


Thanks
Benson
 
Forum Index -> Quartz
Go to:   
Powered by JForum 2.1.7 © JForum Team