Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » UnknownHostException when profiling URL.openStream()

Help

Home

Home » Archived » Test and Performance Tools Platform (TPTP) » UnknownHostException when profiling URL.openStream()

Show: Today's Messages :: Show Polls :: Message Navigator

UnknownHostException when profiling URL.openStream() [message #105450]

Wed, 18 July 2007 07:45

Philipp Tiedt

Messages: 52
Registered: July 2009

Member

Hi,

I just ran into an UnknownHostException when profiling a little piece of
code that does nothing more than

try {
URL url = new URL("http://www.eclipse.org");
url.openStream();
} catch (MalformedURLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}

Running the code without profiling would work. However profiling it throws
the exception saying www.eclipse.org is an unknown host.

Eclipse Europa + TPTP Java 1.5 WinXP

Any Ideas ?
Philipp

Report message to a moderator

Re: UnknownHostException when profiling URL.openStream() [message #105687 is a reply to message #105450]

Thu, 19 July 2007 06:56

Asaf Yaffe

Messages: 333
Registered: July 2009

Senior Member

Philipp Tiedt wrote:
> Hi,
>
> I just ran into an UnknownHostException when profiling a little piece of
> code that does nothing more than
> try {
> URL url = new URL("http://www.eclipse.org");
> url.openStream();
> } catch (MalformedURLException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> } catch (IOException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
>
> Running the code without profiling would work. However profiling it
> throws the exception saying www.eclipse.org is an unknown host.
>
> Eclipse Europa + TPTP Java 1.5 WinXP
>
> Any Ideas ?
> Philipp
>

Philipp,

This seems like an environment configuration problem. If you are behind
a Firewall or a Proxy server, it is likely that the Java environment
used by Eclipse is configured to pass the Proxy/Firewall while the
environment used by the Profiler (actually, the Agent Controller) is not
properly configured.

Here's an example, if you are behind a proxy server, adding the
following command line options to the VM argument will resolve the
problem (replace the mock up values with real ones):

-Dhttp.proxyHost=proxy.mycompany.com -Dhttp.proxyPort=8080

HTH,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler

Report message to a moderator