Missing Configuration File

[braincrush7]

Hello,

I'm migrating from weblogic to JBoss EAP 7.1.0 and am trying to deploy a WAR file of a project I recently ported over to JBoss.

However, the deployment fails and states ServiceName_War.Configurations is not defined!

The actual error code is WFLYCTL0080

and the error message

{"jboss.undertow.deployment.default-server.default-host./serviceName" => "java.lang.RuntimeException: java.lang.RuntimeException: java.lang.Exception: Property \"ServiceName_War.Configurations\" is not defined!

Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.Exception: Property \"ServiceName_War.Configurations\" is not defined!

    Caused by: java.lang.RuntimeException: java.lang.Exception: Property \"ServiceName_War.Configurations\" is not defined!

    Caused by: java.lang.Exception: Property \"ServiceName_War.Configurations\" is not defined!"}}

I've checked, and my War file has a web.xml and jboss-web.xml in its WEB-INF folder and I consider those to be the configuration files for JBoss.

But I am not sure this is what the error message is referring to. If anyone could point me in the right direction search, that would be much appreciated.

[ctomc]

Well you trimmed the error report so finely that most of useful info is missing...

But from general error message only thing that can be said is that your application (some component probably) is referring to some bean/resource named "Configuration" that is not available.

could it be something that is in JNDI, but without full log it is hard to say.

[braincrush7]

Hey,

I actually just used the deployed.failed file instead of the command-line transcript. But I managed to solve the problem.

It turned out that ServiceName wasn't seeing the SystemProperties it needed to.

The solution to it was to make a configurations folder that I placed inside <JBoss_Home>/modules/configurations/... Afterwards created a ServiceName_War.Configurations classpath variable through JBoss admin (Configurations -> System Properties). This allowed my application to see all of the System Properties. In addition, I needed to modifications to web.xml's display name as some of the system properties name are based off of it. Not sure if that is what you meant by JNDI.