[
https://issues.jboss.org/browse/WFLY-6150?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-6150:
-----------------------------------
The aforementioned change may be failing to consume the ignored content of the
"clustered" element, resulting in the nextTag() method tripping on the text
content. The content should be consumed and discarded
EJBBoundClusteringMetaDataParser:68.
Cannot deploy ejb-multi-server QS
---------------------------------
Key: WFLY-6150
URL:
https://issues.jboss.org/browse/WFLY-6150
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Sande Gilda
Assignee: Paul Ferraro
Priority: Blocker
Fix For: 10.1.0.Final
After successful configuration and build, the QS cannot be deployed using
{{deploy-domain.cli}} script. It ends with:
{code}
The batch failed with the following error (you are remaining in the batch editing mode to
have a chance to correct the error): WFLYDC0022: Operation failed or was rolled back on
all servers.
{code}
Errors logged in server log:
{code}
[Server:app-twoB] 09:43:23,441 ERROR [org.jboss.as.server] (ServerService Thread Pool --
59) WFLYSRV0022: Deploy of deployment "jboss-ejb-multi-server-app-two.ear" was
rolled back with no failure message
[Server:app-main] 09:43:23,441 ERROR [org.jboss.as.server] (ServerService Thread Pool --
68) WFLYSRV0022: Deploy of deployment "jboss-ejb-multi-server-app-main.ear" was
rolled back with no failure message
[Server:app-twoA] 09:43:23,439 ERROR [org.jboss.as.server] (ServerService Thread Pool --
59) WFLYSRV0022: Deploy of deployment "jboss-ejb-multi-server-app-two.ear" was
rolled back with no failure message
{code}
This worked fine in ER3. JBEAP-2831 blocked testing in ER4.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)