Created attachment 924558 [details] Server.log Description of problem: Warning in server.log file after clean install and server start: WARN [org.jboss.security] (Periodic Recovery) PBOX000231: End loadConfig, failed to load config: file:/home/hudson/jon-server-3.3.0.DR01/jbossas/bin/login-config.xml: java.io.FileNotFoundException: /home/hudson/jon-server-3.3.0.DR01/jbossas/bin/login-config.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) [rt.jar:1.7.0_45] at java.io.FileInputStream.<init>(FileInputStream.java:146) [rt.jar:1.7.0_45] at java.io.FileInputStream.<init>(FileInputStream.java:101) [rt.jar:1.7.0_45] at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) [rt.jar:1.7.0_45] at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) [rt.jar:1.7.0_45] at java.net.URL.openStream(URL.java:1037) [rt.jar:1.7.0_45] at org.jboss.security.auth.login.XMLLoginConfigImpl.loadSunConfig(XMLLoginConfigImpl.java:420) [picketbox-4.0.19.SP8-redhat-1.jar:4.0.19.SP8-redhat-1] at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:388) [picketbox-4.0.19.SP8-redhat-1.jar:4.0.19.SP8-redhat-1] at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:364) [picketbox-4.0.19.SP8-redhat-1.jar:4.0.19.SP8-redhat-1] at org.jboss.security.auth.login.XMLLoginConfigImpl.getAppConfigurationEntry(XMLLoginConfigImpl.java:127) [picketbox-4.0.19.SP8-redhat-1.jar:4.0.19.SP8-redhat-1] at javax.security.auth.login.LoginContext.init(LoginContext.java:260) [rt.jar:1.7.0_45] at javax.security.auth.login.LoginContext.<init>(LoginContext.java:382) [rt.jar:1.7.0_45] at javax.security.auth.login.LoginContext.<init>(LoginContext.java:459) [rt.jar:1.7.0_45] Version-Release number of selected component (if applicable): JON 3.3 DR01 How reproducible: Steps to Reproduce: 1. Install and start JON 2. 3. Actual results: Warnings in server.log after clean install/start. Expected results: Should be zero silent Warnings in server.log Additional info:
This hasn't been seen in later releases. Please re-open if seen again.
This was again reported in Bug 1144998, marking this duplicate of that bug. *** This bug has been marked as a duplicate of bug 1144998 ***