Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 7.7.1.GA
    • Component/s: Cloud, Kie-Server
    • Labels:
      None
    • Environment:

      OpenShift 4.5
      RHBA image rebuild - tag 7.7.1-2
      RHBA Operator 7.7.1
      Upgraded eap in image to version 7.2.9
      AMQ Broker 7.5 (also tested with 7.6)

    • Target Release:
    • Fix Build:
      GA
    • Steps to Reproduce:
      Hide
      1. Preper OpenShift project for deploying 7.7.1 application
      2. Start S2I build with some project and allow AMQ broker (for Operator) or use template with AMQ
      3. Try to communicate with Kie Server through AMQ Broker

      Steps for QE:

      • run test suite and check that tests for AMQ are passing
      Show
      Preper OpenShift project for deploying 7.7.1 application Start S2I build with some project and allow AMQ broker (for Operator) or use template with AMQ Try to communicate with Kie Server through AMQ Broker Steps for QE: run test suite and check that tests for AMQ are passing
    • QE Test Coverage:
      +

      Description

      When is set up environment with Kie Server S2I build using AMQ Broker for JMS communication, then Kie Server client cannot be obtained. This was discovered by QE tests when following exception was thrown in tests:

      java.lang.RuntimeException: Failed to get Kie Server JMS Client.
      	at org.kie.cloud.common.provider.KieServerClientProvider.getKieServerJmsClient(KieServerClientProvider.java:89)
      	at org.kie.cloud.integrationtests.s2i.jms.KieServerS2iAmqDroolsIntegrationTest.setUp(KieServerS2iAmqDroolsIntegrationTest.java:145)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
      	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
      	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
      	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
      	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
      	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
      	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
      	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
      	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
      	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
      	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
      	at org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
      	at org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
      	at org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
      	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
      	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
      	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
      	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
      	at org.junit.runners.Suite.runChild(Suite.java:128)
      	at org.junit.runners.Suite.runChild(Suite.java:27)
      	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
      	at org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      Caused by: java.lang.RuntimeException: java.lang.NullPointerException
      	at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:125)
      	at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:75)
      	at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101)
      	at org.kie.cloud.common.provider.KieServerClientProvider.getKieServerJmsClient(KieServerClientProvider.java:114)
      	at org.kie.cloud.common.provider.KieServerClientProvider.getKieServerJmsClient(KieServerClientProvider.java:87)
      	... 32 more
      Caused by: java.lang.NullPointerException
      	at org.kie.server.client.impl.KieServicesClientImpl.getCapabilitiesFromServer(KieServicesClientImpl.java:140)
      	at org.kie.server.client.impl.KieServicesClientImpl.init(KieServicesClientImpl.java:88)
      	... 36 more
      

      We saw failing tests for Operator and also for Templates.
      In Kie Operator there was no failure regarding the app and whole application was created and ready to use.
      When we try to get the client in Kie Server is following exception:

      15:48:55,755 ERROR [org.jboss.as.ejb3.invocation] (Thread-0 (ActiveMQ-client-global-threads)) WFLYEJB0034: EJB Invocation failed on component KieServerMDB for method public void org.kie.server.jms.KieServerMDB.onMessage(javax.jms.Message): javax.ejb.EJBException: org.kie.server.jms.JMSRuntimeException: Unable to unmarshall request to CommandScript [msg id: 1e17de1d-61cb-44a5-bd87-4a5dcdfe0659].
      

      For more details look into Kie Server log in attached zip file KieServerS2iAmqDroolsIntegrationTest-testContainerAfterExecServerS2IStart[Immutable KIE Server AMQ Database S2I].zip

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  filippe.spolti Filippe Spolti
                  Reporter:
                  jschwan Jakub Schwan
                  Tester:
                  Jakub Schwan
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: