teiid-odata-8.3.0.Final.war generates exception at startup

[gioppoluca]

Fresh domain mode installation with TEIID 8.3+8.3.1 patch and getting this:

10:25:05,776 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 17) JBAS014612: Operation ("

add") failed - address: ([("deployment" => "teiid-odata-8.3.0.Final.war")]): java.lang.IllegalStateException: JBAS015841: On

ly 'hash' is allowed for deployment full replacement for a domain mode server: {"url" => "file:/opt/jboss/modules/org/jboss/

teiid/main/deployments/teiid-odata-8.3.0.Final.war"}

        at org.jboss.as.server.deployment.DeploymentAddHandler$DomainServerDeploymentAddHandler.addFromContentAdditionParame

ter(DeploymentAddHandler.java:230)

        at org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:147)

        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-control

ler-7.1.1.Final.jar:7.1.1.Final]

        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-cont

roller-7.1.1.Final.jar:7.1.1.Final]

        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-contro

ller-7.1.1.Final.jar:7.1.1.Final]

        at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.ja

va:311) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]

        at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]

        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]

Also checked this: https://community.jboss.org/message/795030

But seems that in manifest the dependency is correct (even if there is a new line where it shouldn't) so no other clue.

Luca

[gioppoluca]

Removing the dashed part in module.xml manages to start the server and the deploy command enables the war:

<resources>

        <resource-root path="teiid-engine-8.3.1.patch.jar" />

        <resource-root path="teiid-engine-8.3.0.Final.jar" />

        <resource-root path="teiid-jboss-integration-8.3.0.Final.jar" />

        <resource-root path="teiid-metadata-8.3.0.Final.jar" />

        <resource-root path="teiid-runtime-8.3.0.Final.jar" />

        <resource-root path="teiid-engine-8.3.0.Final.jar" />

        <resource-root path="saxonhe-9.2.1.5.jar" />

        <resource-root path="xom-1.2.jar" />

        <resource-root path="nux-1.6.jar" />

        <resource-root path="deployments" />

  </resources>

Why there is the deployments folder in the module with the war when there is the deploy instruction in the bin/scropts/teiid-domain-mode-install.cli?

We should deploy either as a module ( a fact that it seems not to like) or as a war.

Any idea on the correct way?

Thanks

Luca

[rareddy]

Luca,

Yes, you are correct. In domain mode the module based deployment should not be happening, can you log a JIRA?

Ramesh..