[JBoss JIRA] (WFWIP-56) IndexOutOfBoundsException in JDBC HA scenario
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-56?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak updated WFWIP-56:
--------------------------------
Steps to Reproduce:
This issue is *intermittent*, it's necessary to run reproducer many times:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/97/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ColocatedClusterFailoverTestCase#testFailbackWithMdbsShutdownDeployUsingCLI -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531731315-SNAPSHOT -DfailIfNoTests=false -Deap=7x | tee log
{code}
was:
{code}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/97/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=ColocatedClusterFailoverTestCase#testFailbackWithMdbsShutdownDeployUsingCLI -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531731315-SNAPSHOT -DfailIfNoTests=false -Deap=7x | tee log
{code}
> IndexOutOfBoundsException in JDBC HA scenario
> ---------------------------------------------
>
> Key: WFWIP-56
> URL: https://issues.jboss.org/browse/WFWIP-56
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Erich Duda
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: feature-branch-blocker
>
> PR: https://github.com/wildfly/wildfly/pull/11355
> *Scenario:*
> * There are two Wildfly servers each containing two Artemis brokers
> * Artemis brokers creates two live-backup pairs. Each Wildfly instance contains one live and one backup
> * Second server has MDB which resends messages from InQueue to OutQueue
> * The second server is stopped and restarted
> After the second server is restarted, everything works correctly for a while. Failback performs successfully, MDB resends messages. However after some time the server starts to print many errors \[1\]. It looks like some messages where corrupted during failover/failback and cannot be delivered.
> The reproducer always hits the issue. The issue is not relevant to particular database, I hit it with Oracle12c and DB2 11.1. I also tried to reduce amount of messages and their size, but I still hit the issue. So it is not related to paging or large messages.
> \[1\]
> {code}
> 15:20:50,010 ERROR [org.apache.activemq.artemis.ra] (Thread-7 (ActiveMQ-client-global-threads)) AMQ154004: Failed to deliver message: java.lang.IndexOutOfBoundsException
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readSimpleStringInternal(ChannelBufferWrapper.java:93) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.buffers.impl.ChannelBufferWrapper.readNullableSimpleString(ChannelBufferWrapper.java:73) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.reader.TextMessageUtil.readBodyText(TextMessageUtil.java:37) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.jms.client.ActiveMQTextMessage.doBeforeReceive(ActiveMQTextMessage.java:112) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:295) [artemis-ra-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2797) [DMN Designer] Data-types: Grid: Relation
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2797?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2797:
-----------------------------------
Description:
*_Relation_*
- (/) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (/) {{InformationItem}} column should show Input Data Type
- (/) {{InformationItem}} column should support changing Input Data Type
was:
*_Relation_*
- (x) Grid header _could_ show Output Data Type
- (/) Editing Output Data Type is possible via Properties panel
- (x) {{InformationItem}} column should show Input Data Type
- (x) {{InformationItem}} column should support changing Input Data Type
> [DMN Designer] Data-types: Grid: Relation
> -----------------------------------------
>
> Key: DROOLS-2797
> URL: https://issues.jboss.org/browse/DROOLS-2797
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> *_Relation_*
> - (/) Grid header _could_ show Output Data Type
> - (/) Editing Output Data Type is possible via Properties panel
> - (/) {{InformationItem}} column should show Input Data Type
> - (/) {{InformationItem}} column should support changing Input Data Type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10833) Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10833?page=com.atlassian.jira.plugin... ]
Ondra Chaloupka commented on WFLY-10833:
----------------------------------------
The `CompensationManagerImpl` class was moved from `impl` package to `internal` based on the issue https://issues.jboss.org/browse/JBTM-2269.
The WildFly 10 integrates Narayana in the older version 5.2.x where the change are not applied yet. The WildFly 13 integrates Narayana in version 5.5.x.
The module `org.jboss.narayana.compensations` uses the the correct new placing of the bean. In the clean WildFly installation I can't see other place where the bean would be defined.
[~westlake91361] I would bet your application depends on the Narayana in version 5.2.x which brings this dependency to the container. Could it be that you pack the Naryana compensation module to your application (e.g. you do not use the Maven scope `provided` during the build)?
> Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10833
> URL: https://issues.jboss.org/browse/WFLY-10833
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 13.0.0.Final
> Environment: JDK 8
> Wildfly 13.0.0.Final
> Reporter: Angela Yuan
> Assignee: Ondra Chaloupka
>
> Able to deploy the same WAR and EAR to Wildfly 10.0.0.Final but not to 13.0.0.Final with the following error:
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."xxxxx.war".WeldStartService: org.jboss.msc.service.S
> tartException in service jboss.deployment.unit."fwdm-services-1.0-SNAPSHOT.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
> at injection point [UnbackedAnnotatedField] @Inject org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager
> at org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager(CancelOnFailureInterceptor.java:0)
> Possible dependencies:
> - Managed Bean [class org.jboss.narayana.compensations.internal.CompensationManagerImpl] with qualifiers [@Any @Default],
> - Managed Bean [class org.jboss.narayana.compensations.impl.CompensationManagerImpl] with qualifiers [@Any @Default]
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:386)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
> at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:564)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:81)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:79)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10833) Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-10833?page=com.atlassian.jira.plugin... ]
Ondra Chaloupka edited comment on WFLY-10833 at 8/16/18 7:04 AM:
-----------------------------------------------------------------
The {{CompensationManagerImpl}} class was moved from `impl` package to `internal` based on the issue https://issues.jboss.org/browse/JBTM-2269.
The WildFly 10 integrates Narayana in the older version 5.2.x where the change are not applied yet. The WildFly 13 integrates Narayana in version 5.5.x.
The module `org.jboss.narayana.compensations` uses the the correct new placing of the bean. In the clean WildFly installation I can't see other place where the bean would be defined.
[~westlake91361] I would bet your application depends on the Narayana in version 5.2.x which brings this dependency to the container. Could it be that you pack the Naryana compensation module to your application (e.g. you do not use the Maven scope `provided` during the build)?
was (Author: ochaloup):
The `CompensationManagerImpl` class was moved from `impl` package to `internal` based on the issue https://issues.jboss.org/browse/JBTM-2269.
The WildFly 10 integrates Narayana in the older version 5.2.x where the change are not applied yet. The WildFly 13 integrates Narayana in version 5.5.x.
The module `org.jboss.narayana.compensations` uses the the correct new placing of the bean. In the clean WildFly installation I can't see other place where the bean would be defined.
[~westlake91361] I would bet your application depends on the Narayana in version 5.2.x which brings this dependency to the container. Could it be that you pack the Naryana compensation module to your application (e.g. you do not use the Maven scope `provided` during the build)?
> Wildfly 13.0.0.Final deployment failed due to WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10833
> URL: https://issues.jboss.org/browse/WFLY-10833
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 13.0.0.Final
> Environment: JDK 8
> Wildfly 13.0.0.Final
> Reporter: Angela Yuan
> Assignee: Ondra Chaloupka
>
> Able to deploy the same WAR and EAR to Wildfly 10.0.0.Final but not to 13.0.0.Final with the following error:
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."xxxxx.war".WeldStartService: org.jboss.msc.service.S
> tartException in service jboss.deployment.unit."fwdm-services-1.0-SNAPSHOT.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type CompensationManager with qualifiers @Default
> at injection point [UnbackedAnnotatedField] @Inject org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager
> at org.jboss.narayana.compensations.impl.CancelOnFailureInterceptor.compensationManager(CancelOnFailureInterceptor.java:0)
> Possible dependencies:
> - Managed Bean [class org.jboss.narayana.compensations.internal.CompensationManagerImpl] with qualifiers [@Any @Default],
> - Managed Bean [class org.jboss.narayana.compensations.impl.CompensationManagerImpl] with qualifiers [@Any @Default]
> at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:386)
> at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
> at org.jboss.weld.bootstrap.Validator.validateInterceptor(Validator.java:564)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:81)
> at org.jboss.weld.bootstrap.ConcurrentValidator$2.doWork(ConcurrentValidator.java:79)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months