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.

Bug 252511

Summary:	default proxy (pac file) will not work for jdbc connection
Product:	platform	Reporter:	jijwang
Component:	Proxy	Assignee:	Libor Fischmeistr <lfischmeistr>
Status:	NEW ---
Severity:	normal	CC:	tpavek
Priority:	P3
Version:	8.1
Hardware:	PC
OS:	Windows 7
Issue Type:	DEFECT	Exception Reporter:

Description jijwang 2015-05-20 19:26:37 UTC

We are using build 201504141337. We found default proxy setting (pac file) not working for jdbc connection. We have to explicitly set up proxy server for jdbc connection to work. Otherwise we will get error like:
java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection

If we check Netbeans\dev\config\Preferences\org\netbeans\core.properties, the default proxy setting will create the following entries:
systemPAC=http://wpad/wpad.dat
testSystemProxyHttpHost=www-proxy...com
testSystemProxyHttpPort=80
usageStatisticsEnabled=false
usageStatisticsNbOfIdeStarts=3
usageStatisticsSetByIde=true
WWWBrowser=SL[/Browsers/SystemDefaultBrowser

But the specific proxy server set up will add the following above those lines:
proxyHttpHost=www-proxy...com
proxyHttpPort=80
proxyType=2

The same code for jdbc connection will work fine in Eclipse without any manual setup for proxy with the following default:
Active Provider: dynamic
Schema: HTTP
HOST: Dynamic
PORT: Dyanmic
Authentication: No

Why the default pac file setting not working?

Comment 1 Libor Fischmeistr 2015-07-07 08:06:48 UTC

Hi, could you please more describe the problem. I would like to reproduce, but don't know how. Where is the JDBC placed? Locally, in OWAN or outside? If you set up the proxy server manually in NetBeans, does it work? Can you please attach the IDE log?

http://wiki.netbeans.org/FaqLogMessagesFile

Comment 2 jijwang 2015-07-07 18:03:18 UTC

(In reply to Libor Fischmeistr from comment #1)
The scenario happened inside a corp network.I have sent mode details to your oracle email.