Happy to hear you found the problem.
It may be either a timeout, max packet size or max number of AJP connections
allowed (in release mode maven sends parallel queries).
HTH,
Fred.
On Tue, Apr 13, 2010 at 11:12 PM, eitank <[email protected]> wrote:
>
> It is the apache proxy that is causing the issue but I can't for the life
> of
> me figure out why. I was able to run the deployment of a release directly
> against the artifactory address. If anyone knows why apache would have an
> issue with a release deployment, I'd love to hear it.
>
>
>
> eitank wrote:
> >
> > One more bit of info:
> > If I add the "-SNAPSHOT" to the version in the pom.xml, the deploy works
> > fine. Otherwise it fails with the 502 error code.
> >
> >
> > eitank wrote:
> >>
> >> Sadly, the URLs for release and snapshot are the same and the war file
> is
> >> 25MB.
> >>
> >> Both snapshot and release requests are going through the same apache
> >> proxy to unpack the ssl.
> >>
> >>
> >>
> >>
> >> freddy33 wrote:
> >>>
> >>> Hi,
> >>>
> >>> I suspect you did not find anything in the artifactory.log?
> >>> The 502 http code means Bad Gateway and is not returned by Artifactory
> >>> itself. It is generally due to proxy (AJP or other) or pure Apache
> >>> configuration errors.
> >>>>From your environment I can see 2 reason:
> >>> 1) The new ss-1.0.5.war file is empty with no data
> >>> 2) The URL or ID defined in distributionManagement are different for
> >>> repository and snapshotRepository.
> >>>
> >>> Hope it helps,
> >>> Fred.
> >>>
> >>> On Tue, Apr 13, 2010 at 10:18 AM, eitank <[email protected]>
> >>> wrote:
> >>>
> >>>>
> >>>> I'm trying to deploy a release to our artifactory installation
> (v2.2.2)
> >>>> and
> >>>> I
> >>>> get the following error:
> >>>>
> >>>> Error deploying artifact: Failed to transfer file:
> >>>>
> >>>>
> https://maven.ss.com/artifactory/libs-releases-local/com/frog/app/ss/1.0.5/ss-1.0.5.war
> >>>> .
> >>>> Return code is: 502
> >>>>
> >>>> I created the tag in svn using the release plugin, both
> release:perform
> >>>> and
> >>>> deploy result in the above failure.
> >>>>
> >>>> I do not get this error with a snapshot version.
> >>>>
> >>>> The only thing I see in the logs is that the http response code is
> 401.
> >>>> My
> >>>> username and password are set in my settings.xml and are the same for
> >>>> both
> >>>> the repository and the snapshotRepository.
> >>>>
> >>>> I changed the password encryption policy from required to supported
> and
> >>>> updated changed my password to clear text and still had the same
> >>>> failure
> >>>> pattern (snapshots worked but releases failed).
> >>>>
> >>>> I've verified that the local repository handles both releases and
> >>>> snapshots.
> >>>> I've tried creating another local repository and got the same failure
> >>>> pattern.
> >>>>
> >>>> Any advice would be greatly appreciated.
> >>>>
> >>>> --
> >>>> View this message in context:
> >>>>
> http://old.nabble.com/Deploying-snapshots-works-but-releases-fail-tp28219425p28219425.html
> >>>> Sent from the Artifactory-Users mailing list archive at Nabble.com.
> >>>>
> >>>>
> >>>>
> >>>>
> ------------------------------------------------------------------------------
> >>>> Download Intel® Parallel Studio Eval
> >>>> Try the new software tools for yourself. Speed compiling, find bugs
> >>>> proactively, and fine-tune applications for parallel performance.
> >>>> See why Intel Parallel Studio got high marks during beta.
> >>>> http://p.sf.net/sfu/intel-sw-dev
> >>>> _______________________________________________
> >>>> Artifactory-users mailing list
> >>>> [email protected]
> >>>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Co. Founder and Chief Architect
> >>> JFrog Ltd
> >>> http://www.jfrog.org/
> >>> http://twitter.com/freddy33
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Download Intel® Parallel Studio Eval
> >>> Try the new software tools for yourself. Speed compiling, find bugs
> >>> proactively, and fine-tune applications for parallel performance.
> >>> See why Intel Parallel Studio got high marks during beta.
> >>> http://p.sf.net/sfu/intel-sw-dev
> >>> _______________________________________________
> >>> Artifactory-users mailing list
> >>> [email protected]
> >>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
> >>>
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Deploying-snapshots-works-but-releases-fail-tp28219425p28235014.html
> Sent from the Artifactory-Users mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
--
Co. Founder and Chief Architect
JFrog Ltd
http://www.jfrog.org/
http://twitter.com/freddy33
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
