You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Robert Munteanu <ro...@gmail.com> on 2009/09/02 22:57:16 UTC

Unable to deploy released war file to archiva

Hi,

I've observed some strange behaviour when deploying and waited to verify on
1.2.2 as well before posting.

I am not able to deploy a release version of a war project, while a snapshot
works fine. Deploying a pom project works for both snapshot and release.

The war file is 19MB large, so I adjusted the upload size ( but that
would've been contradicted by the snapshot upload working ) without any
success.

The error I get in archiva.log is

2009-09-02 23:36:02,985 [TP-Processor3] INFO 
org.apache.maven.archiva.security.ArchivaServletAuthenticator  -
Authorization Denied
[ip=81.180.230.218,permission=archiva-upload-repository,repo=internal] : no
matching permissions
2009-09-02 23:36:33,057 [TP-Processor3] INFO 
org.apache.maven.archiva.security.ArchivaServletAuthenticator  -
Authorization Denied
[ip=81.180.230.218,permission=archiva-upload-repository,repo=internal] : no
matching permissions

(yes, twice)

My workflow is

I simply run mvn deploy which leads to 

[INFO] [deploy:deploy {execution: default-deploy}]
Uploading:
https://archiva/repository/internal/com/example/project/0.4.0/project-0.4.0.war
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error deploying artifact: Error transferring file
Error writing to server

mvn -v says

Apache Maven 2.2.1 (r801777; 2009-08-06 22:16:01+0300)
Java version: 1.6.0_0
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.27.29-0.1-pae" arch: "i386" Family: "unix"

Any hints would be greatly appreciated.

Robert

-- 
View this message in context: http://www.nabble.com/Unable-to-deploy-released-war-file-to-archiva-tp25265603p25265603.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Unable to deploy released war file to archiva

Posted by Robert Munteanu <ro...@gmail.com>.

brettporter wrote:
> 
> Certainly seems correct. Have you double checked that the property  
> isn't duplicated or wasn't reset by the WAR being unpacked again?
> 
> Thanks,
> Brett
> 

Thanks for the reply. Indeed, I've managed to forget removing the unpacked
directory, so I was running 1.2 with the default struts.properties.

Uploading through the web form no longer fails immediately, but after a
while I get a 503 page ( mod_proxy_ajp ) and nothing in archiva.log . Later
on, the artifacts are cleaned up

2009-09-04 22:10:31,335 [TP-Processor7] INFO 
org.apache.struts2.interceptor.FileUploadInterceptor  - Removing file
artifact
/usr/share/tomcat6/work/Catalina/dev/archiva/upload__472e0e6c_123866c07f6__7fef_00000006.tmp
2009-09-04 22:10:31,345 [TP-Processor7] INFO 
org.apache.struts2.interceptor.FileUploadInterceptor  - Removing file pom
/usr/
share/tomcat6/work/Catalina/dev/archiva/upload__472e0e6c_123866c07f6__7fef_00000007.tmp
2009-09-04 22:10:31,345 [TP-Processor7] INFO 
org.apache.struts2.interceptor.FileUploadInterceptor  - Removing file
artifact
/usr/share/tomcat6/work/Catalina/dev/archiva/upload__472e0e6c_123866c07f6__7fef_00000006.tmp
2009-09-04 22:10:31,346 [TP-Processor7] INFO 
org.apache.struts2.interceptor.FileUploadInterceptor  - Removing file pom
/usr/
share/tomcat6/work/Catalina/dev/archiva/upload__472e0e6c_123866c07f6__7fef_00000007.tmp

And still no luck with mvn deploy.

Robert
-- 
View this message in context: http://www.nabble.com/Unable-to-deploy-released-war-file-to-archiva-tp25265603p25300553.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Unable to deploy released war file to archiva

Posted by Brett Porter <br...@apache.org>.
Certainly seems correct. Have you double checked that the property  
isn't duplicated or wasn't reset by the WAR being unpacked again?

Thanks,
Brett


On 04/09/2009, at 2:51 AM, Robert Munteanu wrote:

>
> As a follow-up, using the web interface leads to
>
> (archiva.log)
>
> 2009-09-03 19:32:53,828 [TP-Processor9] ERROR
> org.apache.struts2.dispatcher.multipart.MultiPartRequest  -
> org.apache.commons.fileupload.FileUploadBase 
> $SizeLimitExceededException: the
> request was rejected because its size (19965835) exceeds the  
> configured
> maximum (10485760)
> 2009-09-03 19:32:53,862 [TP-Processor9] ERROR
> org.apache.struts2.interceptor.FileUploadInterceptor  - the request  
> was
> rejected because its size (19965835) exceeds the configured maximum
> (10485760)
>
> and receiving a connection reset response in the brower.
>
> Strangely enough, I modified the struts.properties file directly in  
> the war
> file to read
>
> struts.multipart.maxSize=31457280
>
> Any ideas as to why this happens?
>
> -- 
> View this message in context: http://www.nabble.com/Unable-to-deploy-released-war-file-to-archiva-tp25265603p25279947.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>

Re: Unable to deploy released war file to archiva

Posted by Robert Munteanu <ro...@gmail.com>.
As a follow-up, using the web interface leads to

(archiva.log)

2009-09-03 19:32:53,828 [TP-Processor9] ERROR
org.apache.struts2.dispatcher.multipart.MultiPartRequest  -
org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: the
request was rejected because its size (19965835) exceeds the configured
maximum (10485760)
2009-09-03 19:32:53,862 [TP-Processor9] ERROR
org.apache.struts2.interceptor.FileUploadInterceptor  - the request was
rejected because its size (19965835) exceeds the configured maximum
(10485760)

and receiving a connection reset response in the brower.

Strangely enough, I modified the struts.properties file directly in the war
file to read

struts.multipart.maxSize=31457280

Any ideas as to why this happens?

-- 
View this message in context: http://www.nabble.com/Unable-to-deploy-released-war-file-to-archiva-tp25265603p25279947.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Unable to deploy released war file to archiva

Posted by Robert Munteanu <ro...@gmail.com>.

Wendy Smoak-3 wrote:
> 
> On Wed, Sep 2, 2009 at 1:57 PM, Robert
> Munteanu<ro...@gmail.com> wrote:
> 
>> The error I get in archiva.log is
>>
>> 2009-09-02 23:36:02,985 [TP-Processor3] INFO
>> org.apache.maven.archiva.security.ArchivaServletAuthenticator  -
>> Authorization Denied
>> [ip=81.180.230.218,permission=archiva-upload-repository,repo=internal] :
>> no
>> matching permissions
>> 2009-09-02 23:36:33,057 [TP-Processor3] INFO
>> org.apache.maven.archiva.security.ArchivaServletAuthenticator  -
>> Authorization Denied
>> [ip=81.180.230.218,permission=archiva-upload-repository,repo=internal] :
>> no
>> matching permissions
> 
> Credentials are configured per repository, so it sounds like you have
> permission to deploy to the snapshots repo, but not to internal.
> 
> 

These are my roles:

    * Global Repository Manager
    * Repository Observer - snapshots
    * Repository Observer - internal
    * Global Repository Observer
    * Registered User
    * Repository Manager - snapshots
    * Repository Manager - internal


Wendy Smoak-3 wrote:
> 
> What do you have in settings.xml?  
> 

<settings>
        <servers>
            <server>
            <id>internal</id>
                <username>robert</username>
                <password>x</password>
        </server>
           <server>
            <id>snapshots</id>
                <username>robert</username>
                <password>x</password>
        </server>

        </servers>
</settings>


Wendy Smoak-3 wrote:
> 
> What does distributionManagement look like for this project?
> 

  <distributionManagement>
    <repository>
      <id>internal</id>
      <name>Archiva Managed Internal Repository</name>
      <url>https://archiva/repository/internal/</url>
    </repository>
    <snapshotRepository>
      <id>snapshots</id>
      <name>Archiva Managed Snapshot Repository</name>
      <url>https://archiva/repository/snapshots/</url>
    </snapshotRepository>
  </distributionManagement>


Wendy Smoak-3 wrote:
> 
> Double check that the user in question has the repository manager role
> for the internal repo.
> 

That was my initial thought, but being able to deploy another (pom) project
made me reconsider. The project I was able to deploy is actually the war
project's parent and the war project inherits the distributionManagement
section.

Thanks,

Robert

-- 
View this message in context: http://www.nabble.com/Unable-to-deploy-released-war-file-to-archiva-tp25265603p25266057.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Unable to deploy released war file to archiva

Posted by Wendy Smoak <ws...@gmail.com>.
On Wed, Sep 2, 2009 at 1:57 PM, Robert
Munteanu<ro...@gmail.com> wrote:

> The error I get in archiva.log is
>
> 2009-09-02 23:36:02,985 [TP-Processor3] INFO
> org.apache.maven.archiva.security.ArchivaServletAuthenticator  -
> Authorization Denied
> [ip=81.180.230.218,permission=archiva-upload-repository,repo=internal] : no
> matching permissions
> 2009-09-02 23:36:33,057 [TP-Processor3] INFO
> org.apache.maven.archiva.security.ArchivaServletAuthenticator  -
> Authorization Denied
> [ip=81.180.230.218,permission=archiva-upload-repository,repo=internal] : no
> matching permissions

Credentials are configured per repository, so it sounds like you have
permission to deploy to the snapshots repo, but not to internal.

What do you have in settings.xml?  What does distributionManagement
look like for this project?

Double check that the user in question has the repository manager role
for the internal repo.

-- 
Wendy