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 220153 - Second run opens browser at wrong address
Summary: Second run opens browser at wrong address
Status: VERIFIED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P1 normal (vote)
Assignee: Petr Hejl
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2012-10-16 08:31 UTC by Jiri Skrivanek
Modified: 2012-10-22 09:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Log files. (24.03 KB, application/octet-stream)
2012-10-16 08:31 UTC, Jiri Skrivanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2012-10-16 08:31:11 UTC
Created attachment 126000 [details]
Log files.

When you run web application second time, it tries to open browser at wrong address. To reproduce:

- create web project with WebLogic 12.1.1 server
- run project
- wait until page is show in browser
- run project again but it tries to open browser at dns (Browsing: http://192.168.56.1:7001/WebApplication2)

Product Version: NetBeans IDE Dev (Build 201210160002)
Java: 1.7.0_07; Java HotSpot(TM) 64-Bit Server VM 23.3-b01
System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Comment 1 Petr Hejl 2012-10-16 08:50:56 UTC
Would be good to know IP configuration. The address does not come out of nowhere plus it is provided by WL itself.
Comment 2 Petr Hejl 2012-10-16 13:36:39 UTC
As we figured out with Jirka this is WL binding/proxy issue. The IP address in this case is one of the addresses WL is listening to (and returned as location of the app). However the access to the address went through proxy which probably reject it (as it is from private range).
Comment 3 Petr Hejl 2012-10-16 13:40:36 UTC
I'm afraid this might be considered as designed and I didn't find anything we could do about that. Though I filed issue #220174 which is kind of opposite problem to this one.