Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-9941

login to ~/jbpm-casemgmt/jbpm-cm.html doesn't work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • 7.61.0.Final
    • KieServer
    • None
    • False
    • False
    • NEW
    • NEW
    • 2021 Week 46-48 (from Nov 15), 2021 Week 49-51 (from Dec 6th)

    Description

      when creating docker community images for server it is not possible to login into:

      http://172.17.0.3:8080/jbpm-casemgmt (link doesn't work yet)

      When trying to login with krisv/krisv it says: Login failed: Not Authorized

      The log says:

      08:06:53,056 INFO [io.jaegertracing.internal.reporters.RemoteReporter] (jaeger.RemoteReporter-QueueProcessor) FlushCommand is working again!
      08:07:03,058 WARN [io.jaegertracing.internal.reporters.RemoteReporter] (jaeger.RemoteReporter-QueueProcessor) FlushCommand execution failed! Repeated errors of this command will not be logged.: io.jaegertracing.internal.exceptions.SenderException: Failed to flush spans.
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.ThriftSender.flush(ThriftSender.java:115)
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.internal.reporters.RemoteReporter$FlushCommand.execute(RemoteReporter.java:160)
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.internal.reporters.RemoteReporter$QueueProcessor.run(RemoteReporter.java:182)
      at java.base/java.lang.Thread.run(Thread.java:834)
      Caused by: io.jaegertracing.internal.exceptions.SenderException: Could not send 1 spans
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.UdpSender.send(UdpSender.java:85)
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.ThriftSender.flush(ThriftSender.java:113)
      ... 3 more
      Caused by: org.apache.thrift.transport.TTransportException: Cannot flush closed transport
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.reporters.protocols.ThriftUdpTransport.flush(ThriftUdpTransport.java:148)
      at org.apache.thrift@0.13.0//org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:73)
      at org.apache.thrift@0.13.0//org.apache.thrift.TServiceClient.sendBaseOneway(TServiceClient.java:66)
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.agent.thrift.Agent$Client.send_emitBatch(Agent.java:70)
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.agent.thrift.Agent$Client.emitBatch(Agent.java:63)
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.UdpSender.send(UdpSender.java:83)
      ... 4 more
      Caused by: java.net.PortUnreachableException: ICMP Port Unreachable
      at java.base/java.net.PlainDatagramSocketImpl.send(Native Method)
      at java.base/java.net.DatagramSocket.send(DatagramSocket.java:695)
      at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.reporters.protocols.ThriftUdpTransport.flush(ThriftUdpTransport.java:146)
      ... 9 more

      Steps to reproduce (you should have docker installed and the daemon running):

      • git clone https://github.com/mbiarnes/business-central.git
      • git checkout v7.61.0.Final
      • git revert 59bc911dbc69b88d165a0aeecbe542ae858d6353 (to revert the last commit that will overwrite IMAGE_TAG="7.61.0.Final" by IMAGE_TAG="latest")
      • cd business-central/server
      •  ./build.sh
      •  ./start.sh
      •  you should get something like :         

      Starting jbpm-server-full docker container using:

        • Container name: jbpm-server-full

      Server starting in 172.17.0.3
      You can access the server root context in http://172.17.0.3:8080
      jBPM Workbench is running at http://172.17.0.3:8080/business-central
      KIE Server Swagger documentation is running at http://172.17.0.3:8080/kie-server/docs
      jBPM Case Management Showcase is running at http://172.17.0.3:8080/jbpm-casemgmt 

       

      Maybe this is due some changes Elytron?

      This is not working yet. We don't have community images for 7.60.0.Final since the Elytron changes weren't working 100%, so it was decided not to create images for this version. Now since we have released version 7.61.0.Final we should create community docker images.

      Attachments

        Activity

          People

            xiabai@redhat.com Xiaofeng Bai
            mbiarnes@redhat.com Michael Biarnes Kiefer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: