Results 1 to 2 of 2

Thread: Spring batch 2.1.8 jobRepository creation problem

  1. #1
    Join Date
    Jun 2012
    Posts
    16

    Default Spring batch 2.1.8 jobRepository creation problem

    Hi all,

    I am developing batch job using spring batch. The application server is Glassfish 3.1.1 and the database is sybase ASE 15.5 . The JDBC driver file is jconn4.jar. I am using STS 2.9.2 on windows 7 and using java 1.6.31 (64-bit). The application context contains the following codes.

    Code:
        <tx:annotation-driven mode="aspectj" />  
            <jee:jndi-lookup jndi-name="jdbc/sybaseXADatasource"  
                id="dataSource" />  
            <!-- Spring JtaTransactionManager -->  
            <bean id="transactionManager"  
                class="org.springframework.transaction.jta.JtaTransactionManager">  
            </bean>  
            <bean id="entityManagerFactory"  
                class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">  
                <property value="central" name="persistenceUnitName" />  
            </bean>  
          
          
            <!-- Batch Configuration -->  
              
            <batch:job-repository id="jobRepository"  
                data-source="dataSource" transaction-manager="transactionManager"  
                isolation-level-for-create="SERIALIZABLE" table-prefix="BATCH_"  
                max-varchar-length="1000" />

    The JNDI datasource is working file. while deploying the application following error is received.

    Code:
    SEVERE: ContainerBase.addChild: start:   
    org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jobRepository': Invocation of init method failed; nested exception is com.sybase.jdbc4.utils.UnimplementedOperationException: The method com.sybase.jdbc4.jdbc.SybConnectionProxy.public Properties getClientInfo() has not been completed and should not be called.  
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:5389)  
        at com.sun.enterprise.web.WebModule.start(WebModule.java:498)  
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:917)  
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901)  
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:733)  
        at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2000)  
        at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1651)  
        at com.sun.enterprise.web.WebApplication.start(WebApplication.java:109)  
        at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)  
        at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)  
        at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:294)  
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:462)  
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)  
        at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:382)  
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355)  
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370)  
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1064)  
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96)  
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1244)  
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1232)  
        at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:459)  
        at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:209)  
        at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168)  
        at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)  
        at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:238)  
        at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:828)  
        at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:725)  
        at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1019)  
        at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225)  
        at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)  
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)  
        at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)  
        at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)  
        at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)  
        at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)  
        at com.sun.grizzly.ContextTask.run(ContextTask.java:71)  
        at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)  
        at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)  
        at java.lang.Thread.run(Thread.java:662)

    When I change the type 3 JDBC drivers (jconn3.jar) , The codes are working fine.

    It seen that the getClientInfo() method of Type 4 drivers is un-implemented and the jobRepository API depends on it. The JPA used in the application is using Type 4 JDBC, and working fine and wish to continue with same.

    Is it recommended to use the type 3 drivers with ASE 15.x or is there is configuration in spring batch to use the sybase Type 4 drivers.

    Thanks

  2. #2
    Join Date
    Jun 2012
    Posts
    16

    Default

    Can anybody provide me working example of spring jobRepository with sybase ASE 15.7 using JDBC3 type 4 connection
    Thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •