-
Bug
-
Resolution: Done
-
Major
-
7.2.0.CD12
-
None
tremes1@redhat.com Has hit this failure when running some tests against our OpenShift images using WF code from, I believe, 12 CR1.
13:03:50,832 ERROR [org.jboss.as.ejb3.remote] (default task-1) WFLYEJB0150: Could not write method invocation failure for method public abstract void com.redhat.xpaas.ejb.server.RemoteCounter.increment() on bean named CounterBean for appname modulename ROOT distinctname due to: java.lang.UnsupportedOperationException at java.util.AbstractMap.put(AbstractMap.java:209) at org.jboss.as.ejb3.remote.AssociationImpl.updateAffinities(AssociationImpl.java:267) at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:233) 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)
He or kwills@redhat.com can give you more details re the specific test.
Just walking through code, my guess is the Collections.emptyMap() produced at [1] is getting passed through the stack to the failing code. (I'm filing this because I did this bit of brilliant analysis. 
)
- clones
-
-
- Closed
-
- is incorporated by
-
JBEAP-14504 Upgrade WildFly HTTP client 1.0.12.Final
-
- Closed
-
