This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Database Application Shell problem | ||
---|---|---|---|
Product: | javaee | Reporter: | neil_hawkes <neil_hawkes> |
Component: | Persistence | Assignee: | Sergey Petrov <sj-nb> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
neil_hawkes
2009-08-17 00:02:29 UTC
Seems like problem in network, do you connect to the db on local machine or remotely? Hi jiriprox - thanks for your time. Remotely. I have tested a login using local authentication on the server by using it with two other SQL report tools and that works OK. Using that login creates a connection OK and that connection can be used via the View Data option to create a SQL Command window, which works as expected - the data is available. But nonetheless the project won't run. I have since tested a database application shell project using the derby local host connection and that does work. I will try installing NetBeans 'fresh' on another PC and see if it does the same thing? The problem turned out to be that netBeans hadn't completely copied the system proxy settings - specifically, it didn't pick up to use the same proxy for all protocols. Once I set the IDE proxy options manually, the problem disappeared. looks like I miss something, what is Database application shell? Also if you run project and it fails to run I'm not sure how it's related to netbeans (except case if something is generated wrongly). can you run this application outside of nb? can you provide sample code? Hi Sergeyp Thanks for your time. The problem seems to be that the Toplink persistence object is not able to access the database and is reporting a malformed SOCKS response. The project is automatically generated from New Project/Java Desktop/Database Application and is reading an existing database that runs on MS SQL 2000. The SOCKS request shouldn't be going via proxy - it should be connecting straight to the server. I have played with the proxy settings (No proxy, system settings, manual settings) in NetBeans and on one occasion it worked, but then stopped working for no obvious reason. I have tried using two different MS db drivers and the jTDS db driver and that made no difference. I tried installing a later MS SQL engine and using that to access the database - all good, but the same story within NetBeans. I have logged a maintenance ticket with our network security people and they don't see why there is a problem. I am the system owner for the databases and I have tested the local authentication loggin I am using using a variety of other environments and that works OK It is a bit of a mystery to me. As a NetBeans/JAVA neophyte, I am feeling rather discouraged! Maybe I should go back to VStudio... It seems the Swing Application Framework sets a SystemProxy property, so one needs to set it appropriately in the main class. See 134745 Thanks for your time guys. *** This issue has been marked as a duplicate of 134745 *** |