You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org> on 2007/05/10 19:52:13 UTC

[jira] Commented: (MRM-333) Tomcat deployment of archiva results in unstable instance.

    [ http://jira.codehaus.org/browse/MRM-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95578 ] 

Joakim Erdfelt commented on MRM-333:
------------------------------------

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?

> Tomcat deployment of archiva results in unstable instance.
> ----------------------------------------------------------
>
>                 Key: MRM-333
>                 URL: http://jira.codehaus.org/browse/MRM-333
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-1
>            Reporter: Joakim Erdfelt
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira