IOException still happening even after restore driver defaults
See original GitHub issueHi!
I tryed upgrade to the version 3.5.2, but I found this error:
DBException: Error resolving dependencies
java.io.IOException: IOException: Maven artifact 'maven:/net.sourceforge.jtds:jtds:release' not found
I already reset the drivers defaults, restarted DBeaver, but nothing changes.
Issue Analytics
- State:
- Created 8 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
compiler complains unhandled IOException even though ...
The private constructor throws IOException, in static factory function forBus(String busNumber) even though I have throws IOException in ...
Read more >Fix I/O Device Error on External Hard Drive/USB ... - EaseUS
Wait for the driver to be updated, then reboot your computer. Afterward, you can open your device to check whether the I/O error...
Read more >Top 10 Selenium Exceptions and How To Handle These ...
Handling Exceptions in Selenium WebDriver - In this tutorial we will learn about types of exceptions and how to handle top 10 most...
Read more >Bug in c# Driver 2.11.0 - MongoDB
A timeout occured after 30000ms selecting a server using CompositeServerSelector{ Selectors = MongoDB.Driver.MongoClient+ ...
Read more >Fixed: A Device Attached to The System Is Not Functioning
This error means that your computer cannot properly communicate or transfer data with attached device. Thus, you are likely to get this error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Well, let’s use heavy weapons then.
It is definitely not a general solution, just a workaround for the issue I can’t reproduce. Anyhow I’ll add a fix in 3.5.3 which will solve similar problems.
@serge-rider I had the same problem with Hive driver. I deleted the complete block on the xml and then it works for me.