9 Replies Latest reply on Feb 10, 2011 3:15 AM by ellabi

    EJBTimerService error on JBoss5 start up - without applications

    ellabi Newbie

      Hi

      I just starting to use JBoss5 with HSQLDB2.0.1 rc 3. Just installed and configured JBoss and HSQLDB, without any deployment of application.

      This is what I get in the log of server startup:

      16:49:17,405 ERROR [AbstractKernelController] Error installing to Start: name=jboss.ejb:persistencePolicy=database,service=EJBTimerService state=Create mode=Manual requiredState=Installed

      java.sql.SQLException: length must be specified in type definition: VARBINARY

      at org.hsqldb.jdbc.Util.sqlException(Util.java:215)

      at org.hsqldb.jdbc.JDBCStatement.fetchResult(JDBCStatement.java:1826)

      at org.hsqldb.jdbc.JDBCStatement.executeUpdate(JDBCStatement.java:207)

      at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:249)

      at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.createTableIfNotExists(GeneralPurposeDatabasePersistencePlugin.java:175)

      at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:104)

      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)

      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)

      at sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source)

      ...

       

      and then:

      DEPLOYMENTS MISSING DEPENDENCIES:
        Deployment "jboss.ejb:service=EJBTimerService" is missing the following dependencies:
          Dependency "jboss.ejb:persistencePolicy=database,service=EJBTimerService" (should be in state "Create", but is actually in state "**ERROR**")
        DEPLOYMENTS IN ERROR:
        Deployment "jboss.ejb:persistencePolicy=database,service=EJBTimerService" is in error due to the following reason(s): org.hsqldb.HsqlException: length must be specified in type definition: VARBINARY, **ERROR**

       

      Any help would be really appreciated
       

        • 1. EJBTimerService error on JBoss5 start up - without applications
          jaikiran pai Master

          I haven't tried JBoss AS with HSQLDB2. Looks like it now mandates the length for VARBINARY columns. Is upgrading to JBoss AS 6.0.0.Final an option for you? If yes, can you try AS 6.0.0.Final and upgrade HSQLDB to 2.x there? If you still run into same issue on that version, then let us know.

          • 2. EJBTimerService error on JBoss5 start up - without applications
            ellabi Newbie

            The upgarde to version 6.0.0 wasn't helpful... Still the same problem. As I already notice, the version of HSQLDB is 2.0.1, "the latest stable version" - citate from the download page.

            • 3. EJBTimerService error on JBoss5 start up - without applications
              jaikiran pai Master

              Can you please post the new entire exception stacktrace that you see in JBoss AS 6.0.0.Final?

              • 4. Re: EJBTimerService error on JBoss5 start up - without applications
                Nicklas Karlsson Master

                Never tied it but the ".GeneralPurposeDatabasePersistencePlugin" caught my eye. Perhaps it doesn't know  it's a HSQLSB.

                 

                (nevermind, it turns out that there aren't that many other options than Oracle and general)

                 

                Message was edited by: Nicklas Karlsson

                • 5. Re: EJBTimerService error on JBoss5 start up - without applications
                  Nicklas Karlsson Master

                  As a workaround you could try creating the table yourself (create statement can be determined by looking at http://anonsvn.jboss.org/repos/jbossas/trunk/server/src/main/java/org/jboss/ejb/txtimer/GeneralPurposeDatabasePersistencePlugin.java)

                   

                  But it appears to be a bug since later HSQLDB2 versions appear to be stricter about its sizes and the metadata it returns doesn't say so.

                   

                  Mind filing a JIRA against 6.x so it's not forgotten?

                  • 6. EJBTimerService error on JBoss5 start up - without applications
                    ellabi Newbie

                    Thanks for your answers

                    Unfortunately, my comp is generally failed, so now I'm installing it from scratch, and cann't publish more traces or JIRA...

                    Let continue later...

                    • 7. EJBTimerService error on JBoss5 start up - without applications
                      ellabi Newbie

                      Here I'm back. The full log for the version 5 is here:

                      17:02:05,683 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
                      17:02:05,683 INFO  [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)
                      17:02:05,683 INFO  [ServerImpl] Bootstrap URL: null
                      17:02:05,683 INFO  [ServerImpl] Home Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA
                      17:02:05,683 INFO  [ServerImpl] Home URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/
                      17:02:05,683 INFO  [ServerImpl] Library URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/lib/
                      17:02:05,683 INFO  [ServerImpl] Patch URL: null
                      17:02:05,683 INFO  [ServerImpl] Common Base URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/common/
                      17:02:05,699 INFO  [ServerImpl] Common Library URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/common/lib/
                      17:02:05,699 INFO  [ServerImpl] Server Name: default
                      17:02:05,699 INFO  [ServerImpl] Server Base Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server
                      17:02:05,699 INFO  [ServerImpl] Server Base URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/
                      17:02:05,699 INFO  [ServerImpl] Server Config URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/conf/
                      17:02:05,699 INFO  [ServerImpl] Server Home Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server\default
                      17:02:05,699 INFO  [ServerImpl] Server Home URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/
                      17:02:05,699 INFO  [ServerImpl] Server Data Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server\default\data
                      17:02:05,699 INFO  [ServerImpl] Server Library URL: file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/lib/
                      17:02:05,699 INFO  [ServerImpl] Server Log Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server\default\log
                      17:02:05,699 INFO  [ServerImpl] Server Native Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server\default\tmp\native
                      17:02:05,699 INFO  [ServerImpl] Server Temp Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server\default\tmp
                      17:02:05,699 INFO  [ServerImpl] Server Temp Deploy Dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server\default\tmp\deploy
                      17:02:07,462 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/conf/bootstrap.xml
                      17:02:09,350 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
                      17:02:09,366 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
                      17:02:10,147 INFO  [CopyMechanism] VFS temp dir: C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server\default\tmp
                      17:02:10,147 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.
                      17:02:12,752 INFO  [ServerInfo] Java version: 1.6.0_22,Sun Microsystems Inc.
                      17:02:12,752 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
                      17:02:12,752 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 17.1-b03,Sun Microsystems Inc.
                      17:02:12,752 INFO  [ServerInfo] OS-System: Windows 7 6.1,x86
                      17:02:12,847 INFO  [JMXKernel] Legacy JMX core initialized
                      17:02:17,027 INFO  [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@62be97(root=C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
                      17:02:17,027 INFO  [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@62be97(root=C:\jboss-5.0.1.GA-jdk6\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
                      17:02:17,027 INFO  [ProfileServiceImpl] Loaded profile: ProfileImpl@863941{key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default]}
                      17:02:20,460 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/
                      17:02:36,342 INFO  [NativeServerConfig] JBoss Web Services - Stack Native Core
                      17:02:36,358 INFO  [NativeServerConfig] 3.0.5.GA
                      17:03:02,629 INFO  [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
                      17:03:04,081 INFO  [MailService] Mail Service bound to java:/Mail
                      17:03:12,007 WARN  [JBossASSecurityMetadataStore] 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.
                      17:03:12,055 WARN  [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
                      17:03:12,710 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
                      17:03:12,710 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer
                      17:03:13,537 INFO  [TransactionManagerService] Initializing recovery manager
                      17:03:14,099 INFO  [TransactionManagerService] Recovery manager configured
                      17:03:14,099 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
                      17:03:14,177 INFO  [TransactionManagerService] Starting transaction recovery manager
                      17:03:16,049 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
                      17:03:16,065 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
                      17:03:16,065 INFO  [StandardService] Starting service jboss.web
                      17:03:16,081 INFO  [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
                      17:03:17,470 INFO  [Catalina] Server startup in 1608 ms
                      17:03:17,549 INFO  [TomcatDeployment] deploy, ctxPath=/jbossws
                      17:03:20,544 INFO  [TomcatDeployment] deploy, ctxPath=/web-console
                      17:03:21,856 INFO  [TomcatDeployment] deploy, ctxPath=/invoker
                      17:03:22,498 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
                      17:03:22,592 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
                      17:03:22,795 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
                      17:03:22,997 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
                      17:03:23,232 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
                      17:03:23,732 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
                      17:03:23,856 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                      17:03:23,903 INFO  [RAMJobStore] RAMJobStore initialized.
                      17:03:23,903 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
                      17:03:23,903 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                      17:03:23,903 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                      17:03:28,817 INFO  [ENGINE] Checkpoint start
                      17:03:28,990 INFO  [ENGINE] Checkpoint end
                      17:03:29,458 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
                      17:03:30,799 INFO  [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
                      17:03:31,190 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                      17:03:31,190 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1baeacf started
                      17:03:31,393 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                      17:03:31,393 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
                      17:03:31,393 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
                      17:03:31,393 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                      17:03:31,393 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@17f69df started
                      17:03:31,409 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                      17:03:31,409 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1f64d29 started
                      17:03:31,409 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                      17:03:31,549 ERROR [AbstractKernelController] Error installing to Start: name=jboss.ejb:persistencePolicy=database,service=EJBTimerService state=Create mode=Manual requiredState=Installed
                      java.sql.SQLException: length must be specified in type definition: VARBINARY
                      at org.hsqldb.jdbc.Util.sqlException(Util.java:215)
                      at org.hsqldb.jdbc.JDBCStatement.fetchResult(JDBCStatement.java:1826)
                      at org.hsqldb.jdbc.JDBCStatement.executeUpdate(JDBCStatement.java:207)
                      at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:249)
                      at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.createTableIfNotExists(GeneralPurposeDatabasePersistencePlugin.java:175)
                      at org.jboss.ejb.txtimer.DatabasePersistencePolicy.startService(DatabasePersistencePolicy.java:104)
                      at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
                      at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
                      at sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source)
                      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                      at java.lang.reflect.Method.invoke(Method.java:597)
                      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
                      at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
                      at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
                      at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:189)
                      at $Proxy36.start(Unknown Source)
                      at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
                      at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
                      at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
                      at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
                      at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
                      at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
                      at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
                      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
                      at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
                      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
                      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
                      at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
                      at org.jboss.system.ServiceController.start(ServiceController.java:460)
                      at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
                      at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
                      at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
                      at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
                      at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
                      at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
                      at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
                      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
                      at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
                      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
                      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
                      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
                      at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
                      at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
                      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
                      at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
                      at org.jboss.Main.boot(Main.java:209)
                      at org.jboss.Main$1.run(Main.java:547)
                      at java.lang.Thread.run(Thread.java:662)
                      Caused by: org.hsqldb.HsqlException: length must be specified in type definition: VARBINARY
                      at org.hsqldb.error.Error.error(Error.java:77)
                      at org.hsqldb.ParserDQL.readTypeDefinition(ParserDQL.java:265)
                      at org.hsqldb.ParserDDL.readColumnDefinitionOrNull(ParserDDL.java:2290)
                      at org.hsqldb.ParserDDL.compileCreateTableBody(ParserDDL.java:967)
                      at org.hsqldb.ParserDDL.compileCreateTable(ParserDDL.java:882)
                      at org.hsqldb.ParserDDL.compileCreate(ParserDDL.java:151)
                      at org.hsqldb.ParserCommand.compilePart(ParserCommand.java:206)
                      at org.hsqldb.ParserCommand.compileStatements(ParserCommand.java:88)
                      at org.hsqldb.Session.executeDirectStatement(Session.java:1177)
                      at org.hsqldb.Session.execute(Session.java:976)
                      at org.hsqldb.jdbc.JDBCStatement.fetchResult(JDBCStatement.java:1818)
                      ... 56 more
                      17:03:31,939 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
                      17:03:32,003 INFO  [TomcatDeployment] deploy, ctxPath=/
                      17:03:32,330 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console
                      17:03:32,627 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                      DEPLOYMENTS MISSING DEPENDENCIES:
                        Deployment "jboss.ejb:service=EJBTimerService" is missing the following dependencies:
                          Dependency "jboss.ejb:persistencePolicy=database,service=EJBTimerService" (should be in state "Create", but is actually in state "**ERROR**")

                      DEPLOYMENTS IN ERROR:
                        Deployment "jboss.ejb:persistencePolicy=database,service=EJBTimerService" is in error due to the following reason(s): org.hsqldb.HsqlException: length must be specified in type definition: VARBINARY, **ERROR**

                      17:03:32,673 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
                      17:03:32,939 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                      17:03:32,970 INFO  [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 1m:27s:256ms

                       

                      And after manual creation of TIMERS table, it started up fine.

                      • 8. Re: EJBTimerService error on JBoss5 start up - without applications
                        jaikiran pai Master

                        Can you try this:

                         

                        - Open the JBOSS_HOME/server/< servername>/conf/standardjbosscmp-jdbc.xml in a text editor

                        - Search for the "Hypersonic SQL" type-mappping in that file. It will look something like this:

                         

                        <type-mapping>
                                 <name>Hypersonic SQL</name>
                                 <row-locking-template/>
                                 ...
                        
                        
                        
                                 <mapping>
                                    <java-type>java.lang.Object</java-type>
                                    <!-- hsqldb only supports directly serializable objects for sql type OBJECT -->
                                    <jdbc-type>VARBINARY</jdbc-type>
                                    <sql-type>VARBINARY</sql-type>
                                 </mapping>
                        ...
                        
                              </type-mapping>
                        

                         

                        Try changing it to:

                         

                        <type-mapping>
                                 <name>Hypersonic SQL</name>
                                 <row-locking-template/>
                                 ...
                        
                        
                        
                                 <mapping>
                                    <java-type>java.lang.Object</java-type>
                                    <!-- hsqldb only supports directly serializable objects for sql type OBJECT -->
                                    <jdbc-type>VARBINARY</jdbc-type>
                                    <sql-type>VARBINARY(1024)</sql-type>
                                 </mapping>
                        ...
                        
                              </type-mapping>
                        

                         

                        See the change in the sql-type value. I set the length randomly to 1024.

                         

                        After this change, restart the server and see if it works.

                        • 9. EJBTimerService error on JBoss5 start up - without applications
                          ellabi Newbie

                          Thank you very much - this is the answer for all my troubles (limited to JBoss and the current moment)