directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Only (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DIRSERVER-1918) ApacheDS 2.0.0-M15 fails to start in Windows 2003 Server R2
Date Fri, 15 Nov 2013 13:01:20 GMT
Di Only created DIRSERVER-1918:
----------------------------------

             Summary: ApacheDS 2.0.0-M15 fails to start in Windows 2003 Server R2
                 Key: DIRSERVER-1918
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1918
             Project: Directory ApacheDS
          Issue Type: Bug
          Components: core
    Affects Versions: 2.0.0-M15
         Environment: Windows 2003 R2 Server 
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing)
            Reporter: Di Only
            Priority: Blocker


After installing ApacheDS it started as a service however once stopped i.e. windows restarted,
it failed to start.
I uninstalled and installed again but the behaviour was exactly the same. Once starts immediately
after install. I have set the service start to manual and have attempted to manually start
but all I get is service error that reads:
"Could not start ApacheDS - default on local Computer.
Error 1067: The process terminated unexpectedly"

Windows event log says "The ApacheDS - default service terminated unexpectedly.  It has done
this 3 time(s)."

apacheds.log is empty.

wrapper.log has the following entries repeated several times:
STATUS | wrapper  | 2013/11/15 12:50:23 | --> Wrapper Started as Service
STATUS | wrapper  | 2013/11/15 12:50:23 | Launching a JVM...
INFO   | jvm 1    | 2013/11/15 12:50:26 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2013/11/15 12:50:26 |   Copyright 1999-2006 Tanuki Software, Inc.  All
Rights Reserved.
INFO   | jvm 1    | 2013/11/15 12:50:26 | 
STATUS | wrapper  | 2013/11/15 12:50:51 | <-- Wrapper Stopped

Config was changed as follow but it has not made any difference:
wrapper.startup.timeout=300
wrapper.ping.timeout=600




--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message