JDK-6352254 : JRE 5 plugin fails to get connection to the server if proxy server is used.
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 5.0u2
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2005-11-17
  • Updated: 2010-04-02
  • Resolved: 2006-04-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
5.0u8Resolved 6Resolved
Related Reports
Duplicate :  
JDK-6365587 - Proxy-Connection header sent through tunnel
Description
Customer has some applet code which works fine in 1.4.2 while using a proxy, but does not work in 1.5.0_02. If they turn off the proxy, 1.5.0_02 starts to work fine. They are specifying JPI to use browser based proxy settings from IE 6.

Unfortunately, we can't get a runnable test-case from them and can only see the resulting exceptions.

The client browser (IE) receives an error back after it has downloaded the applet code from the server, and then the applet code tries to initially connect back  to the server to perform some transaction. When the proxy is in use, they see a 3-10 minute 'hang' at the end of which they finally get back a NullPointerException. The following exception is the result of 1.5.0_02+proxy+error logging,

LOGIN_TYPE: DIRECT_LOGIN
PORTAL_APP_NAME: CITIDIRECT
CSM_TABLE_KEY: a2578b595f888d575d54608d5e59545b5f885754608a8a59548b8d585f5e605c5f8a5a595ca4a37a7074777a6c6aa3777e555d5957585e5aa38c95867c7a39
cookie: JPIclsid=clsid:CAFEEFAC-0015-0000-0002-ABCDEFFEDCBA; ClientVM=JPI; PilotJPI=YES; SWID=PW.620173|en_US; JSESSIONID=0000WIU7PnxmV0UP5y3Y6V3FIiM:10gs9uq2u; LangID=en_US; SWID=PW.620173|en_US; UserBinding=1-0; CasaCoAuthCookie={0d28af06-9f72-48a0-9cc2-df187958c325}|SIMPSEC|PW.620173|en_US; LOGIN_METHOD=CITIDIRECT; PLUGIN_DOWNLOAD=FALSE;LOGIN_TYPE=DIRECT_LOGIN|CITIDIRECT
Content-length: 565

_CDC_SRV_ID_=9000&_RETRY_SEQ_=0&_RETRY_=1&_BUF_=FIRST_DATA%3D%28S_COMPRESSED_UTF_MSG_%253D%25286eJytkDsKAkEQROsqZgorzNfVwGA%2FDgiCiWfwEsve3deNGBkYSNHVNf2Z7hktipo1qOqCBbBXD0%2FKqOjZiDrpoKKEshqLJ5BBARWsOmurJzbRc9fNz1eqOzjClttoBzo9fqhZ2OlItOELPvj0xqz02c3UiB993%2FBGo6%2FHZtj2X7%2FO%2Bff9A9WWrd4b%2BbFAPrllf5PjBWkeKV8%25253D%2529%29%2CFIRST_REQUEST%3D%28Btrue%29&_CMD_=GET_INIT_DATA&_VM_VERSION_=SUNJRE
&CSM_TABLE_KEY=a2578b595f888d575d54608d5e59545b5f885754608a8a59548b8d585f5e605c5f8a5a595ca4a37a7074777a6c6aa3777e555d5957585e5aa38c95867c7a39&LOGIN_TYPE=DIRECT_LOGIN-b09&PLUGIN_VERSION=1.5.0_02&LZ=266&NUM_OF_ROUNDTRIPS=1 HTTP/1.1
, Object[0]=[] caught java.lang.IllegalArgumentException: can't parse argument number 0d28af06-9f72-48a0-9cc2-df187958c325
Exception in thread "AWT-EventQueue-3" java.lang.NullPointerException
    at com.citibank.casa.awt.CasaDialog.getButtonPanel(CasaDialog.java:259)
    at com.citibank.casa.awt.CasaInteractionDialog.focusFirstButton(CasaInteractionDialog.java:188)
    at com.citibank.casa.awt.CasaMessageBox.processInitialFocus(CasaMessageBox.java:86)
    at com.citibank.casa.awt.CasaInteractionDialogWindowAdapter.windowOpened(CasaInteractionDialogWindowAdapter.java:26)
    at java.awt.Window.processWindowEvent(Unknown Source)
    at com.sun.java.swing.JDialog.processWindowEvent(JDialog.java:192)
Comments
EVALUATION Transferring to classes_net as requested by Hao Dong.
17-03-2006
EVALUATION This bug requires further evaluation and possibly coordination with the networking team for resolution. It is only reproducible in a limited scenario where a proxy server is used which requires cookie information in the connection headers. Therefore, untargeting this from 5.0u7. This will be considered for a future update or feature release.
08-02-2006