Closed GoogleCodeExporter closed 9 years ago
Hello,
I Have the same problem.
Have you find the solution?
Original comment by houda.ja...@gmail.com
on 31 Jul 2012 at 9:47
Please post the tomcat log.
Original comment by jrivard
on 5 Aug 2012 at 4:06
8 07, 2012 10:24:40 午前 org.apache.catalina.core.AprLifecycleListener init
情報: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the java.library.path:
C:\Program
Files\Java\jre7\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Pr
ogram Files/Java/jre7/bin/client;C:/Program Files/Java/jre7/bin;C:/Program
Files/Java/jre7/lib/i386;C:\Program Files\Common Files\Microsoft Shared\Windows
Live;C:\Program Files\Dell\DW WLAN
Card;;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System3
2\WindowsPowerShell\v1.0\;C:\Program Files\Windows7Master;C:\Program
Files\Common Files\Thunder Network\KanKan\Codecs;C:\Program
Files\WIDCOMM\Bluetooth Software\;C:\Program Files\NTRU Cryptosystems\NTRU TCG
Software Stack\bin\;C:\Program Files\Windows Live\Shared;C:\Program
Files\TortoiseSVN\bin;C:\Program Files\Java\jdk1.7.0_05\bin;D:\eclipse;;.
8 07, 2012 10:24:41 午前 org.apache.tomcat.util.digester.SetPropertiesRule
begin
警告: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
property 'source' to 'org.eclipse.jst.jee.server:pwm' did not find a matching
property.
8 07, 2012 10:24:41 午前 org.apache.tomcat.util.digester.Digester endElement
警告: No rules found matching
'Server/Service/Engine/Host/Context/init-param/param-name'.
8 07, 2012 10:24:41 午前 org.apache.tomcat.util.digester.Digester endElement
警告: No rules found matching
'Server/Service/Engine/Host/Context/init-param/param-value'.
8 07, 2012 10:24:41 午前 org.apache.tomcat.util.digester.Digester endElement
警告: No rules found matching
'Server/Service/Engine/Host/Context/init-param'.
8 07, 2012 10:24:41 午前 org.apache.coyote.AbstractProtocol init
情報: Initializing ProtocolHandler ["http-bio-8080"]
8 07, 2012 10:24:41 午前 org.apache.coyote.AbstractProtocol init
情報: Initializing ProtocolHandler ["ajp-bio-8009"]
8 07, 2012 10:24:41 午前 org.apache.catalina.startup.Catalina load
情報: Initialization processed in 1451 ms
8 07, 2012 10:24:41 午前 org.apache.catalina.core.StandardService
startInternal
情報: サービス Catalina を起動します
8 07, 2012 10:24:41 午前 org.apache.catalina.core.StandardEngine startInternal
情報: Starting Servlet Engine: Apache Tomcat/7.0.29
8 07, 2012 10:24:42 午前 org.apache.catalina.util.SessionIdGenerator
createSecureRandom
情報: Creation of SecureRandom instance for session ID generation using
[SHA1PRNG] took [106] milliseconds.
log4j:WARN No appenders could be found for logger
(password.pwm.config.ConfigurationReader).
log4j:WARN Please initialize the log4j system properly.
2012-08-07 10:24:52, DEBUG, pwm.PwmApplication, successfully initialized
default log4j config at log level TRACE
2012-08-07 10:24:52, WARN , pwm.PwmApplication, skipping pwmDB open due to
application mode NEW
2012-08-07 10:24:53, WARN , pwm.PwmApplication, unable to initialize
pwmDBLogger: PwmDB cannot be null
2012-08-07 10:24:53, INFO , pwm.PwmApplication, initializing pwm
2012-08-07 10:24:53, INFO , pwm.PwmApplication, loaded configuration:
2012-08-07 10:24:53, INFO , pwm.PwmApplication, loaded pwm global password
policy: PwmPasswordPolicy: {MinimumLowerCase=0, MinimumSpecial=0,
MaximumOldChars=0, MaximumUpperCase=0, MaximumNumeric=0, EnableWordlist=true,
RegExMatch=, MinimumUnique=0, MinimumNonAlpha=0, DisallowedAttributes=[cn,
givenName, sn], MinimumStrength=0, AllowNumeric=true, ChangeMessage=,
MinimumAlpha=0, MaximumLowerCase=0, AllowSpecial=true, ADComplexity=false,
MaximumLength=64, MaximumRepeat=0, AllowFirstCharNumeric=true, MinimumLength=2,
MaximumSequentialRepeat=0, AllowLastCharSpecial=true, MinimumNumeric=0,
MaximumAlpha=0, RegExNoMatch=, MaximumNonAlpha=0, MaximumSpecial=0,
MinimumUpperCase=0, AllowFirstCharSpecial=true, DisallowedValues=[password,
test], AllowLastCharNumeric=true}
2012-08-07 10:24:53, INFO , pwm.PwmApplication, generated new random instanceID
2B45C163FC7926BD
2012-08-07 10:24:53, INFO , pwm.PwmApplication, using '2B45C163FC7926BD' for
this pwm instance's ID (instanceID)
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, this pwm instance first
installed on Tue Aug 07 10:24:53 CST 2012
2012-08-07 10:24:53, INFO , pwm.PwmApplication, environment info:
java.vm.vendor=Oracle Corporation, java.vm.version=23.1-b03, java.vm.name=Java
HotSpot(TM) Client VM, java.home=C:\Program Files\Java\jre7, memmax=259522560,
threads=3, ldapChai API version: 0.6.2 release, b743
2012-08-07 10:24:53, INFO , pwm.PwmApplication, debug info:, memfree=77147776,
memallocd=259522560, memmax=259522560, threads=3
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.wordlist.SharedHistoryManager
2012-08-07 10:24:53, INFO , wordlist.SharedHistoryManager, pwmDB is not
available, will remain closed
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.wordlist.SharedHistoryManager has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.util.db.DatabaseAccessor
2012-08-07 10:24:53, DEBUG, db.DatabaseAccessor, skipping database connection
open, no connection parameters configured
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.util.db.DatabaseAccessor has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.health.HealthMonitor
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.health.HealthMonitor has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.util.stats.StatisticsManager
2012-08-07 10:24:53, ERROR, stats.StatisticsManager, pwmDB is not available,
will remain closed
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.util.stats.StatisticsManager has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.wordlist.WordlistManager
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.wordlist.WordlistManager has completed successfully
2012-08-07 10:24:53, DEBUG, wordlist.WordlistManager, Pwm-wordlist starting up
in background thread
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.wordlist.SeedlistManager
2012-08-07 10:24:53, WARN , wordlist.WordlistManager, pwmDB is not available,
Pwm-wordlist will remain closed
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.wordlist.SeedlistManager has completed successfully
2012-08-07 10:24:53, DEBUG, wordlist.SeedlistManager, Pwm-seedist starting up
in background thread
2012-08-07 10:24:53, WARN , wordlist.SeedlistManager, pwmDB is not available,
Pwm-seedist will remain closed
2012-08-07 10:24:53, DEBUG, wordlist.WordlistManager, closed
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.util.EmailQueueManager
2012-08-07 10:24:53, DEBUG, wordlist.SeedlistManager, closed
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.util.EmailQueueManager has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.util.SmsQueueManager
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.util.SmsQueueManager has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.util.UrlShortenerService
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.util.UrlShortenerService has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.TokenManager
2012-08-07 10:24:53, TRACE, pwm.TokenManager, opening
2012-08-07 10:24:53, ERROR, pwm.TokenManager, 5055 ERROR_INVALID_SECURITY_KEY
(unable to start token manager: PWM Security Key value is not configured)
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.TokenManager has completed successfully
2012-08-07 10:24:53, DEBUG, pwm.PwmApplication, initializing service
password.pwm.VersionChecker
2012-08-07 10:24:53, TRACE, pwm.VersionChecker, sending cloud version request
to: https://pwm-cloud.appspot.com/rest/pwm/current-version
2012-08-07 10:25:15, ERROR, pwm.VersionChecker, 5054
ERROR_UNREACHABLE_CLOUD_SERVICE (unable to reach version check service
'https://pwm-cloud.appspot.com/rest/pwm/current-version', error: Connection to
https://pwm-cloud.appspot.com refused)
2012-08-07 10:25:15, ERROR, pwm.VersionChecker, unable to retrieve current
version data from cloud: java.lang.NumberFormatException: For input string: ""
2012-08-07 10:25:15, DEBUG, pwm.PwmApplication, initialization of service
password.pwm.VersionChecker has completed successfully
2012-08-07 10:25:15, INFO , pwm.PwmApplication, PWM v1.6.2 b1175 (release) open
for bidness! (22s)
2012-08-07 10:25:15, DEBUG, pwm.PwmApplication, buildTime=2012.07.14 17:52:09
EDT, javaLocale=ja_JP, pwmDefaultLocale=
2012-08-07 10:25:15, ERROR, util.PwmMacroMachine, unable to parse
configured/detected site URL: no protocol: [UNCONFIGURED_URL]
2012-08-07 10:25:15, WARN , pwm.PwmApplication, unable to add email to queue:
5039 ERROR_CLOSING
8 07, 2012 10:25:15 午前 com.sun.jersey.api.core.PackagesResourceConfig init
情報: Scanning for root resource and provider classes in the packages:
password.pwm.ws.server.rest
8 07, 2012 10:25:15 午前 com.sun.jersey.api.core.ScanningResourceConfig
logClasses
情報: Root resource classes found:
class password.pwm.ws.server.rest.RestHealthServer
class password.pwm.ws.server.rest.RestClearResponsesServer
class password.pwm.ws.server.rest.RestRandomPasswordServer
class password.pwm.ws.server.rest.RestCheckPasswordServer
class password.pwm.ws.server.rest.RestStatisticsServer
class password.pwm.ws.server.rest.RestSetPasswordServer
8 07, 2012 10:25:15 午前 com.sun.jersey.api.core.ScanningResourceConfig init
情報: No provider classes found.
8 07, 2012 10:25:15 午前
com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
情報: Initiating Jersey application, version 'Jersey: 1.12 02/15/2012 05:30
PM'
8 07, 2012 10:25:17 午前 org.apache.coyote.AbstractProtocol start
情報: Starting ProtocolHandler ["http-bio-8080"]
8 07, 2012 10:25:17 午前 org.apache.coyote.AbstractProtocol start
情報: Starting ProtocolHandler ["ajp-bio-8009"]
8 07, 2012 10:25:17 午前 org.apache.catalina.startup.Catalina start
情報: Server startup in 36880 ms
2012-08-07 10:25:38, TRACE, pwm.EventManager, {0} http session created
2012-08-07 10:25:38, DEBUG, pwm.PwmApplication, ignoring loopback host during
autoSiteURL detection: http://127.0.0.1:8080/pwm/
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} http session headers:
[127.0.0.1]
accept=text/html, application/xhtml+xml, */*
accept-language=ja-JP
user-agent=Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
accept-encoding=gzip, deflate
host=127.0.0.1:8080
connection=Keep-Alive
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} GET request for: /pwm/ (no
params) [127.0.0.1]
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} user locale set to 'ja'
[127.0.0.1]
2012-08-07 10:25:38, DEBUG, pwm.SessionFilter, {0} unable to find a valid
configuration, redirecting to ConfigManager [127.0.0.1]
2012-08-07 10:25:38, DEBUG, pwm.PwmApplication, ignoring loopback host during
autoSiteURL detection: http://127.0.0.1:8080/pwm/config/ConfigManager
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} GET request for:
/pwm/config/ConfigManager (no params) [127.0.0.1]
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} session has not been
validated, redirecting with verification key to
http://127.0.0.1:8080/pwm/config/ConfigManager?session_verificiation_key=CJKEWFa
LGYOMSE0F9RxYbwuwTa1H8VPK138fee6da6d [127.0.0.1]
2012-08-07 10:25:38, DEBUG, pwm.PwmApplication, ignoring loopback host during
autoSiteURL detection: http://127.0.0.1:8080/pwm/config/ConfigManager
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} GET request for:
/pwm/config/ConfigManager [127.0.0.1]
session_verificiation_key='CJKEWFaLGYOMSE0F9RxYbwuwTa1H8VPK138fee6da6d'
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} session validated,
redirecting to original request url:
http://127.0.0.1:8080/pwm/config/ConfigManager? [127.0.0.1]
2012-08-07 10:25:38, DEBUG, pwm.PwmApplication, ignoring loopback host during
autoSiteURL detection: http://127.0.0.1:8080/pwm/config/ConfigManager
2012-08-07 10:25:38, TRACE, pwm.SessionFilter, {0} GET request for:
/pwm/config/ConfigManager (no params) [127.0.0.1]
2012-08-07 10:25:38, DEBUG, servlet.ConfigManagerServlet, {0} initializing
configuration bean with configMode=NEW [127.0.0.1]
8 07, 2012 10:25:38 午前 org.apache.catalina.core.ApplicationContext log
情報: サーブレット pwmVariablesJS
を利用不可能にマークします
8 07, 2012 10:25:38 午前 org.apache.catalina.core.StandardWrapperValve invoke
重大: サーブレット pwmVariablesJS に例外を割り当てます
javax.servlet.ServletException: サーブレット pwmVariablesJS
に指定されたサーブレットクラスがありません
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1130)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:857)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:136)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2012-08-07 10:25:38, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/themes/default/pwmMobileStyle.css (no params)
(gzip) [127.0.0.1]
2012-08-07 10:25:38, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/pwmMobileStyle.css (no params) (gzip) [127.0.0.1]
2012-08-07 10:25:38, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/themes/default/pwmStyle.css (no params) (gzip)
[127.0.0.1]
2012-08-07 10:25:38, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/pwmStyle.css (no params) (gzip) [127.0.0.1]
2012-08-07 10:25:38, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/pwmHelper.js (no params) (gzip) [127.0.0.1]
2012-08-07 10:25:38, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/dojo/dijit/themes/nihilo/nihilo.css (no params)
(gzip) [127.0.0.1]
2012-08-07 10:25:39, ERROR, servlet.ResourceFileServlet, {0} error fulfilling
response for url '/pwm/resources/dojo/dojo/dojo.js', error: null [127.0.0.1]
2012-08-07 10:25:39, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/pwmStyle.css (no params) (cached, gzip)
[127.0.0.1]
2012-08-07 10:25:39, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/dojo/dijit/themes/nihilo/nihilo.css (no params)
(cached, gzip) [127.0.0.1]
2012-08-07 10:25:39, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/themes/default/pwmMobileStyle.css (no params)
(cached, gzip) [127.0.0.1]
2012-08-07 10:25:39, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/pwmHelper.js (no params) (cached, gzip)
[127.0.0.1]
2012-08-07 10:25:39, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/dojo/dojo/dojo.js (no params) (cached, gzip)
[127.0.0.1]
2012-08-07 10:25:39, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/header-gradient.gif (no params) (not cached)
[127.0.0.1]
2012-08-07 10:25:39, TRACE, servlet.ResourceFileServlet, {0} GET request for:
/pwm/resources/nonce-h5kd9a5w/favicon.ico (no params) (not cached) [127.0.0.1]
Original comment by wuhe...@gmail.com
on 7 Aug 2012 at 2:27
Hello Team,
I'm getting the same error see attachment
OS: Windows Server 2008 R2 SP1 64-bit
Tomcat: 7.0.29
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b06)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)
Best Regards
Original comment by alek...@gmail.com
on 8 Aug 2012 at 3:39
Attachments:
To date, I've been unable to reproduce this on any platform. The single
exception in the trace on comment #3 is likely the cause, but does not give any
clues as to the actual root cause. Do you see any errors or stack traces in
any other tomcat log file?
Original comment by jrivard
on 8 Aug 2012 at 3:42
I uninstalled the application and I installed it again and I'm getting the
following logs in Tomcat.
I'm maybe missing some configuration but I'm not sure.
Aug 08, 2012 11:51:21 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\apache-tomcat-7.0.29\webapps\pwm.war
Aug 08, 2012 11:51:21 AM org.apache.tomcat.util.digester.Digester endElement
WARNING: No rules found matching 'Context/init-param/param-name'.
Aug 08, 2012 11:51:21 AM org.apache.tomcat.util.digester.Digester endElement
WARNING: No rules found matching 'Context/init-param/param-value'.
Aug 08, 2012 11:51:21 AM org.apache.tomcat.util.digester.Digester endElement
WARNING: No rules found matching 'Context/init-param'.
log4j:WARN No appenders could be found for logger (password.pwm.config.Configura
tionReader).
log4j:WARN Please initialize the log4j system properly.
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, successfully initialized default
log4j config at log level TRACE
2012-08-08 11:51:31, WARN , pwm.PwmApplication, skipping pwmDB open due to appli
cation mode NEW
2012-08-08 11:51:31, WARN , pwm.PwmApplication, unable to initialize pwmDBLogger
: PwmDB cannot be null
2012-08-08 11:51:31, INFO , pwm.PwmApplication, initializing pwm
2012-08-08 11:51:31, INFO , pwm.PwmApplication, loaded configuration:
2012-08-08 11:51:31, INFO , pwm.PwmApplication, loaded pwm global password polic
y: PwmPasswordPolicy: {MinimumLowerCase=0, MinimumSpecial=0, MaximumOldChars=0,
MaximumUpperCase=0, MaximumNumeric=0, EnableWordlist=true, RegExMatch=, MinimumU
nique=0, MinimumNonAlpha=0, DisallowedAttributes=[cn, givenName, sn], MinimumStr
ength=0, AllowNumeric=true, ChangeMessage=, MinimumAlpha=0, MaximumLowerCase=0,
AllowSpecial=true, ADComplexity=false, MaximumLength=64, MaximumRepeat=0, AllowF
irstCharNumeric=true, MinimumLength=2, MaximumSequentialRepeat=0, AllowLastCharS
pecial=true, MinimumNumeric=0, MaximumAlpha=0, RegExNoMatch=, MaximumNonAlpha=0,
MaximumSpecial=0, MinimumUpperCase=0, AllowFirstCharSpecial=true, DisallowedVal
ues=[password, test], AllowLastCharNumeric=true}
2012-08-08 11:51:31, INFO , pwm.PwmApplication, generated new random instanceID
3F282929D56054F1
2012-08-08 11:51:31, INFO , pwm.PwmApplication, using '3F282929D56054F1' for thi
s pwm instance's ID (instanceID)
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, this pwm instance first installe
d on Wed Aug 08 11:51:31 EDT 2012
2012-08-08 11:51:31, INFO , pwm.PwmApplication, environment info: java.vm.vendor
=Oracle Corporation, java.vm.version=23.1-b03, java.vm.name=Java HotSpot(TM) 64-
Bit Server VM, java.home=C:\Program Files\Java\jdk1.7.0_05\jre, memmax=477233152
, threads=43, ldapChai API version: 0.6.3 devbuild, b744
2012-08-08 11:51:31, INFO , pwm.PwmApplication, debug info:, memfree=134620504,
memallocd=270991360, memmax=477233152, threads=43
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.wordlist.SharedHistoryManager
2012-08-08 11:51:31, INFO , wordlist.SharedHistoryManager, pwmDB is not availabl
e, will remain closed
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.wordlist.SharedHistoryManager has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.util.db.DatabaseAccessor
2012-08-08 11:51:31, DEBUG, db.DatabaseAccessor, skipping database connection op
en, no connection parameters configured
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.util.db.DatabaseAccessor has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.health.HealthMonitor
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.health.HealthMonitor has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.util.stats.StatisticsManager
2012-08-08 11:51:31, ERROR, stats.StatisticsManager, pwmDB is not available, wil
l remain closed
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.util.stats.StatisticsManager has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.wordlist.WordlistManager
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.wordlist.WordlistManager has completed successfully
2012-08-08 11:51:31, DEBUG, wordlist.WordlistManager, Pwm-wordlist starting up i
n background thread
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.wordlist.SeedlistManager
2012-08-08 11:51:31, WARN , wordlist.WordlistManager, pwmDB is not available, Pw
m-wordlist will remain closed
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.wordlist.SeedlistManager has completed successfully
2012-08-08 11:51:31, DEBUG, wordlist.SeedlistManager, Pwm-seedist starting up in
background thread
2012-08-08 11:51:31, WARN , wordlist.SeedlistManager, pwmDB is not available, Pw
m-seedist will remain closed
2012-08-08 11:51:31, DEBUG, wordlist.WordlistManager, closed
2012-08-08 11:51:31, DEBUG, wordlist.SeedlistManager, closed
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.util.EmailQueueManager
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.util.EmailQueueManager has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.util.SmsQueueManager
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.util.SmsQueueManager has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.util.UrlShortenerService
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.util.UrlShortenerService has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.TokenManager
2012-08-08 11:51:31, TRACE, pwm.TokenManager, opening
2012-08-08 11:51:31, ERROR, pwm.TokenManager, 5055 ERROR_INVALID_SECURITY_KEY (u
nable to start token manager: PWM Security Key value is not configured)
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.TokenManager has completed successfully
2012-08-08 11:51:31, DEBUG, pwm.PwmApplication, initializing service password.pw
m.VersionChecker
2012-08-08 11:51:31, TRACE, pwm.VersionChecker, sending cloud version request to
: https://pwm-cloud.appspot.com/rest/pwm/current-version
2012-08-08 11:51:32, INFO , pwm.VersionChecker, version check to https://pwm-clo
ud.appspot.com/rest/pwm/current-version completed, current-build=1181, current-v
ersion=v1.6.3
2012-08-08 11:51:32, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.VersionChecker has completed successfully
2012-08-08 11:51:32, DEBUG, pwm.PwmApplication, initializing service password.pw
m.util.IntruderManager
2012-08-08 11:51:32, DEBUG, pwm.PwmApplication, initialization of service passwo
rd.pwm.util.IntruderManager has completed successfully
2012-08-08 11:51:32, INFO , pwm.PwmApplication, PWM v1.6.3 b1181 (release) open
for bidness! (167ms)
2012-08-08 11:51:32, DEBUG, pwm.PwmApplication, buildTime=2012.08.06 15:09:31 ED
T, javaLocale=en_US, pwmDefaultLocale=
2012-08-08 11:51:32, ERROR, util.PwmMacroMachine, unable to parse configured/det
ected site URL: no protocol: [UNCONFIGURED_URL]
2012-08-08 11:51:32, WARN , pwm.PwmApplication, unable to add email to queue: 50
39 ERROR_CLOSING
Aug 08, 2012 11:51:32 AM com.sun.jersey.api.core.PackagesResourceConfig init
INFO: Scanning for root resource and provider classes in the packages:
password.pwm.ws.server.rest
Aug 08, 2012 11:51:32 AM com.sun.jersey.api.core.ScanningResourceConfig logClass
es
INFO: Root resource classes found:
class password.pwm.ws.server.rest.RestClearResponsesServer
class password.pwm.ws.server.rest.RestSetPasswordServer
class password.pwm.ws.server.rest.RestCheckPasswordServer
class password.pwm.ws.server.rest.RestStatisticsServer
class password.pwm.ws.server.rest.RestHealthServer
class password.pwm.ws.server.rest.RestRandomPasswordServer
Aug 08, 2012 11:51:32 AM com.sun.jersey.api.core.ScanningResourceConfig init
INFO: No provider classes found.
Aug 08, 2012 11:51:32 AM com.sun.jersey.server.impl.application.WebApplicationIm
pl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.12 02/15/2012 05:30 PM'
Best Regards
Original comment by alek...@gmail.com
on 8 Aug 2012 at 4:01
This thread seems to be relevant:
http://www.coderanch.com/t/537064/java-Web-Component-SCWCD/certification/jsp-fil
e-tag-web-xml
Original comment by jrivard
on 9 Aug 2012 at 1:44
Hello folks,
I have exact same situation. I can't finish pwm configuration.
Any selection return me to the /pwm/config/ConfigManager?# link.
Menu is not visible for me also.
Windows 2008 R2 SP1,
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b06)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)
tomcat 7.0.29
pwm 1.6.3
Original comment by al.m...@gmail.com
on 9 Aug 2012 at 2:29
Attachments:
Comment 7 have the key to fix my issue. I went to "..\webapps\pwm\WEB-INF" and
edited the file web.xml by deleting metadata-complete="true" attribute, hit F5
in the browser and walla!! everything works.
Thank you guys for all the help.
Original comment by alek...@gmail.com
on 9 Aug 2012 at 3:06
-------------
Tomcat 7.0.29 Released 2012-07-08
The Apache Tomcat Project is proud to announce the release of version 7.0.29 of
Apache Tomcat. This release corrects a small number of regressions introduced
in the 7.0.28 release and takes account of several recent clarifications from
the Servlet Expert Group as well as containing a handful of bug fixes and small
improvements compared to version 7.0.28. The notable changes include:
Add support for a default error page
The servlet version defined in web.xml no longer determines if Tomcat scans for
annotations when the web application starts. This is now solely controlled by
metadata-complete element.
On web application start, JARs are now always scanned for
ServletContainerInitializers regardless of the setting of metadata-complete
Full details of these changes, and all the other changes, are available in the
Tomcat 7 changelog.
------------
sure, before Tomcat 7.0.29 the "metadata-complete" is regardless, this is the
problem.
Original comment by wuhe...@gmail.com
on 9 Aug 2012 at 5:44
In my case and probably the same for "Comment 8" we are using Tomcat 7.0.29,
and the problem with the "metadata-complete" is still there.
Original comment by alek...@gmail.com
on 9 Aug 2012 at 1:08
alekorl: so your saying you remove the metadata-complete from the web.xml and
you still see the problem?
Original comment by jrivard
on 9 Aug 2012 at 1:10
Sorry if I didn't explained myself correctly. The problem with the
metadata-complete remains in Tomcat 7.0.29 until it is remove from web.xml
Original comment by alek...@gmail.com
on 9 Aug 2012 at 1:26
related:
https://issues.apache.org/bugzilla/show_bug.cgi?id=53574
Seems to be tomcat 7.0.29. Unclear if it's a bug in 7.0.29, or a strengthing
of the server spec. Still investigating workarounds. Setting medata-complete
seems undesirable in general.
Original comment by jrivard
on 10 Aug 2012 at 1:56
Thank you very much!
Removing metadata-complete="true" from web.xml was help!!!
Now it's work!
Original comment by al.m...@gmail.com
on 10 Aug 2012 at 11:16
From the following comment, it's confirmed this is a bug in Tomcat v7.0.29.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53574#c3
Thus, this will be an incompatibility with PWM and Tomcat v7.0.29. Workarounds
are:
1) Use Tomcat v7.0.28 or v7.0.30 or greater (when its available)
2) Edit PWM's "WEB-INF/web.xml" to remove the metadata-complete="true"
attribute.
Original comment by jrivard
on 13 Aug 2012 at 2:20
Issue 239 has been merged into this issue.
Original comment by jrivard
on 22 Aug 2012 at 11:00
Issue 265 has been merged into this issue.
Original comment by jrivard
on 23 Aug 2012 at 5:30
v1.6.4 includes a workaround for this issue and should work with Apache Tomcat
7.0.29.
Original comment by jrivard
on 23 Aug 2012 at 10:12
Original issue reported on code.google.com by
danza...@gmail.com
on 19 Jul 2012 at 2:49Attachments: