Jboss Failed to instantiate class org.jboss.logmanager.handlers.PeriodicRotatingFileHandle

Question

When I tried to install jbosseap6.3 as a service. I got the error below. Does anyone have an idea of ​​the error below. Any shedding light means it is very helpful to me.

java.lang.IllegalArgumentException: Failed to instantiate class "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler" for handler "FILE" at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:119) at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:338) at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:291) at org.jboss.logmanager.config.LogContextConfigurationImpl.commit(LogContextConfigurationImpl.java:300) at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:542) at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97) at org.jboss.as.logging.logmanager.ConfigurationPersistence.configure(ConfigurationPersistence.java:149) at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:300) at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:262) at java.util.logging.LogManager$3.run(LogManager.java:399) at java.util.logging.LogManager$3.run(LogManager.java:396) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396) at java.util.logging.LogManager.access$800(LogManager.java:145) at java.util.logging.LogManager$2.run(LogManager.java:345) at java.security.AccessController.doPrivileged(Native Method) at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338) at java.util.logging.LogManager.getLogManager(LogManager.java:378) at org.jboss.modules.Main.main(Main.java:443) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:117) ... 18 more Caused by: java.io.FileNotFoundException: C:\jboss-eap-6.3\standalone\log\server.log (The process cannot access the file because it is being used by another process) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:154) at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.setFile(PeriodicRotatingFileHandler.java:105) at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:192) at org.jboss.logmanager.handlers.FileHandler.<init>(FileHandler.java:122) at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.<init>(PeriodicRotatingFileHandler.java:73) ... 23 more Shutdown JBossEAP6.3.0 service [2015-05-29 09:58:27] 

Answer 1

Try starting the jBoss server as an administrator by right-clicking, this will allow jboss to create all folders and files.

Answer 2

Right-click the Jboss EA installation directory (my file is C: \ program files \ EAP6.1, then the tab "Properties", "Security". Given all the permissions on this folder (all the users you see just give full control) Then you can create log files, etc. in the required folder, but this is just a workaround, although it works only for local installations.

Answer 3

I solved this problem by creating a log directory in C: \ jboss-eap-6.3 \ standalone \

Answer 4

I had the same problem, it worked after the launch in the root, maybe you are launching it without proper rights.

Answer 5

Most likely you will get this error because you either have the log file open in a text editor or this instance of JBoss is already running.

Answer 6

This is a permission issue, the solution that worked for me is that I deleted the jboss wildfly home directory from C: \ programs in C: \