Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-1492

JDBC library test stuck on EAP 6/7 and tomcat 7 on Sybase

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JDG 7.2 ER5
    • JDG 7.2 ER2, JDG 7.2 ER3
    • Core
    • None
    • ER5
    • Workaround Exists
    • Hide

      Disable upsert by setting the following property to true on the cache store `infinispan.jdbc.upsert.disabled`

      Show
      Disable upsert by setting the following property to true on the cache store `infinispan.jdbc.upsert.disabled`
    • Hide

      Download and unpack following:
      EAP7 - http://download-node-02.eng.bos.redhat.com/released/JBEAP-7/7.1.0/jboss-eap-7.1.0.zip
      EAP6 - http://download-ipv4.eng.brq.redhat.com/released/JBEAP-6/6.4.16/jboss-eap-6.4.16-full-build.zip
      EWS 3 (includes tomcat7) - http://download-ipv4.eng.brq.redhat.com/released/JBossEWS/3.0.3/jws-application-servers-3.0.3-RHEL6-x86_64.zip
      Driver - http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.1.0/sybase157/jdbc4/jconn4.jar

      Steps:
      1. Clone https://github.com/infinispan/jdg-functional-tests (branch master)
      2. Allocate DBs using this link: http://dballocator.mw.lab.eng.bos.redhat.com:8080/Allocator/AllocatorServlet?operation=allocate&expression=sybase157%26%26geo_BOS&expiry=1440&requestee=GUI (keep open for later reference)
      5. Go to jdg-functional-tests/invm/jdbc-cache-store/
      6. Fill in appropriate values into command and run:

      EAP:
mvn clean verify -U -Dmaven.test.failure.ignore=true -Ddatabase=sybase157 -Ddriver.dir={DRIVER_DIRECTORY} -Ddriver.jar=jconn4.jar -Ddriver.class=com.sybase.jdbc4.jdbc.SybDriver -Dconnection.url={CONNECTION_URL_FROM_DB_ALLOCATOR(do not forget to remove "\")} -Ddb.username={DB_USERNAME} -Ddb.password={DB_PASSWORD} -Dfile.log.level=INFO  {"-Peap" for EAP6, "-Peap7" for EAP7} -Deap.home={EAP_DIRECTORY}

TOMCAT:
mvn clean verify -U -Dmaven.test.failure.ignore=true -Ddatabase=sybase157 -Ddriver.dir={DRIVER_DIRECTORY} -Ddriver.jar=jconn4.jar -Ddriver.class=com.sybase.jdbc4.jdbc.SybDriver -Dconnection.url={CONNECTION_URL_FROM_DB_ALLOCATOR(do not forget to remove "\")} -Ddb.username={DB_USERNAME} -Ddb.password={DB_PASSWORD} -Dfile.log.level=INFO -Ptomcat -Dtomcat.home={TOMCAT_DIRECTORY}
      Show
      Download and unpack following: EAP7 - http://download-node-02.eng.bos.redhat.com/released/JBEAP-7/7.1.0/jboss-eap-7.1.0.zip EAP6 - http://download-ipv4.eng.brq.redhat.com/released/JBEAP-6/6.4.16/jboss-eap-6.4.16-full-build.zip EWS 3 (includes tomcat7) - http://download-ipv4.eng.brq.redhat.com/released/JBossEWS/3.0.3/jws-application-servers-3.0.3-RHEL6-x86_64.zip Driver - http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.1.0/sybase157/jdbc4/jconn4.jar Steps: 1. Clone https://github.com/infinispan/jdg-functional-tests (branch master) 2. Allocate DBs using this link: http://dballocator.mw.lab.eng.bos.redhat.com:8080/Allocator/AllocatorServlet?operation=allocate&expression=sybase157%26%26geo_BOS&expiry=1440&requestee=GUI (keep open for later reference) 5. Go to jdg-functional-tests/invm/jdbc-cache-store/ 6. Fill in appropriate values into command and run: EAP: mvn clean verify -U -Dmaven.test.failure.ignore= true -Ddatabase=sybase157 -Ddriver.dir={DRIVER_DIRECTORY} -Ddriver.jar=jconn4.jar -Ddriver.class=com.sybase.jdbc4.jdbc.SybDriver -Dconnection.url={CONNECTION_URL_FROM_DB_ALLOCATOR( do not forget to remove "\" )} -Ddb.username={DB_USERNAME} -Ddb.password={DB_PASSWORD} -Dfile.log.level=INFO { "-Peap" for EAP6, "-Peap7" for EAP7} -Deap.home={EAP_DIRECTORY} TOMCAT: mvn clean verify -U -Dmaven.test.failure.ignore= true -Ddatabase=sybase157 -Ddriver.dir={DRIVER_DIRECTORY} -Ddriver.jar=jconn4.jar -Ddriver.class=com.sybase.jdbc4.jdbc.SybDriver -Dconnection.url={CONNECTION_URL_FROM_DB_ALLOCATOR( do not forget to remove "\" )} -Ddb.username={DB_USERNAME} -Ddb.password={DB_PASSWORD} -Dfile.log.level=INFO -Ptomcat -Dtomcat.home={TOMCAT_DIRECTORY}

      The jdbc-cachestore test for jdbc library is stuck on EAP6/7 and crashes on tomcat 7. I am unable to determine if this is one and the same bug, however they seem coincidental enough to be addressed simultaneously.

      EAP7/6 and tomcat:
      The test is stuck after PassivateAll is called - "INFO: ISPN000029: Passivating all entries to disk"

      Previous description indicated somewhat different issue on tomcat, but as of ER3 (or due to mistake on my part), the bug is now the same

              remerson@redhat.com Ryan Emerson
              zhostasa_jira Zdenek Hostasa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: