5 Replies Latest reply on Dec 8, 2006 2:02 PM by ankurdotshah

    JBoss 4.0.0 and MySQL as DefaultDS: bug in ejb-deployer.xml

    juergen.zimmermann
    juergen.zimmermann Sep 23, 2004 5:06 AM

      When configuring MySQL 4.1.5 as DefaultDS there are troubles in
      server/default/deploy/ejb-deployer.xml:

      At there is a create table statement having 2 problems

      create table TIMERS (
      TIMERID varchar(50) not null,
      TARGETID varchar(50) not null,
      INITIALDATE timestamp not null,
      INTERVAL bigint,
      INSTANCEPK other,
      INFO other,
      constraint timers_pk primary key (TIMERID)
      )

      1) "INTERVAL" is a reserved keyword
      2) "other" is no valid column type

      • 20023 Views
      • Tags:
        • 2. Re: JBoss 4.0.0 and MySQL as DefaultDS: bug in ejb-deployer.
          ahs1
          ahs1 Sep 23, 2004 6:15 AM (in response to juergen.zimmermann)

          DDL differes a lot from vendor to vendor.

          This entry is to be seen as "adjust according to your specific database".
          This should be documented.

          But the jdbc-implementation does have a problem persisting Timers on MS-SQL databases as the MS-SQL-driver does not implement "setObject" as needed.
          To get this running ther should be an option to use the BLOB-fields (optinally) as binary streams.

            • Actions
          • 3. Re: JBoss 4.0.0 and MySQL as DefaultDS: bug in ejb-deployer.
            lodgemonkey
            lodgemonkey Sep 24, 2004 4:02 PM (in response to juergen.zimmermann)

            I changed my ejb-deployer.xml so that the INTERVAL mySQL key word, was INTERVALS. Then changed the column types from OTHER to BLOB.

            JBoss 4.0 has started and the errors from the EJBTimerService have stopped, but I'm waiting to see if there are any side-effects.

            -R



              • Actions
            • 4. Re: JBoss 4.0.0 and MySQL as DefaultDS: bug in ejb-deployer.
              mat_the_green
              mat_the_green Apr 23, 2006 11:58 AM (in response to juergen.zimmermann)

              I am getting this error when starting JBoss 4.0.3SP1 :
              16:31:51,129 INFO [ServiceConfigurator] Problem configuring service jboss.ejb:service=EJBTimerService,persistencePolicy=database
              org.jboss.deployment.DeploymentException: No Attribute found with name: TableName
              at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:300)
              at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:442)
              at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:153)
              at org.jboss.system.ServiceController.install(ServiceController.java:215)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:585)
              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
              at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
              at $Proxy4.install(Unknown Source)
              at org.jboss.deployment.SARDeployer.create(SARDeployer.java:232)
              at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935)
              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789)
              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:585)
              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
              at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
              at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
              at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
              at $Proxy9.deploy(Unknown Source)
              at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
              at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
              at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
              at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:265)
              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
              at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
              at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:585)
              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
              at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)
              at $Proxy0.start(Unknown Source)
              at org.jboss.system.ServiceController.start(ServiceController.java:428)
              at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:585)
              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
              at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
              at $Proxy4.start(Unknown Source)
              at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
              at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:585)
              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
              at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
              at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
              at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
              at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
              at $Proxy5.deploy(Unknown Source)
              at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
              at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
              at org.jboss.Main.boot(Main.java:187)
              at org.jboss.Main$1.run(Main.java:438)
              at java.lang.Thread.run(Thread.java:595)

              Any ideas on how to fix the problem?

              Cheers
              Mat

                • Actions
              • 5. Re: JBoss 4.0.0 and MySQL as DefaultDS: bug in ejb-deployer.
                ankurdotshah
                ankurdotshah Dec 8, 2006 2:02 PM (in response to juergen.zimmermann)

                So i am having similar problems. The only thing is that i am using jboss v.4.0.1 and in the ejb-deployer.xml there 's no create statement (not sure how the table is created). When i deploy my app. during the creation of timers and hilosequences table, i get an exception.

                  • Actions