CODEWITHSUNDEEP
javawildfly-10
BenRowley
BenRowley

Reputation: 24

Error starting Wildfly 10.0.0.Final

I haven't been able to find a specific answer to what could be causing this issue though I am hoping it is something quite simple.

Issue. I have installed version 10.0.0.Final from the Wildfly website and extracted into C:\Program Files\wildfly-10.0.0.Final.

I then navigate to C:\Program Files\wildfly-10.0.0.Final\bin directory via windows command prompt and execute the standalone.bat command.

Wildfly doesn't start and I get the following exception: 

java.lang.IllegalArgumentException: Failed to instantiate class "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler" for handler "FILE"

If anyone has encountered this error message before, then your guidance would be greatly appreciated.

Thanks!

Ben

Upvotes: 1

Views: 1634

Answers (2)

BenRowley
BenRowley

Reputation: 24

The issue was caused due to the command prompt. As I am using windows 10, I needed to be using Command Prompt (Admin),rather than just the normal cmd hence the permission issues alluded to previously by pczeus.

After using Command Prompt (Admin), I was able to start the server.

Upvotes: 0

pczeus
pczeus

Reputation: 7867

The error appears to be a result of either file permissions on the JBoss home directory, lack of space available, or a missing directory.

Relevant posts include:

Starting WildFly 8.2 under a user with limited permissions

Which suggests setting the JBOSS_BASE_DIR property to the root folder of the JBoss installation.

https://github.com/jboss-dockerfiles/wildfly/issues/24

Suggests this can occur if the root folder does not have enough space allocated for the user (typically running in Unix environments).

Error in starting Wildfly 8.0 server with JDK 1.8

The logs/boot.log didn't exist. The author manually created the file which then revealed a permission issue on the log file (more likely on the entire Jboss installation folder).

Upvotes: 1

Related Questions