[
https://issues.jboss.org/browse/WFLY-10782?page=com.atlassian.jira.plugin...
]
Petr Kremensky updated WFLY-10782:
----------------------------------
Description:
Trying to boot the server with configuration migrated from EAP 6.4.x fails with
{{IllegalArgumentException: Cannot require dependency more than once:service
jboss.binding.messaging-throughput}}.
*Reproduce*
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-full.xml
unzip -q jboss-eap-6.4.20.zip
cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG}
${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=jacorb:migrate
/subsystem=messaging:migrate
/subsystem=web:migrate
/subsystem=cmp:remove
/extension=org.jboss.as.cmp:remove
/subsystem=jaxr:remove
/extension=org.jboss.as.jaxr:remove
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
reload
{noformat}
*Outcome*
{noformat}
12:39:40,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread
Pool -- 47) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]): java.lang.IllegalArgumentException: Cannot require dependency more than once:service
jboss.binding.messaging-throughput
{noformat}
*Attachments:*
[^standalone-full-6.4.20.xml] - out-of-box 6.4.20 config file
[^standalone-full-wildfly.xml] - out-of-box Wildfly 32910b3 (Thu Aug 2 10:49:25 CEST
2018) config file
[^standalone-full-6.4.20-to-wildfly.xml] - configuration produced by migration
This was working with 01852ab revision (Mon Jul 16 07:41:15 CEST 2018), unfortunately my
automation was broken due to galleon2 move, so without more investigation involved I'm
unable to tell precise date when the issue appeared.
The issue is regression thus marking as a blocker.
was:
Trying to boot the server with configuration migrated from EAP 6.4.x fails with
{{IllegalArgumentException: Cannot require dependency more than once:service
jboss.binding.messaging-throughput}}.
*Reproduce*
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-full.xml
unzip -q jboss-eap-6.4.20.zip
cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG}
${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=jacorb:migrate
/subsystem=messaging:migrate
/subsystem=web:migrate
/subsystem=cmp:remove
/extension=org.jboss.as.cmp:remove
/subsystem=jaxr:remove
/extension=org.jboss.as.jaxr:remove
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
reload
{noformat}
*Outcome*
{noformat}
12:39:40,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread
Pool -- 47) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]): java.lang.IllegalArgumentException: Cannot require dependency more than once:service
jboss.binding.messaging-throughput
{noformat}
*Attachments:*
{{standalone-full-6.4.20.xml}} - out-of-box 6.4.20 config file
{{standalone-full-wildfly.xml}} - out-of-box Wildfly 32910b3 (Thu Aug 2 10:49:25 CEST
2018) config file
{{standalone-full-6.4.20-to-wildfly.xml}} - configuration produced by migration
This was working with 01852ab revision (Mon Jul 16 07:41:15 CEST 2018), unfortunately my
automation was broken due to galleon2 move, so without more investigation involved I'm
unable to tell precise date when the issue appeared.
The issue is regression thus marking as a blocker.
IllegalArgumentException from messaging-activemq after migration from
EAP 6.4.x
-------------------------------------------------------------------------------
Key: WFLY-10782
URL:
https://issues.jboss.org/browse/WFLY-10782
Project: WildFly
Issue Type: Bug
Components: JMS, Migration
Reporter: Petr Kremensky
Assignee: Jeff Mesnil
Priority: Blocker
Attachments: standalone-full-6.4.20-to-wildfly.xml, standalone-full-6.4.20.xml,
standalone-full-wildfly.xml
Trying to boot the server with configuration migrated from EAP 6.4.x fails with
{{IllegalArgumentException: Cannot require dependency more than once:service
jboss.binding.messaging-throughput}}.
*Reproduce*
{noformat}
WORKSPACE=`pwd`
CONFIG=standalone-full.xml
unzip -q jboss-eap-6.4.20.zip
cp -r ${WILDFLY}/dist/target/wildfly-14.0.0.Beta2-SNAPSHOT wildfly
SOURCE_HOME=${WORKSPACE}/jboss-eap-6.4
TARGET_HOME=${WORKSPACE}/wildfly
cp ${SOURCE_HOME}/standalone/configuration/${CONFIG}
${TARGET_HOME}/standalone/configuration
${TARGET_HOME}/bin/standalone.sh -c ${CONFIG} --start-mode=admin-only &
${TARGET_HOME}/bin/jboss-cli.sh --connect --controller=remote://localhost:9999
# Migrate
/subsystem=jacorb:migrate
/subsystem=messaging:migrate
/subsystem=web:migrate
/subsystem=cmp:remove
/extension=org.jboss.as.cmp:remove
/subsystem=jaxr:remove
/extension=org.jboss.as.jaxr:remove
/subsystem=threads:remove
/extension=org.jboss.as.threads:remove
reload
{noformat}
*Outcome*
{noformat}
12:39:40,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread
Pool -- 47) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]): java.lang.IllegalArgumentException: Cannot require dependency more than once:service
jboss.binding.messaging-throughput
{noformat}
*Attachments:*
[^standalone-full-6.4.20.xml] - out-of-box 6.4.20 config file
[^standalone-full-wildfly.xml] - out-of-box Wildfly 32910b3 (Thu Aug 2 10:49:25 CEST
2018) config file
[^standalone-full-6.4.20-to-wildfly.xml] - configuration produced by migration
This was working with 01852ab revision (Mon Jul 16 07:41:15 CEST 2018), unfortunately my
automation was broken due to galleon2 move, so without more investigation involved I'm
unable to tell precise date when the issue appeared.
The issue is regression thus marking as a blocker.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)