Archiva

Tomcat deployment of archiva results in unstable instance.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-alpha-1
  • Fix Version/s: 1.0-beta-3
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

When deploying archiva to a tomcat instance, the resulting instance is unstable and causes many other problems.

We need to identify, and document a tomcat installation.

Wiki docs: http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat

If a specific tomcat topic arises, please link it to this issue.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MRM-205 Undesirable Tomcat configuration for .jspf files

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRM-243 507 Insufficient Storage when deploying artifact with webdav

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRM-288 Error on startup: NPE, configuration can not be null

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRM-323 Managed repo in archiva cannot be accessed thru direct webdav url even with valid credentials (Archiva deployed in Tomcat)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRM-769 CLONE - 507 Insufficient Storage when deploying artifact with webdav

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. MRM-213 cannot undeploy archiva webapp

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Test - A new unit, integration or system test MRM-310 Selenium test cases do not run

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Joakim Erdfelt added a comment -

When reporting details, please include the following ....

  1. Java version? (specifics please, "1.5" is insufficient. "Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)" is of much more use.)
  2. Are you running the JDK or JRE?
  3. What version of Tomcat?
  4. Where did you get your version of Tomcat? (downloaded from apache.org, installed from OS packaging tool, etc...)
  5. What kind of OS are you running? (versions and service pack details are helpful)
  6. Are you using the embedded Derby Database or an external Database?
    • If an external Database, then the name and version of the database is helpful.
    • JDBC specifics too, what JDBC driver are you using? What version?
    • How do you have the JNDI Database connection configured? (yes, there are many ways to do this)
  7. Have you have tried the recommendations on http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat ? If not, why not?
Show
Joakim Erdfelt added a comment - When reporting details, please include the following .... Java version? (specifics please, "1.5" is insufficient. "Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)" is of much more use.) Are you running the JDK or JRE? What version of Tomcat? Where did you get your version of Tomcat? (downloaded from apache.org, installed from OS packaging tool, etc...) What kind of OS are you running? (versions and service pack details are helpful) Are you using the embedded Derby Database or an external Database? If an external Database, then the name and version of the database is helpful. JDBC specifics too, what JDBC driver are you using? What version? How do you have the JNDI Database connection configured? (yes, there are many ways to do this) Have you have tried the recommendations on http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat ? If not, why not?
Hide
Permalink
Joakim Erdfelt added a comment -

Completed testing and documentation on Jakarta Tomcat 5.0.28 on Linux using JDK 1.5.0_11.
Important notes about Jar file compatibility can be found at http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat#ArchivaonTomcat-Tomcat5.0.xSpecifics
No problems left.

Finishing up documentation and tests on Tomcat 5.5.25 and Tomcat 6.0.14 next.

Show
Joakim Erdfelt added a comment - Completed testing and documentation on Jakarta Tomcat 5.0.28 on Linux using JDK 1.5.0_11. Important notes about Jar file compatibility can be found at http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat#ArchivaonTomcat-Tomcat5.0.xSpecifics No problems left. Finishing up documentation and tests on Tomcat 5.5.25 and Tomcat 6.0.14 next.
Hide
Permalink
Joakim Erdfelt added a comment -

All open issues with Tomcat have been closed.
All fixes have been committed to archiva/trunk in svn.

The next archiva release (1.0-beta-3?) will contain these fixes.

Show
Joakim Erdfelt added a comment - All open issues with Tomcat have been closed. All fixes have been committed to archiva/trunk in svn. The next archiva release (1.0-beta-3?) will contain these fixes.

People

  • Assignee:
    Joakim Erdfelt
    Reporter:
    Joakim Erdfelt
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: