We have not actually tested if that particular build works. Maybe that is
a problem.
Would you suggest us trying with latest and greatest RC-41?
I tried to set the FINEST debug level in logging.properties, but it did
not give much more information:
18-Jun-2015 08:57:02.879 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[org.apache.catalina.webresources.StandardRoot@2adb4678] to [STARTING]
18-Jun-2015 08:57:02.880 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[org.apache.catalina.webresources.StandardRoot@2adb4678] to [STARTED]
18-Jun-2015 08:57:03.053 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[WebappLoader[/fortress-web-1.0.9]] to [INITIALIZING]
18-Jun-2015 08:57:03.054 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[WebappLoader[/fortress-web-1.0.9]] to [INITIALIZED]
18-Jun-2015 08:57:03.060 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[WebappLoader[/fortress-web-1.0.9]] to [STARTING_PREP]
18-Jun-2015 08:57:03.114 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[WebappLoader[/fortress-web-1.0.9]] to [STARTING]
18-Jun-2015 08:57:03.119 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[WebappLoader[/fortress-web-1.0.9]] to [STARTED]
18-Jun-2015 08:57:03.128 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[Realm[org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy]] to
[INITIALIZING]
18-Jun-2015 08:57:03.158 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[Realm[org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy]] to
[INITIALIZED]
18-Jun-2015 08:57:03.158 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[Realm[org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy]] to
[STARTING_PREP]
18-Jun-2015 08:57:03.159 INFO [localhost-startStop-1] null.null
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.initialize
Tomcat7 Context-based policy agent
18-Jun-2015 08:57:03.159 INFO [localhost-startStop-1] null.null
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.initialize -
instantiate policy agent name:
org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
18-Jun-2015 08:57:03.373 SEVERE [localhost-startStop-1] null.null
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.startInternal
caught Throwable=java.lang.ExceptionInInitializerError
18-Jun-2015 08:57:03.376 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[Realm[org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy]] to
[FAILED]
18-Jun-2015 08:57:03.377 FINE [localhost-startStop-1]
org.apache.catalina.util.LifecycleBase.setStateInternal Setting state for
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/fortress
-web-1.0.9]] to [FAILED]
18-Jun-2015 08:57:03.377 SEVERE [localhost-startStop-1]
org.apache.catalina.core.ContainerBase.addChildInternal
ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/fortress
-web-1.0.9]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:
725)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:945)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1768)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component
[Realm[org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java
:5063)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 10 more
Caused by: org.apache.catalina.LifecycleException:
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.startInternal
caught Throwable=java.lang.ExceptionInInitializerError
at
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.startInternal(
Tc7AccessMgrProxy.java:246)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 12 more
18-Jun-2015 08:57:03.378 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web
application archive
/opt/polystar/fortress/apache-tomcat-8.0.22/webapps/fortress-web-1.0.9.war
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/fortress
-web-1.0.9]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:
728)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:945)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1768)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1
142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:
617)
at java.lang.Thread.run(Thread.java:745)
18-Jun-2015 08:57:03.381 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive
/opt/polystar/fortress/apache-tomcat-8.0.22/webapps/fortress-web-1.0.9.war
has finished in 3,167 ms
/Oleksandr
On 17/6/2015 01:09 , "Shawn McKinney" <[email protected]> wrote:
>
>
>> On Jun 16, 2015, at 5:27 PM, Oleksandr Bodriagov (Polystar)
>><[email protected]> wrote:
>>
>> No, it is not a latest snapshot of the fortress-web. It is fortress-web
>> with ³FC-105 - [fortress-web] - redundant null check² as a last commit.
>>
>> To make an RPM we have done the following:
>> 1. Created local branches for fortress-core/realm/rest/web using
>>originals
>> from 20th of May.
>> 2. A. Added build.properties to our local branch of the fortress-core
>> B. Modified pom.xml in the core so that it automatically performs "mvn
>> install -Dload.file=./ldap/setup/refreshLDAPData.xml² and ³mvn install
>> -Dload.file=./ldap/setup/DelegatedAdminManagerLoad.xml² by changing
>> executions in maven-antrun-plugin to <phase>install</phase> and <arg
>> file="./ldap/setup/refreshLDAPData.xml" /> or <arg
>> file="./ldap/setup/DelegatedAdminManagerLoad.xml" />
>> 3. All jars and wars are deployed to our Nexus server
>> 4. Fortress-web¹s pom.xml:
>> A. Copies build.properties from the core using the
>> maven-resources-plugin
>> B. Loads <arg file="./src/main/resources/FortressWebDemoUsers.xml" />
>> in <phase>install</phase>
>> 5. Fortress-rest¹s pom.xml:
>> A. Copies build.properties as well.
>> B. Changed maven-antrun-plugin to <phase>install</phase> and <arg
>> file="./src/main/resources/FortressRestServerPolicy.xml" />
>> 6. Created fortress-rpm (last execution step) that lists fortress-rest,
>> fortress-web, and fortress-realm-proxy as dependencies, contains
>>Tomcat¹s
>> tar.gz, and does the following:
>> A. Extracts tomcat
>> B. Adds ³default² users to tomcat-users.xml
>> C. Starts ApacheDS
>> D. Imports Fortress configuration apacheds-fortress.ldif to LDAP using
>> ldapadd utility
>> E. Deploys wars to webapps
>> F. Copies fortress-realm-proxy to lib
>> G. Starts Tomcat
>>
>> 7. Versions were increased simply because we made changes to pom.xml(s)
>> and did many releases
>>
>>
>> Have we missed something? I am concerned about executions defined with
>> maven-antrun-plugin.
>>
>
>The maven-antrun now executes during mvn install correct? Why are you
>concerned about it - did you see an error during that phase?
>
>My next question is have you successfully run this particular build
>outside of the rpm test? I¹m also wondering why we¹re not getting a more
>detailed log message from tomcat. Can you change the log4j.properties to
>get more detail? (i.e. set the default level to debug).
>
>> On Jun 16, 2015, at 5:27 PM, Oleksandr Bodriagov (Polystar)
>><[email protected]> wrote:
>>
>> When do you plan to release the fortress-master that automates and
>> incorporates other fortress projects?
>
>It is required for next release. Will need to discuss with team, not a
>lot of work but requires moving git repos around - probably some low
>number of weeks.
>
>> On Jun 16, 2015, at 5:27 PM, Oleksandr Bodriagov (Polystar)
>><[email protected]> wrote:
>>
>> How to make fortress-rest run in https mode?
>
>Need to run a test and refresh my memory on how its done and then
>document. Maybe add it to the Apache Fortress Demo as another test case.
> As I recall it was just a matter of setting up Tomcat for HTTPS and then
>changing the URL on the client side. Speaking of - what do you use as
>fortress-rest client test harness?
>
>I recommend posting another question to this list for this issue.
>
>Shawn
>[email protected]
