[JBoss JIRA] (WFLY-11143) Message sent to JMSReplyTo from old client does not find correct binding
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFLY-11143?page=com.atlassian.jira.plugin... ]
Miroslav Novak moved JBEAP-15626 to WFLY-11143:
-----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11143 (was: JBEAP-15626)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: ActiveMQ)
> Message sent to JMSReplyTo from old client does not find correct binding
> ------------------------------------------------------------------------
>
> Key: WFLY-11143
> URL: https://issues.jboss.org/browse/WFLY-11143
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
>
> There is regression in backward compatibility of messaging client. JMSReplyTo destination set by older client contains incorrect address which causes that reply message does not have correct binding and such message is lost.
> Impact: Applications will stop work after upgrade to WF14/EAP 7.2.0.CD14.
> Test Scenario:
> * Start EAP 7.2.0.CD14/WF14 server (Artemis 2.x) with deployed InQueue and OutQueue
> * Send message to InQueue from older EAP 7.2.0.CD13/WF13/Artemis 1.5.5 client to InQueue. Message has JMSReplyTo header set to OutQueue. Client got "OutQueue" queue from JNDI lookup from EAP7.2.0.CD14/WF14
> * Deploy MDB to server
> ** MDB consumes message from InQueue and sends new message to destination defined in JMSReplyTo header (so to OutQueue)
> * Receive message from OutQueue
> Result:
> No message is received from OutQueue. There is debug message in server log:
> {code}
> 11:36:09,565 DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] (Thread-25 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@22848193)) Message CoreMessage[m
> essageID=214,durable=true,userID=c0de8bd0-cba6-11e8-840f-f496342f6705,priority=4, timestamp=Tue Oct 09 11:36:09 CEST 2018,expiration=0, durable=true, address=jms.queue.OutQueue,size=580,properties=TypedPropertie
> s[inMessageId=ID:c0383a39-cba6-11e8-95ad-f496342f6705,__AMQ_CID=c0d9349a-cba6-11e8-840f-f496342f6705,_AMQ_DUPL_ID=90d1e80e-116d-4eef-9513-84c6085549db,_AMQ_ROUTING_TYPE=0]]@1680840457 is not going anywhere as it
> didn't have a binding on address:jms.queue.OutQueue
> {code}
> which indicates that jms.queue.OutQueue address does not have a binding.
> The same happesn if older EAP/WF server (with Artemis 1.5.5x) is used and new EAP 7.2.0.CD14/WF14(Artemis 2.x) client is used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11142) Regression in SOAP over JMS when WF13 and WF14 are communicating
by Jan Blizňák (Jira)
[ https://issues.jboss.org/browse/WFLY-11142?page=com.atlassian.jira.plugin... ]
Jan Blizňák updated WFLY-11142:
-------------------------------
Steps to Reproduce:
#get JBWS TS
git clone https://github.com/jbossws/jbossws-cxf.git .
git checkout jbossws-cxf-5.2.3.Final
#client WF13(artemis 1.5.5) & server WF14(artemis 2.6.3)
{code:java}
mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-14.0.0.Final -Dwildfly1400.version=13.0.0.Final
{code}
#client WF14(artemis 2.6.3) & server WF13(artemis 1.5.5)
{code:java}
mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-13.0.0.Final -Dwildfly1400.version=14.0.0.Final
{code}
was:
# get JBWS TS
git clone https://github.com/jbossws/jbossws-cxf.git .
git checkout jbossws-cxf-5.2.3.Final
#client WF13(artemis 1.5.5) & server WF14(artemis 2.6.3)
{code:java}
mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-14.0.0.Final -Dwildfly1400.version=13.0.0.Final
{code}
#client WF14(artemis 2.6.3) & server WF13(artemis 1.5.5)
{code:java}
mvn -Ptestsuite,wildfly1400 clean integration-test -Dnodeploy -Dtest=JMSEndpointOnlyDeploymentTestCase#testMessagingClient -DnoLogRedirect -DenableServerLoggingToConsole -pl modules/dist,modules/test-utils,modules/testsuite,modules/testsuite/cxf-tests -Dserver.home=/tmp/wildfly-13.0.0.Final -Dwildfly1400.version=14.0.0.Final
{code}
> Regression in SOAP over JMS when WF13 and WF14 are communicating
> ----------------------------------------------------------------
>
> Key: WFLY-11142
> URL: https://issues.jboss.org/browse/WFLY-11142
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Web Services
> Affects Versions: 14.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Jeff Mesnil
> Priority: Major
>
> There is a regression visible in JBossWS testsuite in SOAP over JMS test when client side and server side are WF13 and WF14 or vice-versa, in other words it is affecting backward and forward compatibility.
> The cause was identified as Artemis upgrade from 1.5.5 to 2.6.3, there is ongoing investigation for gathering more details.
> Exception in case of new client and old server:
> {code:java}
> Exception while processing jms message in cxf. Rolling back: javax.jms.JMSRuntimeException: Invalid address queue://jms.queue.testQueue
> at org.apache.activemq.artemis.jms.client.ActiveMQDestination.fromAddress(ActiveMQDestination.java:119) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.jms.client.ActiveMQMessage.getJMSReplyTo(ActiveMQMessage.java:356) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.cxf.transport.jms.JMSMessageHeadersType.getDestName(JMSMessageHeadersType.java:363) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
> at org.apache.cxf.transport.jms.JMSMessageHeadersType.read(JMSMessageHeadersType.java:358) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
> at org.apache.cxf.transport.jms.JMSMessageHeadersType.from(JMSMessageHeadersType.java:335) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
> at org.apache.cxf.transport.jms.JMSMessageUtils.asCXFMessage(JMSMessageUtils.java:64) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
> at org.apache.cxf.transport.jms.JMSDestination.onMessage(JMSDestination.java:237) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
> at org.apache.cxf.transport.jms.util.PollingMessageListenerContainer$Poller.run(PollingMessageListenerContainer.java:84) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_181]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_181]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_181]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11142) Regression in SOAP over JMS when WF13 and WF14 are communicating
by Jan Blizňák (Jira)
Jan Blizňák created WFLY-11142:
----------------------------------
Summary: Regression in SOAP over JMS when WF13 and WF14 are communicating
Key: WFLY-11142
URL: https://issues.jboss.org/browse/WFLY-11142
Project: WildFly
Issue Type: Bug
Components: JMS, Web Services
Affects Versions: 14.0.0.Final
Reporter: Jan Blizňák
Assignee: Jeff Mesnil
There is a regression visible in JBossWS testsuite in SOAP over JMS test when client side and server side are WF13 and WF14 or vice-versa, in other words it is affecting backward and forward compatibility.
The cause was identified as Artemis upgrade from 1.5.5 to 2.6.3, there is ongoing investigation for gathering more details.
Exception in case of new client and old server:
{code:java}
Exception while processing jms message in cxf. Rolling back: javax.jms.JMSRuntimeException: Invalid address queue://jms.queue.testQueue
at org.apache.activemq.artemis.jms.client.ActiveMQDestination.fromAddress(ActiveMQDestination.java:119) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
at org.apache.activemq.artemis.jms.client.ActiveMQMessage.getJMSReplyTo(ActiveMQMessage.java:356) [artemis-jms-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
at org.apache.cxf.transport.jms.JMSMessageHeadersType.getDestName(JMSMessageHeadersType.java:363) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at org.apache.cxf.transport.jms.JMSMessageHeadersType.read(JMSMessageHeadersType.java:358) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at org.apache.cxf.transport.jms.JMSMessageHeadersType.from(JMSMessageHeadersType.java:335) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at org.apache.cxf.transport.jms.JMSMessageUtils.asCXFMessage(JMSMessageUtils.java:64) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at org.apache.cxf.transport.jms.JMSDestination.onMessage(JMSDestination.java:237) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at org.apache.cxf.transport.jms.util.PollingMessageListenerContainer$Poller.run(PollingMessageListenerContainer.java:84) [cxf-rt-transports-jms-3.2.4-jbossorg-1.jar:3.2.4.jbossorg-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_181]
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11141) Upgrade smallrye-config 1.3.4
by Jeff Mesnil (Jira)
Jeff Mesnil created WFLY-11141:
----------------------------------
Summary: Upgrade smallrye-config 1.3.4
Key: WFLY-11141
URL: https://issues.jboss.org/browse/WFLY-11141
Project: WildFly
Issue Type: Component Upgrade
Components: MP Config
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 15.0.0.Alpha1
Smallrye-config 13.4 will incorporate the fix for WFLY-10920
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11140) IllegalStateException: java.util.ConcurrentModificationException
by Jeff Mesnil (Jira)
Jeff Mesnil created WFLY-11140:
----------------------------------
Summary: IllegalStateException: java.util.ConcurrentModificationException
Key: WFLY-11140
URL: https://issues.jboss.org/browse/WFLY-11140
Project: WildFly
Issue Type: Bug
Components: MP Config
Affects Versions: 14.0.1.Final, 14.0.0.Final
Reporter: tommaso borgato
Assignee: Jeff Mesnil
One of the many affected scenarios is [perflab_eap-7x-failover-http-session-shutdown-dist-sync-shared-sessions|h...]: it is a 4 nodes (running with the standalone-ha.xml configuration) fail-over scenario where the deployed EAR contains two WAR sharing http sessions:
{{clusterbench-ee7-shared-sessions.ear/META-INF/jboss-all.xml}}:
{noformat}
<jboss umlns="urn:jboss:1.0">
<shared-session-config xmlns="urn:jboss:shared-session-config:1.0">
<session-config>
<cookie-config>
<path>/</path>
</cookie-config>
</session-config>
</shared-session-config>
</jboss>
{noformat}
During server shut-down the EAR is stopped and we observe the following error:
{noformat}
[JBossINF] [0m[0m05:49:46,803 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 99) WFLYCLINF0003: Stopped clusterbench-ee7-shared-sessions.ear cache from web container
[JBossINF] [0m[0m05:49:46,805 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb
[JBossINF] [0m[31m05:49:46,813 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0043: Deployment unit processor org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor@6953f688 unexpectedly threw an exception during undeploy phase POST_MODULE of subdeployment "clusterbench-ee7-web-default-2.war" of deployment "clusterbench-ee7-shared-sessions.ear": java.util.ConcurrentModificationException
[JBossINF] at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
[JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1476)
[JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1474)
[JBossINF] at io.smallrye.config.SmallRyeConfigProviderResolver.releaseConfig(SmallRyeConfigProviderResolver.java:71)
[JBossINF] at org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor.undeploy(SubsystemDeploymentProcessor.java:102)
[JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:211)
[JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:204)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1792)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1761)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
[JBossINF] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
[JBossINF] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
[JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
[JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
[JBossINF] at java.lang.Thread.run(Thread.java:748)
[JBossINF]
[JBossINF] [0m[31m05:49:46,812 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0043: Deployment unit processor org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor@6953f688 unexpectedly threw an exception during undeploy phase POST_MODULE of subdeployment "clusterbench-ee7-web-default-1.war" of deployment "clusterbench-ee7-shared-sessions.ear": java.util.ConcurrentModificationException
[JBossINF] at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
[JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1476)
[JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1474)
[JBossINF] at io.smallrye.config.SmallRyeConfigProviderResolver.releaseConfig(SmallRyeConfigProviderResolver.java:71)
[JBossINF] at org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor.undeploy(SubsystemDeploymentProcessor.java:102)
[JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:211)
[JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:204)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1792)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1761)
[JBossINF] at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
[JBossINF] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
[JBossINF] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
[JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
[JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
[JBossINF] at java.lang.Thread.run(Thread.java:748)
{noformat}
Also other scenarios like [perflab_eap-7x-failover-http-session-shutdown-dist-sync-nb-state-transfer...] and [perflab_eap-7x-failover-remote-jdg-session-shutdown-invalidation-sync-hot...] exhibits the same error: I assume it does not depend on the shared sessions configuration mentioned above;
Find attached:
- the complete server log (perf18-consoleText.txt)
- the EAR used for the shared-sessions scenario (clusterbench-ee7-shared-sessions.ear)
- the EAR used for the [perflab_eap-7x-failover-http-session-shutdown-dist-sync-nb-state-transfer...] scenario (clusterbench-ee7.ear)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10920) IllegalStateException: java.util.ConcurrentModificationException
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFLY-10920?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-10920:
-------------------------------
Priority: Critical (was: Major)
> IllegalStateException: java.util.ConcurrentModificationException
> ----------------------------------------------------------------
>
> Key: WFLY-10920
> URL: https://issues.jboss.org/browse/WFLY-10920
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Affects Versions: 14.0.1.Final, 14.0.0.Final
> Reporter: tommaso borgato
> Assignee: Jeff Mesnil
> Priority: Critical
> Attachments: clusterbench-ee7-shared-sessions.ear, clusterbench-ee7.ear, perf18-consoleText.txt
>
>
> One of the many affected scenarios is [perflab_eap-7x-failover-http-session-shutdown-dist-sync-shared-sessions|h...]: it is a 4 nodes (running with the standalone-ha.xml configuration) fail-over scenario where the deployed EAR contains two WAR sharing http sessions:
> {{clusterbench-ee7-shared-sessions.ear/META-INF/jboss-all.xml}}:
> {noformat}
> <jboss umlns="urn:jboss:1.0">
> <shared-session-config xmlns="urn:jboss:shared-session-config:1.0">
> <session-config>
> <cookie-config>
> <path>/</path>
> </cookie-config>
> </session-config>
> </shared-session-config>
> </jboss>
> {noformat}
> During server shut-down the EAR is stopped and we observe the following error:
> {noformat}
> [JBossINF] [0m[0m05:49:46,803 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 99) WFLYCLINF0003: Stopped clusterbench-ee7-shared-sessions.ear cache from web container
> [JBossINF] [0m[0m05:49:46,805 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb
> [JBossINF] [0m[31m05:49:46,813 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0043: Deployment unit processor org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor@6953f688 unexpectedly threw an exception during undeploy phase POST_MODULE of subdeployment "clusterbench-ee7-web-default-2.war" of deployment "clusterbench-ee7-shared-sessions.ear": java.util.ConcurrentModificationException
> [JBossINF] at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
> [JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1476)
> [JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1474)
> [JBossINF] at io.smallrye.config.SmallRyeConfigProviderResolver.releaseConfig(SmallRyeConfigProviderResolver.java:71)
> [JBossINF] at org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor.undeploy(SubsystemDeploymentProcessor.java:102)
> [JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:211)
> [JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:204)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1792)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1761)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> [JBossINF] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> [JBossINF] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> [JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> [JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> [JBossINF] at java.lang.Thread.run(Thread.java:748)
> [JBossINF]
> [JBossINF] [0m[31m05:49:46,812 ERROR [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0043: Deployment unit processor org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor@6953f688 unexpectedly threw an exception during undeploy phase POST_MODULE of subdeployment "clusterbench-ee7-web-default-1.war" of deployment "clusterbench-ee7-shared-sessions.ear": java.util.ConcurrentModificationException
> [JBossINF] at java.util.HashMap$HashIterator.nextNode(HashMap.java:1442)
> [JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1476)
> [JBossINF] at java.util.HashMap$EntryIterator.next(HashMap.java:1474)
> [JBossINF] at io.smallrye.config.SmallRyeConfigProviderResolver.releaseConfig(SmallRyeConfigProviderResolver.java:71)
> [JBossINF] at org.wildfly.extension.microprofile.config.smallrye.deployment.SubsystemDeploymentProcessor.undeploy(SubsystemDeploymentProcessor.java:102)
> [JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:211)
> [JBossINF] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:204)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1792)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$StopTask.execute(ServiceControllerImpl.java:1761)
> [JBossINF] at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> [JBossINF] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> [JBossINF] at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> [JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> [JBossINF] at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> [JBossINF] at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Also other scenarios like [perflab_eap-7x-failover-http-session-shutdown-dist-sync-nb-state-transfer...] and [perflab_eap-7x-failover-remote-jdg-session-shutdown-invalidation-sync-hot...] exhibits the same error: I assume it does not depend on the shared sessions configuration mentioned above;
> Find attached:
> - the complete server log (perf18-consoleText.txt)
> - the EAR used for the shared-sessions scenario (clusterbench-ee7-shared-sessions.ear)
> - the EAR used for the [perflab_eap-7x-failover-http-session-shutdown-dist-sync-nb-state-transfer...] scenario (clusterbench-ee7.ear)
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-2788:
---------------------------------------
[~uxdlc]
_Daniele Zonca I'm confused about your comment regarding "expression builder component" - doesn't the tree as designed offer the ability to cover both? Click on the parent node to select the top-level data object, or click on a field within it?_
Yes it covers both but I meant that we should limit to top level data object for instance definition and internal fields for column definition (almost like now).
Let me know if you would like to create a new item to track revisit of this interaction and open a subtask to track the implementation of the first iteration (as described before) or vice-versa
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png, one.png, two.png, zero.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months