You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing a pipeline that reads data from a rest api and saves it to a mssql server database. The connection to the database is via VPN. By opening a "Database Lookup" step the GUI freezes and I have to wait about ten seconds before I can do anything. Every change made in the detail screen causes another GUI crash. In the Hop console I always get the same error: "Error in the Hop GUI: Failed to execute runnable..."
Issue Priority
Priority: 2
Issue Component
Component: Transforms
The text was updated successfully, but these errors were encountered:
Does the connection work in Hop over VPN?
The stack trace seems to indicate that it wants to fetch metadata from the database but it can't connect to it.
Hi Has,
when the GUI becomes responsive again I launch the transformation and it proceeds smoothly quickly, then the connection to the db actually works. I don't understand why it goes haywire in the editing screen. I indicated the "Database Lookup" step, but it happens with every step involving the db of course.
Code needs hardening for when the database driver loses connection and give back a null for the row metadata (fields).
It's probably a timeout or something like that, which is causing the connection drop.
Apache Hop version?
2.6.0
Java version?
11.0.17
Operating system
Windows
What happened?
I'm developing a pipeline that reads data from a rest api and saves it to a mssql server database. The connection to the database is via VPN. By opening a "Database Lookup" step the GUI freezes and I have to wait about ten seconds before I can do anything. Every change made in the detail screen causes another GUI crash. In the Hop console I always get the same error: "Error in the Hop GUI: Failed to execute runnable..."
Issue Priority
Priority: 2
Issue Component
Component: Transforms
The text was updated successfully, but these errors were encountered: