directory-fortress mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleksandr Bodriagov (Polystar)" <oleksandr.bodria...@polystar.com>
Subject Re: [Bulk] Re: [Bulk] [Bulk] problem deploying fortress-rest
Date Wed, 22 Apr 2015 09:30:45 GMT

Hi Shawn,

I have pulled the new core and installed everything from scratch following
instructions in 
"apache-fortress-rest.html”
and I got stuck again at the rest part. Everything till this point worked:

[INFO] --- tomcat-maven-plugin:1.1:deploy (default-cli) @ fortress-rest ---
[INFO] Deploying war to
http://localhost:8080/fortress-rest-1.0-RC40-SNAPSHOT
[INFO] 
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] 
------------------------------------------------------------------------
[INFO] Total time: 15.025s
[INFO] Finished at: Wed Apr 22 11:18:11 CEST 2015
[INFO] Final Memory: 43M/478M
[INFO] 
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project
fortress-rest: Cannot invoke Tomcat manager: FAIL - Deployed application
at context path /fortress-rest-1.0-RC40-SNAPSHOT but context failed to
start -> [Help 1]


Here is my "target/fortress-rest-1.0-RC40-SNAPSHOT/fortress.properties”
file (it describes a local installation on my computer):
#
#   Licensed to the Apache Software Foundation (ASF) under one
#   or more contributor license agreements.  See the NOTICE file
#   distributed with this work for additional information
#   regarding copyright ownership.  The ASF licenses this file
#   to you under the Apache License, Version 2.0 (the
#   "License"); you may not use this file except in compliance
#   with the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
#   Unless required by applicable law or agreed to in writing,
#   software distributed under the License is distributed on an
#   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
#   KIND, either express or implied.  See the License for the
#   specific language governing permissions and limitations
#   under the License.
#
# Fortress slapd.conf default settings.
# Note: Directives that begin with '@' are substitution parms for
Fortress' build.xml 'init-slapd' target.

# Host name and port of LDAP DIT:
host=localhost
port=10389

# Used for SSL Connection to LDAP Server:
enable.ldap.ssl=false
enable.ldap.ssl.debug=${enable.ldap.ssl.debug}
trust.store=${trust.store}
trust.store.password=${trust.store.password}
trust.store.set.prop=${trust.store.set.prop}

# Used for SSL Demo with Tomcat:
key.store=${key.store}
key.store.password=${key.store.password}

# These credentials are used for read/write access to all nodes under
suffix:
admin.user=uid=admin,ou=system
# LDAP admin root pass is encrypted using 'encrypt' target in build.xml:
admin.pw=secret

# This is min/max settings for LDAP administrator pool connections that
have read/write access to all nodes under suffix:
min.admin.conn=1
max.admin.conn=10

# This is min/max connection pool settings for LDAP User authentication
connection pool:
min.user.conn=1
max.user.conn=10

# These credentials are used for read/write access to all nodes under
slapd access log suffix:
log.admin.user=cn=Manager,cn=log
# For corresponding log user:
log.admin.pw=secret

# This is min/max settings for LDAP connections to read slapo access log:
min.log.conn=1
max.log.conn=3

# This node contains fortress properties stored on behalf of connecting
LDAP clients:
config.realm=DEFAULT
config.root=ou=Config,dc=example,dc=com

# enable this to see trace statements when connection pool allocates new
connections:
debug.ldap.pool=true

# Default for pool reconnect flag is false:
enable.pool.reconnect=true

crypto.prop=${crypto.prop}

ehcache.config.file=ehcache.xml

# If for any reason echcache must be DISABLED for DSD, make sure this
parameter is set to 'true' which is the default.  Otherwise performance
penalty will be incurred during multi-role activations.
disable.dsd.cache=false

# This will override default LDAP manager implementations for the RESTful
ones:
enable.mgr.impl.rest=false
# Optional parameters needed when Fortress client is connecting with the
En Masse (rather than LDAP) server:
http.user=demouser4
http.pw=password
http.host=localhost
http.port=8080

dao.connector=apache

GroupTest=org.apache.directory.fortress.core.group.GroupAntTest

# These may be used to override default LDAP or REST with OTHER
implementations:
#reviewmgr.implementation=org.apache.directory.fortress.core.rest.ReviewMgr
OtherImpl
#adminmgr.implementation=org.apache.directory.fortress.core.rest.AdminMgrOt
herImpl
#accessmgr.implementation=org.apache.directory.fortress.core.rest.AccessMgr
OtherImpl
#delegated.adminmgr.implementation=org.apache.directory.fortress.core.rest.
DelAdminMgrOtherImpl
#delegated.reviewmgr.implementation=org.apache.directory.fortress.core.rest
.DelReviewMgrOtherImpl
#policymgr.implementation=org.apache.directory.fortress.core.rest.PwPolicyM
grOtherImpl
#delegated.accessmgr.implementation=org.apache.directory.fortress.core.rest
.DelAccessMgrOtherImpl
#auditmgr.implementation=org.apache.directory.fortress.core.rest.AuditMgrOt
herImpl
#configmgr.implementation=org.apache.directory.fortress.core.rest.ConfigMgr
OtherImpl

/Oleksandr





On 21/4/2015 22:18 , "Shawn McKinney" <smckinney@apache.org> wrote:

>
>> On Apr 21, 2015, at 12:46 PM, Oleksandr Bodriagov (Polystar)
>><oleksandr.bodriagov@polystar.com> wrote:
>> 
>> I have tried doing as you said and again got:
>> [INFO] BUILD FAILURE
>> [INFO] 
>> ------------------------------------------------------------------------
>> [INFO] Total time: 19.351s
>> [INFO] Finished at: Tue Apr 21 19:39:00 CEST 2015
>> [INFO] Final Memory: 43M/475M
>> [INFO] 
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on
>>project
>> fortress-rest: Cannot invoke Tomcat manager: FAIL - Deployed application
>> at context path /fortress-rest-1.0-RC40-SNAPSHOT but context failed to
>> start -> [Help 1]
>> 
>> 
>> My java version is ³1.8.0_31².
>
>Oleksandr,
>
>I retried with java 8 and same version tomcat as you, 8.0.21 and have
>ruled that out as potential problem.
>
>But, I have discovered a problem with fortress core packaging.  The core
>jar includes the fortress.properties inside of it which is bad.  So that
>problem has just been fixed but requires you to repull the core and run
>mvn install on that component.
>
>Next when you try to redeploy your rest component you should use that
>latest core just built.  After you have redeployed and if you still have
>a problem, verify that fortress.properties is not inside the
>fortress-core jar.  Next send me the fortress.properties you are using
>inside your rest component (scrubbed of sensitive info like creds, dn’s).
>
>Thanks
>
>Shawn
>smckinney@apache.org

Mime
View raw message