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

Port in SQL Kamelet overriden when used with InMemoryChannel source

    XMLWordPrintable

Details

    • Bug
    • Status: Done
    • Blocker
    • Resolution: Done
    • Camel-K-GA
    • Camel-K-GA
    • Camel-K
    • None
      1. deploy the operator
      2. deploy the attached reproducer file
      3. observe the log of inmem-to-mariadb-sink pod
    • ?
    • In progress

    Description

      When the SQL sink kamelets (tried with mariadb and sqlserver) are used in a KameletBinding with InMemoryChannel source, the port property is set to 8080 on the sink, which causes database connections to fail.

       

      Specifiyng the port explicitely does not help either.

       

      What did help was editing the kamelet itself and changing the name of the property to e.g. mariadbPort. Seems like the kamelet is picking up a property set by something else in the route.

       

      Here's the errors:

      Caused by: java.sql.SQLNonTransientConnectionException: Could not connect to address=(host=mariadb-tnb)(port=8080)(type=master) : Socket fail to connect to host:mariadb-tnb, port:8080. No route to host (Host unreachable)
       
      Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host mssql-tnb, port 8080 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
      

      Attachments

        Activity

          People

            nicolaferraro Nicola Ferraro
            asmigala@redhat.com Andrej Smigala
            Andrej Smigala Andrej Smigala
            Heiko Braun
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: