Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-6570

BPEL "if" clause, doesn't work properly when using MSSQL (for bpel DB scheme), it dispatches process in a wrong way.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • jboss-fuse-6.2.1, jboss-fuse-6.3
    • SwitchYard
    • None
    • % %
    • Hide

      1. mkdir workspace, cd workspace
      2. git clone -c http.sslverify=false https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-soa/jbossqe-fsw-it.git
      3. git clone -c http.sslverify=false https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-soa/jenkins-jobs.git
      4. open jenkins-jobs ... jobs.yaml file, go to "database-bpel-sy-fuse:"/"database-bpel-sy-eap:" section
      and comment out all rows with databases, except for(e.g): "job.db: mssql2014"
      5. go to jenkins-jobs ... env.properties file and replace all below listed params with:

      1. FUSE:
        job.fuse.url=file:/path/to/karaf_zip/jboss-fuse-karaf-6.3.0.redhat-237.zip
      1. EAP:
        job.eap.fuse.installer.url=/path/to/eap_installer_jar/fuse-eap-installer-6.3.0.redhat-237.jar
        job.eap.url=file:/path/to/eap_zip/jboss-eap-6.4.0.zip
        job.eap.patch.paths=/path/to/eap_patch1/jboss-eap-6.4.9-patch.zip,/path/to/eap_patch2/jboss-eap-6.4.10-patch.zip,/path/to/eap_patch3/jboss-eap-6.4.11-patch.zip

      6. cd workspace
      run:
      #FUSE:
      mvn clean install exec:java -f jenkins-jobs/pom.xml -DuseAlias -Dexec.arguments=database-bpel-sy-fuse
      #EAP:
      mvn clean install exec:java -f jenkins-jobs/pom.xml -DuseAlias -Dexec.arguments=database-bpel-sy-eap

      7. check log.

      Show
      1. mkdir workspace, cd workspace 2. git clone -c http.sslverify=false https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-soa/jbossqe-fsw-it.git 3. git clone -c http.sslverify=false https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-soa/jenkins-jobs.git 4. open jenkins-jobs ... jobs.yaml file, go to "database-bpel-sy-fuse:"/"database-bpel-sy-eap:" section and comment out all rows with databases, except for(e.g): "job.db: mssql2014" 5. go to jenkins-jobs ... env.properties file and replace all below listed params with: FUSE: job.fuse.url= file:/path/to/karaf_zip/jboss-fuse-karaf-6.3.0.redhat-237.zip EAP: job.eap.fuse.installer.url=/path/to/eap_installer_jar/fuse-eap-installer-6.3.0.redhat-237.jar job.eap.url= file:/path/to/eap_zip/jboss-eap-6.4.0.zip job.eap.patch.paths=/path/to/eap_patch1/jboss-eap-6.4.9-patch.zip,/path/to/eap_patch2/jboss-eap-6.4.10-patch.zip,/path/to/eap_patch3/jboss-eap-6.4.11-patch.zip 6. cd workspace run: #FUSE: mvn clean install exec:java -f jenkins-jobs/pom.xml -DuseAlias -Dexec.arguments=database-bpel-sy-fuse #EAP: mvn clean install exec:java -f jenkins-jobs/pom.xml -DuseAlias -Dexec.arguments=database-bpel-sy-eap 7. check log.

    Description

      In jbossqe-fsw-it(see below steps to reproduce)/switchyard/service-implementations/bpel/bpel-error-handler-test, while using MSSQL for BPEL DB scheme, this exception occurs (example):

      Failed tests(see also full log):
      BpelErrorHandlerTest.testSayHelloBeanLocalImplWithEmptyName:128->checkSwitchServiceOn:372->checkSwitchService:381 expected:<...est:1.0}TestService/[SwitchService]Remote> but was:<...est:1.0}TestService/[HelloServiceBpel]Remote>
      BpelErrorHandlerTest.testSayHelloBeanLocalImplWithNonEmptyName:101 expected:<...Service/HelloService[]> but was:<...Service/HelloService[BpelRemote]>
      BpelErrorHandlerTest.testSayHelloBpelRemoteImplWithNonEmptyName:284 expected:<...or_handler_test:1.0}[TestService/HelloServiceBpelRemot]e> but was:<...or_handler_test:1.0}[SwitchServic]e>

      (Test works OK for e.g. MYSQL, POSTGRE db. please note, this test doesn't require bpel-integration-pack. For DB allocation jenkins-jobs(below) uses "DB allocator")

      (1 explanation for example:
      input(request.xml):
      implementation=bean
      local=true
      name=Martin

      should be:
      ...TestService/HelloService...

      was:
      ...TestService/HelloServiceBpelRemote... )

      This error happens irregularly(there is variations of these errors), most of the time for combination: "bean-local" and "bpel-remote"(local=false)

      For bpel file responsible for dispatching see "TestProcess.bpel" in attachment

      I observe this behaviour since 6.2.1 176 and 6.3.0 211, but I'm not sure if it didn't occur earlier as well.

      Attachments

        1. full.log
          196 kB
        2. TestProcess.bpel
          15 kB

        Activity

          People

            tcunning@redhat.com Thomas Cunningham
            sveres@redhat.com Stefan Veres
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: