You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/03/28 16:40:58 UTC

[jira] Closed: (MRM-624) Failed to install Archiva as windows service

     [ http://jira.codehaus.org/browse/MRM-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRM-624.
----------------------------

         Assignee: Brett Porter
       Resolution: Fixed
    Fix Version/s:     (was: 1.0.x)
                   1.1

I'm closing this as fixed as it works for me with the new stuff in Archiva 1.1 on Vista.

Please reopen if you experience this problem with that (if you are able to test it in advance, that'd be perfect :)

> Failed to install Archiva as windows service
> --------------------------------------------
>
>                 Key: MRM-624
>                 URL: http://jira.codehaus.org/browse/MRM-624
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: Win XP/ JDK: IBM 5.0
>            Reporter: Slavomir Kocka
>            Assignee: Brett Porter
>            Priority: Minor
>             Fix For: 1.1
>
>
> When installing standalone Archiva as service, it simply does not work (Wrapper with switch -s)
> Logs says, that there failed to execute following command:
> C:\mkdis\apache-archiva-1.0\bin\windows-x86-32>"%JAVA_HOME%\bin\java" -Dclassworlds.conf="../../conf/classworlds.conf" -
> Djava.io.tmpdir="../../temp" -Dplexus.core="../../core" -Dplexus.home="../.." -Dtools.jar="C:\Program Files\IBM\Java50\l
> ib\tools.jar" -Dappserver.base="../.." -Dplexus.system.path="C:\Program Files\Windows Resource Kits\Tools\;C:\Program Fi
> les\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IBM\Infoprint Select;C:\
> Notes;C:\Program Files\XLView;C:\lotus\compnent;C:\Utilities;C:\Program Files\IBM\Personal Communications\;C:\Program Fi
> les\IBM\Trace Facility\;C:\WINDOWS\Downloaded Program Files;C:\mkdis\Python24;" -Xms3m -Xmx128m -Djava.library.path="../
> ../bin/windows-x86-32" -classpath "../../core/boot/wrapper.jar;../../core/boot/plexus-classworlds-1.2-alpha-7.jar" -Dwra
> pper.key="JQK7VC49zzNi9lh0" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.deb
> ug="TRUE" -Dwrapper.pid=4956 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwra
> pper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp org.codehaus.plexus.classworlds.laun
> cher.Launcher
> When I run this command in command line, I receive following output.
> WrapperManager class initialized by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@2d282d28
> Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
>   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
> Wrapper Manager: JVM #1
> Running a 32-bit JVM.
> Wrapper Manager: Registering shutdown hook
> Wrapper Manager: Using wrapper
> Load native library.  One or more attempts may fail if platform specific libraries do not exist.
> Loading native library failed: wrapper-windows-x86-32.dll  Cause: java.lang.UnsatisfiedLinkError: wrapper-windows-x86-32
>  (Not found in java.library.path)
> Loaded native library: wrapper.dll
> Calling native initialization method.
> Initializing WrapperManager native library.
> Java Executable: C:\Program Files\IBM\Java50\bin\java.exe
> Windows version: 5.1.2600
> Java Version   : J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20071007 (JIT enabled)
> J9VM - 20071004_14218_lHdSMR
> JIT  - 20070820_1846ifx1_r8
> GC   - 200708_10
> Java VM Vendor : IBM Corporation
> WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@2f1e2f1e, args[]) called by thread: main
> Control event monitor thread started.
> Startup runner thread started.
> Communications runner thread started.
> Open socket to wrapper...Wrapper-Connection
> Failed to connect to the Wrapper at port 32000.
> java.net.ConnectException: Connection refused: connect

-- 
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