undertow http-invoker path attribute doesn't work (WildFly 22)

87 views
Skip to first unread message

jasi...@gmail.com

unread,
Mar 3, 2021, 2:29:42 PM3/3/21
to WildFly
I have multiple WildFly standalone servers that need to make remote EJB calls to each other. I want to change the EJB path from the default wildfly-services to something like wildfly-services-x (where x identifies a particular service) so that I can use the load balancer's routing rules to select the correct group of standalone instances to send the request to.

Unfortunately, changing the path to anything other than wildfly-service breaks the remote EJB calls. As far as I can tell, the request never makes it out of the client side, i.e., it never hits undertow on the target.

The debug log looks like this when I use wildfly-services (successful)
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) sendRequest: calling interceptor: org.jboss.ejb.client.TransactionInterceptor@db735b3
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) TransactionEJBClientInterceptor: calling handleInvocation, context transaction = null, transaction policy = SUPPORTS
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) TransactionEJBClientInterceptor: calling handleInvocation, no context transaction; using caller transaction = null
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) TransactionEJBClientInterceptor: Calling  handleInvocation: setting context transaction: transaction = null
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) sendRequest: calling interceptor: org.jboss.ejb.client.NamingEJBClientInterceptor@72ff28f0
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) NamingEJBClientInterceptor: calling handleInvocation: setting destination
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) NamingEJBClientInterceptor: calling setNamingDestination: providerURIs = [http://usronjsipher6:8080/wildfly-services], invocationContext type = org.jboss.ejb.client.EJBClientInvocationContext
2021-03-03 11:00:21,785-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-2) NamingEJBClientInterceptor: setting destination: (size == 1), destination = http://usronjsipher6:8080/wildfly-services

When I use wildfly-services-x it logs this "skipping messing target" message and then fails later on.
2021-03-03 11:16:18,681-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-1) TransactionEJBClientInterceptor: calling handleInvocation, context transaction = null, transaction policy = SUPPORTS
2021-03-03 11:16:18,681-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-1) TransactionEJBClientInterceptor: calling handleInvocation, no context transaction; using caller transaction = null
2021-03-03 11:16:18,681-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-1) TransactionEJBClientInterceptor: Calling  handleInvocation: setting context transaction: transaction = null
2021-03-03 11:16:18,681-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-1) sendRequest: calling interceptor: org.jboss.ejb.client.NamingEJBClientInterceptor@18b85edf
2021-03-03 11:16:18,681-0500 DEBUG [org.jboss.ejb.client.invocation] (default task-1) NamingEJBClientInterceptor: calling handleInvocation: skipping missing target

Reply all
Reply to author
Forward
0 new messages