Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-4630

Not able to build project from BC which is deployed in OCP env

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • None
    • Business Central, Cloud, Kie-Server
    • None
    • False
    • None
    • False
    • ---
    • ---

    Description

       

      Issue1:  Customer is not able to build project from BC console 

      Project build is  failing with below error:

       

      ==========

      ERROR [org.kie.workbench.common.services.backend.builder.core.BuildHelper] (default task-17) org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.default:artifact:jar:1.0.0: java.lang.RuntimeException: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.default:artifact:jar:1.0.0

          at deployment.ROOT.war//org.appformer.maven.integration.MavenRepository.getArtifactDependecies(MavenRepository.java:128)

      . . . .

      Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.default:artifact:pom:1.0.0 from/to central (https://repo1.maven.org/maven2/): repo1.maven.org

          ...

      Caused by: java.net.UnknownHostException: repo1.maven.org

          at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:797)

      ==========

      Please refer to BC pod logs(rhpamdev-rhpamcentr-42-s5l24-rhpamdev-rhpamcentr (1).log) for more details.

       

      Assuming its issue with proxy, I asked customer to access repo1.maven.org through curl command from BC pod, but its working fine. Here is the output of curl command:

      ~~~

       curl -v -s -w 'Establish Connection: %{time_connect}s\nTTFB: %{time_starttransfer}s\nTotal: %{time_total}s\n'  https://repo1.maven.org/maven2/org/default -x 10.11.12.9:8080

      <html>

      <head><title>404 Not Found</title></head>

      <body bgcolor="white">

      <center><h1>404 Not Found</h1></center>

      <hr><center>nginx</center>

      </body>

      </html>

      <!-- a padding to disable MSIE and Chrome friendly error page -->

      <!-- a padding to disable MSIE and Chrome friendly error page -->

      <!-- a padding to disable MSIE and Chrome friendly error page -->

      <!-- a padding to disable MSIE and Chrome friendly error page -->

      <!-- a padding to disable MSIE and Chrome friendly error page -->

      <!-- a padding to disable MSIE and Chrome friendly error page -->

      Establish Connection: 0.023931s

      TTFB: 0.833674s

      Total: 0.833805s

      ~~~

      Output of curl command attached(curl_output_22ndDec.txt)

      To bypass the connectivity issue with the maven repository I tried using 'kie.maven.offline.force=true' option but somehow pod is getting killed.

      Below files captured at the time of issue:

          events_22ndDec.txt 

          rhpamdev-rhpamcentr-46-p5p4s-rhpamdev-rhpamcentr_(1).log 

          kieapp yml(kieapp-rhpamdev (11).yaml)

        Issue2 : Customer is not able to deploy kjar(build using maven command) on kie-server pod

      Also, we tried to deploy kjar on kie-server pod but pod is getting terminated due to probe failue(initialDelaySeconds set tp 1000 secs). In the captured thread dump as well we can see thread is trying to resolve dependencies

       

      =================

      "ServerService Thread Pool – 83" #138 prio=5 os_prio=0 cpu=5507.74ms elapsed=246.33s tid=0x000055a5d266d000 nid=0x690 runnable  [0x00007f8de4336000]

         java.lang.Thread.State: RUNNABLE

          at java.net.SocketInputStream.socketRead0(java.base@11.0.17/Native Method)

          at java.net.SocketInputStream.socketRead(java.base@11.0.17/SocketInputStream.java:115)

          at java.net.SocketInputStream.read(java.base@11.0.17/SocketInputStream.java:168)

          at java.net.SocketInputStream.read(java.base@11.0.17/SocketInputStream.java:140)

          at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:161)

          at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:82)

          at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:276)

          at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138)

          at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)

          at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)

          at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:294)

          at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:257)

          at org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:207)

          at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)

          at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)

          at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:679)

          at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:481)

          at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:836)

          at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)

          at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)

          at org.apache.http.impl.client.DecompressingHttpClient.execute(DecompressingHttpClient.java:164)

          at org.eclipse.aether.transport.http.HttpTransporter.execute(HttpTransporter.java:318)

          at org.eclipse.aether.transport.http.HttpTransporter.implGet(HttpTransporter.java:274)

          at org.eclipse.aether.spi.connector.transport.AbstractTransporter.get(AbstractTransporter.java:59)

          at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)

          at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)

          at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)

          at org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)

          at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)

          at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)

          at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)

          at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)

          at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)

          at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)

          at org.appformer.maven.integration.MavenRepository.resolveArtifact(MavenRepository.java:179)

          at org.appformer.maven.integration.MavenRepository.resolveArtifact(MavenRepository.java:157)

          at org.appformer.maven.integration.MavenRepository.resolveArtifact(MavenRepository.java:153)

          at org.appformer.maven.integration.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:50)

          at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:116)

          at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:112)

          - locked <0x00000000df78a0e0> (a org.kie.scanner.KieRepositoryScannerImpl)

          at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:192)

          at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:138)

          at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:115)

          at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:188)

          at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:180)

      =================

       

      It seems like kie-server pod is also not able to connect to maven repo through proxy. In kie-server settings.xml BC maven repo is configured:

      =================

       <server>

             <id>guvnor-m2-repo</id>

             <username>bpmsAdmin</username>                       

             <password>admin12@</password>    

      </server>

       

      ... .

      <repository>

        <id>guvnor-m2-repo</id>

        <url>http://rhpamdev-rhpamcentr:8080/maven2/</url>         

        <releases>

          <enabled>true</enabled>

        </releases>

        <snapshots>

          <enabled>true</enabled>

        </snapshots>

      </repository>

      =================

      Attaching complete thread dump for review. 

       

      Issue: 

        Customer is not able to build project from BC console 

        Customer is not able to deploy kjar(build using maven command) on kie-server pod

      Attachments

        Activity

          People

            rhn-support-fspolti Filippe Spolti
            rhn-support-abhumbe Abhijit Humbe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: