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

cdi-camel-jetty S2I template incorrect default service name, breaking cdi-camel-http

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • Future
    • FIS 1.0 - OpenShift Fuse 3.1-GA
    • FIS-Quickstarts
    • None
    • % %
    • CDI images are deprecated

    Description

      The cdi-camel-http quickstart expects the cdi-camel-jetty service to be named "qs-cdi-camel-jetty".

      In the cdi-camel-jetty template however, the service is named "s2i-qs-cdi-camel-jetty" instead by default.

      This causes the cdi-camel-http to output this error when both are deployed using the S2I with default values

      Caused by: java.net.ConnectException: Connection refused: localhost/127.0.0.1:8080
      	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
      	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
      	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:224)
      	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:281)
      	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)
      	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
      	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
      	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
      	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
      	at java.lang.Thread.run(Thread.java:745)
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            maschmid@redhat.com Marek Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: