2 Replies Latest reply on Apr 4, 2008 11:22 AM by peterj

    Problem with JBoss 5.0beta4 : [QuartzTimerServiceFactory] sq

    rajeevdr

      Hi,
      I am a newbie in EJB3. When I am trying to start JBoss-5.0.0.Beta4, I am getting the below error. I am unable to run the EJB3 application because of this. Could anybody please assist me. I have not changed anything in the extracted directories.

      16:20:57,234 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE qrtz_job_details(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL, DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1) NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))

      The complete log is provided below.
      16:20:17,078 INFO [ServerImpl] Starting JBoss (Microcontainer)...
      16:20:17,125 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200802091115)
      16:20:17,125 INFO [ServerImpl] Home Dir: C:\Eclipse3.3\jboss-5.0.4
      16:20:17,125 INFO [ServerImpl] Home URL: file:/C:/Eclipse3.3/jboss-5.0.4/
      16:20:17,125 INFO [ServerImpl] Library URL: file:/C:/Eclipse3.3/jboss-5.0.4/lib/
      16:20:17,140 INFO [ServerImpl] Patch URL: null
      16:20:17,140 INFO [ServerImpl] Server Name: default
      16:20:17,140 INFO [ServerImpl] Server Home Dir: C:\Eclipse3.3\jboss-5.0.4\server\default
      16:20:17,140 INFO [ServerImpl] Server Home URL: file:/C:/Eclipse3.3/jboss-5.0.4/server/default/
      16:20:17,140 INFO [ServerImpl] Server Data Dir: C:\Eclipse3.3\jboss-5.0.4\server\default\data
      16:20:17,140 INFO [ServerImpl] Server Temp Dir: C:\Eclipse3.3\jboss-5.0.4\server\default\tmp
      16:20:17,140 INFO [ServerImpl] Server Config URL: file:/C:/Eclipse3.3/jboss-5.0.4/server/default/conf/
      16:20:17,140 INFO [ServerImpl] Server Library URL: file:/C:/Eclipse3.3/jboss-5.0.4/server/default/lib/
      16:20:17,140 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
      16:20:17,546 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Eclipse3.3/jboss-5.0.4/server/default/conf/bootstrap-beans.xml
      16:20:18,828 INFO [ProfileImpl] Using profile root:C:\Eclipse3.3\jboss-5.0.4\server\default
      16:20:19,343 INFO [ServerInfo] Java version: 1.5.0_15,Sun Microsystems Inc.
      16:20:19,343 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_15-b04,Sun Microsystems Inc.
      16:20:19,343 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      16:20:19,453 INFO [JMXKernel] Legacy JMX core initialized
      16:20:24,281 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      16:20:25,218 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      16:20:25,218 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      16:20:25,718 INFO [TransactionManagerService] Starting recovery manager
      16:20:25,968 INFO [TransactionManagerService] Recovery manager started
      16:20:25,968 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      16:20:54,734 INFO [AspectDeployer] Deploying xml into org.jboss.aop.AspectManager@1aedcb3 for BaseClassLoader@5d50c4{vfsfile:/C:/Eclipse3.3/jboss-5.0.4/server/default/deploy/ejb3-interceptors-aop.xml}
      16:20:56,906 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Eclipse3.3/jboss-5.0.4/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
      16:20:56,906 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Eclipse3.3/jboss-5.0.4/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
      16:20:56,984 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      16:20:57,234 WARN [QuartzTimerServiceFactory] sql failed: CREATE TABLE qrtz_job_details(JOB_NAME VARCHAR(80) NOT NULL, JOB_GROUP VARCHAR(80) NOT NULL, DESCRIPTION VARCHAR(120) NULL, JOB_CLASS_NAME VARCHAR(128) NOT NULL, IS_DURABLE VARCHAR(1) NOT NULL, IS_VOLATILE VARCHAR(1) NOT NULL, IS_STATEFUL VARCHAR(1) NOT NULL, REQUESTS_RECOVERY VARCHAR(1) NOT NULL, JOB_DATA BINARY NULL, PRIMARY KEY (JOB_NAME,JOB_GROUP))
      16:20:58,062 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      16:20:58,125 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      16:20:58,125 INFO [JobStoreCMT] Using db table-based data access locking (synchronization).
      16:20:58,171 INFO [JobStoreCMT] Removed 0 Volatile Trigger(s).
      16:20:58,171 INFO [JobStoreCMT] Removed 0 Volatile Job(s).
      16:20:58,171 INFO [JobStoreCMT] JobStoreCMT initialized.
      16:20:58,171 INFO [StdSchedulerFactory] Quartz scheduler 'JBossEJB3QuartzScheduler' initialized from an externally provided properties instance.
      16:20:58,171 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      16:20:58,187 INFO [JobStoreCMT] Freed 0 triggers from 'acquired' / 'blocked' state.
      16:20:58,187 INFO [JobStoreCMT] Recovering 0 jobs that were in-progress at the time of the last shut-down.
      16:20:58,187 INFO [JobStoreCMT] Recovery complete.
      16:20:58,187 INFO [JobStoreCMT] Removed 0 'complete' triggers.
      16:20:58,187 INFO [JobStoreCMT] Removed 0 stale fired job entries.
      16:20:58,187 INFO [QuartzScheduler] Scheduler JBossEJB3QuartzScheduler_$_NON_CLUSTERED started.
      16:21:00,734 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre1.5.0_15\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Java\jre1.5.0_15\bin\client;C:\Program Files\Java\jre1.5.0_15\bin;C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IBM\Infoprint Select;C:\Notes;C:\Program Files\XLView;C:\lotus\compnent;C:\Utilities;C:\Program Files\IBM\Personal Communications\;C:\Program Files\IBM\Trace Facility\;C:\Program Files\Intel\Wireless\Bin\;C:\Program Files\ThinkPad\ConnectUtilities;C:\WINDOWS\Downloaded Program Files;C:\IBMTOOLS\Python22;C:\Program Files\Java\jdk1.6.0_01;C:\Program Files\Java\jdk1.6.0_01\bin;C:\Program Files\Java\jdk1.6.0_01\lib;C:\Sun\SDK\bin;C:\Sun\SDK\jdk\bin;C:\Sun\SDK\jdk\lib;C:\Sun\SDK\jdk\jre\bin;C:\Sun\SDK\jdk\jre\lib;C:\Sun\SDK\bin;C:\Sun\SDK\lib
      16:21:01,000 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
      16:21:01,015 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
      16:21:01,015 INFO [Catalina] Initialization processed in 1641 ms
      16:21:01,015 INFO [StandardService] Starting service jboss.web
      16:21:01,015 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.0.CR12
      16:21:01,187 INFO [Catalina] Server startup in 171 ms
      16:21:01,218 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war
      16:21:04,500 INFO [NativeServerConfig] JBoss Web Services - Native
      16:21:04,500 INFO [NativeServerConfig] jbossws-native-2.0.3.GA (build=200801241020)
      16:21:07,046 INFO [TomcatDeployment] deploy, ctxPath=/jbossws, vfsUrl=jbossws.sar/jbossws-context.war
      16:21:07,250 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Eclipse3.3/jboss-5.0.4/server/default/deploy/jms-ra.rar/META-INF/ra.xml
      16:21:07,390 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
      16:21:09,203 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
      16:21:09,250 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Eclipse3.3/jboss-5.0.4/server/default/deploy/mail-ra.rar/META-INF/ra.xml
      16:21:09,468 INFO [MailService] Mail Service bound to java:/Mail
      16:21:09,812 INFO [TomcatDeployment] deploy, ctxPath=/web-console, vfsUrl=management/console-mgr.sar/web-console.war
      16:21:12,000 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
      16:21:12,625 INFO [ServerPeer] JBoss Messaging 1.4.1.Beta1 server [0] started
      16:21:12,859 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      16:21:13,234 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      16:21:13,234 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@300ca7 started
      16:21:13,234 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      16:21:13,250 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      16:21:13,250 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1eee6b2 started
      16:21:13,250 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
      16:21:13,250 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
      16:21:13,265 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
      16:21:13,265 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@618ac5 started
      16:21:13,265 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      16:21:13,328 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/Eclipse3.3/jboss-5.0.4/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
      16:21:13,390 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      16:21:13,390 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      16:21:13,390 INFO [RAMJobStore] RAMJobStore initialized.
      16:21:13,390 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
      16:21:13,390 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      16:21:13,390 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      16:21:13,421 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
      16:21:14,265 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
      16:21:14,421 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      16:21:14,421 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta4 (build: SVNTag=JBoss_5_0_0_Beta4 date=200802091115)] Started in 57s:281ms
      ________________________________________________
      Thanks & Regards,
      Rajeev R.

        • 1. Re: Problem with JBoss 5.0beta4 : [QuartzTimerServiceFactory
          jaikiran

          That looks like a WARN message.

          I am unable to run the EJB3 application because of this


          In the logs, i don't see your application being deployed. How are you deploying the application? And what exactly do you mean by "unable to run EJB3 application"

          • 2. Re: Problem with JBoss 5.0beta4 : [QuartzTimerServiceFactory
            peterj

            JBossAS 5.0.0Beta4 is a little picky about how things get deployed (that is a kind way of saying that deployment in beta4 is very screwed up). In most cases, I have to start the app server first, and then deploy the EJB. If I place the EJB archive in the deploy directory and then start the app server, the EJB will typically not deploy correctly.

            Are you starting jbossas inside eclipse? That is just adding another level of confusion. Search the forums for other posts related to beta4 and eclipse.