directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FC-92) Remove debug flag from context.xml
Date Tue, 21 Apr 2015 13:09:58 GMT
Shawn McKinney created FC-92:
--------------------------------

             Summary: Remove debug flag from context.xml
                 Key: FC-92
                 URL: https://issues.apache.org/jira/browse/FC-92
             Project: FORTRESS
          Issue Type: Bug
    Affects Versions: 1.0.0-RC39
            Reporter: Shawn McKinney
             Fix For: 1.0.0-RC40


Fortress web and rest use context.xml for tomcat realm integration.  In it is a flags, debug
and resourceName, that are not mapped to realm.  This is causing error in tomcat 8.18:

<Context reloadable="true">
    <Realm className="org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy"
           debug="0"
           resourceName="UserDatabase"
           defaultRoles=""
           containerType="TomcatContext"
           realmClasspath=""
            />
</Context>

Since these flags are not used, they should be removed.

[ERROR] Failed to execute goal
org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project
fortress-rest: Cannot invoke Tomcat manager: Error writing to server ->
[Help 1]

If I do it manually I get the following error in catalina logs:

21-Apr-2015 12:15:48.625 INFO [localhost-startStop-2]
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application
archive /usr/local/apache-tomcat-8.0.21/webapps/fortress-rest.war
21-Apr-2015 12:15:48.629 WARNING [localhost-startStop-2]
org.apache.tomcat.util.digester.SetPropertiesRule.begin
[SetPropertiesRule]{Context/Realm} Setting property 'debug' to '0' did not
find a matching property.
21-Apr-2015 12:15:48.630 WARNING [localhost-startStop-2]
org.apache.tomcat.util.digester.SetPropertiesRule.begin
[SetPropertiesRule]{Context/Realm} Setting property 'resourceName' to
'UserDatabase' did not find a matching property.
21-Apr-2015 12:15:48.630 INFO [localhost-startStop-2] null.null
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.setDefaultRole
s <>
21-Apr-2015 12:15:48.630 INFO [localhost-startStop-2]
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.setContainerTy
pe 
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.setContainerTy
pe <TomcatContext>
21-Apr-2015 12:15:48.630 INFO [localhost-startStop-2]
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.setRealmClassp
ath 
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.setRealmClassp
ath <>
21-Apr-2015 12:15:49.194 INFO [localhost-startStop-2]
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.initialize
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.initialize
Tomcat7 Context-based policy agent
21-Apr-2015 12:15:49.194 INFO [localhost-startStop-2]
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.initialize
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.initialize -
instantiate policy agent name:
org.apache.directory.fortress.realm.tomcat.TcAccessMgrImpl
21-Apr-2015 12:15:50.034 INFO [localhost-startStop-2]
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy.initialize
org.apache.directory.fortress.realm.tomcat.Tc7AccessMgrProxy J2EE Tomcat7
policy agent initialization successful
21-Apr-2015 12:15:52.130 WARNING [localhost-startStop-2]
org.apache.catalina.startup.ContextConfig.validateSecurityRoles Security
role name fortress-rest-user used in an <auth-constraint> without being
defined in a <security-role>
21-Apr-2015 12:15:53.039 SEVERE [localhost-startStop-2]
org.apache.catalina.core.StandardContext.startInternal Error listenerStart
21-Apr-2015 12:15:53.039 SEVERE [localhost-startStop-2]
org.apache.catalina.core.StandardContext.startInternal Context
[/fortress-rest] startup failed due to previous errors
21-Apr-2015 12:15:53.048 WARNING [localhost-startStop-2]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [fortress-rest] appears to have started a thread named
[pool-29-thread-1] but has failed to stop it. This is very likely to
create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(Synchrono
usQueue.java:460)
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQu
eue.java:362)
java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941)
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:10
66)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1127)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:617)
java.lang.Thread.run(Thread.java:745)
21-Apr-2015 12:15:53.048 WARNING [localhost-startStop-2]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [fortress-rest] appears to have started a thread named
[NioProcessor-1] but has failed to stop it. This is very likely to create
a memory leak. Stack trace of thread:
sun.nio.ch.KQueueArrayWrapper.kevent0(Native Method)
sun.nio.ch.KQueueArrayWrapper.poll(KQueueArrayWrapper.java:198)
sun.nio.ch.KQueueSelectorImpl.doSelect(KQueueSelectorImpl.java:103)
sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
org.apache.mina.transport.socket.nio.NioProcessor.select(NioProcessor.java
:72)
org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(Abst
ractPollingIoProcessor.java:1077)
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.jav
a:64)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:617)
java.lang.Thread.run(Thread.java:745)
21-Apr-2015 12:15:53.049 WARNING [localhost-startStop-2]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [fortress-rest] appears to have started a thread named
[fortress-rest] but has failed to stop it. This is very likely to create a
memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:552)
java.util.TimerThread.run(Timer.java:505)
21-Apr-2015 12:15:53.049 WARNING [localhost-startStop-2]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [fortress-rest] appears to have started a thread named
[Statistics Thread-fortress-rest-1] but has failed to stop it. This is
very likely to create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awai
tNanos(AbstractQueuedSynchronizer.java:2078)
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Sch
eduledThreadPoolExecutor.java:1093)
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Sch
eduledThreadPoolExecutor.java:809)
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:10
67)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
1127)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:617)
java.lang.Thread.run(Thread.java:745)
21-Apr-2015 12:15:53.052 INFO [localhost-startStop-2]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive
/usr/local/apache-tomcat-8.0.21/webapps/fortress-rest.war has finished in
4,427 ms




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message