Streamsets Integration to CONNX

, , ,
1

Hi

I am trying to connect a Streamsets pipeline to a VM where CONNX is installed and configured.

The CONNX installed on the VM seems to work as expected, CDD is configured, DSN Registry too for SSCONNX and with Infonaut I can query the data from the table.
I also created an Inbound rule on the VM firewall to open the port 7500.

Now, from Streamset, i m trying to create a JDBC connection as per below with the admin credentials.
jdbc:connx:DD=SSCONNX;GATEWAY=daedcprod01.eur.ad.sag;port=7500

Here i m getting a timeout.

After looking for a long time on what could be the issue on the VM, I found this log CONNXJDBC.LOG

any idea why i get this error?


Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2001(W): CONNX Information Server Version: (4.8).
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2020(W): CONNX Core Version: (14.6.22275).
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): environment setting LANG is not set.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): environment setting LC_ALL is not set.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): Port: 7500.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): DebugLevel: 0.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): DebugVerbose: 0.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): JDBCConnectionPooling: 0.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): JDBCConnectionPoolingTimeout: 300000.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): JDBCParallelConnectionCap: 0.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): Prefetch: 1.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2023(W): SSL: 0.
Mar  6 11:49:58.423 2023@LM_STARTUP@ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2002(W): Server starting to Wait on new Connections.

> Mar  6 11:49:58.423 2023@LM_ERROR  @ UPTIME:(00 00:00:00.0   ) IP:(SERVER         ) TID:(10068     )==> 2008(E): Unable to open acceptor on port: (7500) status: (10048).

Mar  6 12:50:00.945 2023@LM_ERROR  @ UPTIME:(00 01:29:28.999 ) IP:(10.248.141.137 ) TID:(12208     )==>Unusually large or small packet size of 50529027 detected
Mar  6 12:50:00.945 2023@LM_ERROR  @ UPTIME:(00 01:29:28.999 ) IP:(10.248.141.137 ) TID:(12208     )==>
Mar  6 12:50:08.133 2023@LM_ERROR  @ UPTIME:(00 01:29:36.187 ) IP:(10.248.141.137 ) TID:(12208     )==> 2003(E): Receive Problems. Connection Broken. Errno: 0.
Mar  6 12:50:08.133 2023@LM_ERROR  @ UPTIME:(00 01:29:36.187 ) IP:(10.248.141.137 ) TID:(12208     )==> 2003(E): Receive Problems. Connection Broken. Errno: 0.
2

I would recommend first verifying you are able to connect using the CONNX JDBC Sample application. I would also recommend you create a support incident, where we can collect better diagnostics and understand all of your configuration settings. Based on the error it looks like you may have two different things configured to listen to port 7500.

1 Like
3

Hi

The issue was solved by opening the firewall on port 7500 from the Linux VM (where Streamsets container is running) to the windows VM (where CONNX is running. )

1 Like
4

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.