Hi Sam,
The console is using the Java API that updatetool provides and it
should be using the system proxy settings.
I will also check to see that thats the case indeed.
If you have the console running, you can also go to the Configuration
tab of the update center tree node, and set it up.
Or you can bring up glassfishv3/bin/updateool and set the proxy
there. Yes, you can still run updatetool even though you de-select
that during installation.
thanks
Anissa
Sam Crawford wrote:
Correct, the server does not have direct connectivity to the
repository. It's in a corporate/firewalled network, and all
communications have to at least go via a proxy server. This is very
common in corporate networks.
I'd have thought this would be quite a big issue for corporates trying
to use the new software, no?
Is there any workaround?
Thanks,
Sam
2009/12/11 Anissa Lam <Anissa.Lam@sun.com>:
Hi Sam,
The Update Center setting that you select during installation only applies
to the standalone updatetool application. It is not communicated to the
admin console. During console startup, we try to connect to the
repository to check if there is any available update for you. This also
happens when you go to the Update Center tree node.
As indicated in the log, there seems to be a network issue and waiting for
timeout takes the long time. We can file an RFE against admingui for
providing a way for user to disable the update center functionality in the
GUI. In the meantime, i would like to know if your server indeed does not
have network access or the repository has issue.
thanks
Anissa.
Sam Crawford wrote:
Hello,
When I installed GlassFish v3 (the enterprise edition) I requested
that the Update Center functionality be skipped.
However, when trying to access the admin console on port 4848, I find
that it takes a very long time to login, and I see the following in
the serverlogs:
[#|2009-12-11T16:31:07.816+0000|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=29;_ThreadName=Thread-1;|Cannot
refresh Catalog : Connection timed out|#]
[#|2009-12-11T16:31:07.950+0000|INFO|glassfishv3.0|org.glassfish.admingui|_ThreadID=26;_ThreadName=Thread-1;|Update
Component count = 0|#]
[#|2009-12-11T16:31:08.086+0000|INFO|glassfishv3.0|org.glassfish.admingui|_ThreadID=29;_ThreadName=Thread-1;|Update
Component count = 0|#]
When the console does eventually load, clicking on the "Update Center"
tab (in the hope to find another way to disable it) generates a very
long stream of "Connection timed out" stacktraces in the server log.
How can the Update Center functionality be completely disabled? And do
you know why the console still seems to be making connections, even
though I requested the Update Center disabled at installation time?
Thanks,
Sam
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net