Skip to main content

pkg having trouble getting package list

2 replies [Last post]
ljnelson
Offline
Joined: 2003-08-04
Points: 0

Hello; as part of our installation we use the (rather outdated) Hibernate
add-on, which we install by way of the bundled pkg software.

Lately we've noticed we get this error when we run pkg (when we're first
setting up a new GlassFish installation):

Connection failed for URL http://pkg.glassfish.org/v3/stable/catalog/0:
503: Service Temporarily Unavailable

In these cases we are able to browse to this URL using a browser and can
see the list of packages.

Has something changed with pkg.glassfish.org such that it would return 503
for the pkg client, but not for a web browser?

Best,
Laird

--
http://about.me/lairdnelson

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
jfdipol
Offline
Joined: 2007-08-16
Points: 0

Laird,

I'm unaware of any specific change that would cause this. My guess
is that this is a sporadic/transient issue, possibly based on load.

I do occasionally see connection failures on our scripts that
continuously check
repository health. But that has been the case for quite a while
(so it's not a new condition).

Joe

On 1/8/13 7:47 AM, Laird Nelson wrote:
> Hello; as part of our installation we use the (rather outdated)
> Hibernate add-on, which we install by way of the bundled pkg software.
>
> Lately we've noticed we get this error when we run pkg (when we're
> first setting up a new GlassFish installation):
>
> Connection failed for URL
> http://pkg.glassfish.org/v3/stable/catalog/0: 503: Service
> Temporarily Unavailable
>
>
> In these cases we are able to browse to this URL using a browser and
> can see the list of packages.
>
> Has something changed with pkg.glassfish.org
> such that it would return 503 for the pkg
> client, but not for a web browser?
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson

ljnelson
Offline
Joined: 2003-08-04
Points: 0

On Tue, Jan 8, 2013 at 12:29 PM, Joe Di Pol wrote:

> I'm unaware of any specific change that would cause this. My guess
> is that this is a sporadic/transient issue, possibly based on load.
>

Thanks; it seems to be pretty persistent (has gone on for around 18-24
hours now). The GUI update center on this particular machine suffers from
the same issue. No proxy server is in play.

Best,
Laird

--
http://about.me/lairdnelson