[JBoss JIRA] (WFLY-9914) Server reload breaks security context
by Teresa Miyar (Jira)
[ https://issues.jboss.org/browse/WFLY-9914?page=com.atlassian.jira.plugin.... ]
Teresa Miyar commented on WFLY-9914:
------------------------------------
It does not fail in any of the newer versions.
> Server reload breaks security context
> -------------------------------------
>
> Key: WFLY-9914
> URL: https://issues.jboss.org/browse/WFLY-9914
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Final
> Environment: Ubuntu 16.04 LTS, Oracle JDK 1.8.0_161
> Reporter: Harald Wellmann
> Assignee: Teresa Miyar
> Priority: Major
>
> h3. Summary
> A minimal example webapp using Soteria and DeltaSpike Security works as expected when first deployed to WildFly.
> After issuing a {{reload}} command via {{jboss-cli.sh}}, the application no longer works, since no groups are associated to the caller principal.
> The problem no longer occurs after a server shutdown and restart.
> h3. Details
> {noformat}
> # Start server
> $ ${JBOSS_HOME}/bin/standalone.sh
> # Build and deploy demo
> $ git clone https://github.com/hwellmann/security-demo.git
> $ cd security-demo
> $ mvn deploy
> # Request protected resource
> $ curl -u operator:secret http://localhost:8080/api/version
> {"version":1}
> # Reload server
> $ ${JBOSS_HOME}/bin/jboss-cli.sh -c --command=:reload
> # Issue same request, access denied
> $ curl -u operator:secret http://localhost:8080/api/version
> {"message":"requested access to the resource is denied"}
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-2602) Download link for particular KIE Execution Server war instead of zip with wars for all containers
by Michael Biarnes Kiefer (Jira)
[ https://issues.jboss.org/browse/DROOLS-2602?page=com.atlassian.jira.plugi... ]
Michael Biarnes Kiefer commented on DROOLS-2602:
------------------------------------------------
[~tirelli] The kie-server-7.7.0.Final-webc.war comes in this zip but also in
./droolsjbpm-integration/kie-server-parent/kie-server-wars/kie-server/target/kie-server-<version>-webc.war
So I have to add this in one script that uploads the binaries to filemgmt, change websites files https://github.com/kiegroup/drools-website/blob/master/_config/pom.yml and https://github.com/kiegroup/drools-website/blob/master/download/download.... to add the webc.
Then it should appear on bottom of the download of KIE Execution server.
Questions:
* does it look right if you have a zip with all servers and the only one of these servers again but separated?
* what do we do if another user asks for another file in this zip? Do we finally have to add all of them in the listing? (the original idea for this zip will be disabled)
Wdyt?
> Download link for particular KIE Execution Server war instead of zip with wars for all containers
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2602
> URL: https://issues.jboss.org/browse/DROOLS-2602
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 7.7.0.Final
> Reporter: Igor Azarny
> Assignee: Michael Biarnes Kiefer
> Priority: Optional
> Labels: distribution
>
> Could you please provide the download link for particular KIE Execution Server war instead of zip with wars for all containers?
> Reason - need to create buildpack with kie server for pivotal cloud foundry on CI env. So I need just kie-server-7.7.0.Final-webc.war instead of kie-server-distribution-7.7.0.Final.zip
> Thanks, Igor
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11234) Since WildFly 14 i18n ResourceBundle properties file not found if without locale
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11234?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFLY-11234.
-------------------------------------
Fix Version/s: 15.0.0.Alpha1
Assignee: Brian Stansberry (was: Jason Greene)
Resolution: Duplicate Issue
> Since WildFly 14 i18n ResourceBundle properties file not found if without locale
> --------------------------------------------------------------------------------
>
> Key: WFLY-11234
> URL: https://issues.jboss.org/browse/WFLY-11234
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 14.0.1.Final
> Environment: Ubuntu 18.04, OpenJDK 8 and 11
> Reporter: Anton Pussep
> Assignee: Brian Stansberry
> Priority: Major
> Fix For: 15.0.0.Alpha1
>
>
> As discussed in this thread
> https://developer.jboss.org/message/985930
> my i18n properties have not been resolved on WildFly 14.0.1.Final - it was working fine through WildFly 10-13, however. I could solve the issue by renaming my properties file from messages.properties to messages_en.properties. Since this solved the issue, I suspect that WildFly 14 does not accept filenames without locale anymore. Since I'm not sure if this is by design, I'm posting this as a bug report here.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11235) Server with HA profile bound to 0.0.0.0 sends cluster topology containing this address to client
by Dennis Reed (Jira)
[ https://issues.jboss.org/browse/WFLY-11235?page=com.atlassian.jira.plugin... ]
Dennis Reed edited comment on WFLY-11235 at 10/24/18 5:52 PM:
--------------------------------------------------------------
0.0.0.0 is not a valid IP to send to clients -- it's a major misconfiguration and should throw an error instead of trying to use it. Just picking an IP and hoping it's right is even worse, particularly from a stability and debugging standpoint (in other words it would cause a lot of misconfigured systems and support cases).
Since everything shares the same ports, it's a little trickier, as 0.0.0.0 is a valid bind for other services. There should probably be a separate configuration for IP to send to clients that is required when binding to 0.0.0.0.
was (Author: dereed):
0.0.0.0 is not a valid IP to send to clients -- it's a major misconfiguration and should throw an error instead of trying to use it. Just picking an IP and hoping it's right is even worse, particularly from a stability and debugging standpoint.
Since everything shares the same ports, it's a little trickier, as 0.0.0.0 is a valid bind for other services. There should probably be a separate configuration for IP to send to clients that is required when binding to 0.0.0.0.
> Server with HA profile bound to 0.0.0.0 sends cluster topology containing this address to client
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-11235
> URL: https://issues.jboss.org/browse/WFLY-11235
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Minor
> Labels: downstream_dependency
> Attachments: WFLY-11235-reproducer.zip
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> Scenario:
> - server-1
> -- Doesn't matter which profile
> -- Doesn't matter which bind address
> -- Has a remote-outbound-connection pointing at server-2 through server-2's public IP address
> - server-2
> -- On a different machine than server-1
> -- Bound to 0.0.0.0 (important)
> -- Running standalone-ha profile (important)
> - Standalone EJB client invokes a bean server-1, which as a result invokes another bean on server-2. Repeat this multiple times.
> The first invocation goes through correctly, but it can be seen in the log of server-1 that server-2 (10.8.246.90) has sent a cluster topology containing 0.0.0.0:
> {noformat}
> 04:04:24,651 TRACE [org.jboss.ejb.client.remoting] (default task-5) Running callback org.jboss.ejb.protocol.remote.RemoteEJBService$1$1$$Lambda$876/915175573@68823b7b(org.jboss.ejb.protocol.remote.EJBServerChannel(a)707ad04e, org.jboss.as.ejb3.remote.AssociationImpl@3eb54e9a)
> 04:04:24,919 INFO [org.wildfly.naming] (default task-7) WildFly Naming version 1.0.7.Final-redhat-1
> 04:04:24,930 INFO [org.jboss.ejb.client] (default task-7) JBoss EJB Client version 4.0.9.Final-redhat-1
> 04:04:24,941 DEBUG [org.jboss.ejb.client.invocation] (default task-7) Calling invoke(module = /server-side/WhoAmIBean, strong affinity = None, weak affinity = None):
> 04:04:24,948 TRACE [org.jboss.ejb.client.invocation] (default task-7) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None, weak affinity = None)
> 04:04:24,949 TRACE [org.jboss.ejb.client.invocation] (default task-7) Performing any discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None, weak affinity = None, filter spec = (ejb-module=server-side))
> 04:04:24,952 TRACE [org.jboss.ejb.client.invocation] (default task-7) EJB discovery provider: attempting to connect to configured connection remote+http://10.8.246.90:8080
> 04:04:25,317 DEBUG [org.jboss.ejb.client.invocation] (default task-18) Received CLUSTER_TOPOLOGY(15) message, registering cluster ejb to node localhost
> 04:04:25,319 DEBUG [org.jboss.ejb.client.invocation] (default task-18) Received CLUSTER_TOPOLOGY(15) message block, registering block ::/0 to address /0.0.0.0:8080
> 04:04:25,321 DEBUG [org.jboss.ejb.client.invocation] (default task-19) Received MODULE_AVAILABLE(8) message for module /server-side
> 04:04:25,324 TRACE [org.jboss.ejb.client.invocation] (default task-7) Performed first-match discovery(target affinity(node) = localhost, destination = remote+http://10.8.246.90:8080)
> 04:04:25,325 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:450))
> 04:04:25,326 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from SENT to WAITING (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:339))
> 04:04:25,345 TRACE [org.jboss.ejb.client] (default task-22) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from WAITING to READY (org.jboss.ejb.client.EJBClientInvocationContext.resultReady(EJBClientInvocationContext.java:646))
> 04:04:25,345 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from READY to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:546))
> 04:04:25,346 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from CONSUMING to DONE (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:573))
> {noformat}
> After the first invocation, the bean proxy on server-1 sets it affinity to a ClusterAffinity, which means that the next invocation's destination is picked based on the cluster topology (which contains only 0.0.0.0). It will most likely fail, and after this, the affinity seems to be reset back to None, therefore we have a loop where always one invocation works correctly and the following one fails.
> The following is the log observed on server-1 when an invocation tries to go to 0.0.0.0 (so it either fails with connection refused, or server-1 tries to invoke itself in case that it's listening on 0.0.0.0 too)
> {noformat}
> 04:04:26,485 DEBUG [org.jboss.ejb.client.invocation] (default task-24) Calling invoke(module = /server-side/WhoAmIBean, strong affinity = Cluster "ejb", weak affinity = None):
> 04:04:26,485 TRACE [org.jboss.ejb.client.invocation] (default task-24) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None)
> 04:04:26,486 TRACE [org.jboss.ejb.client.invocation] (default task-24) Performing cluster discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, filter spec = (&(cluster=ejb)))
> 04:04:26,486 TRACE [org.jboss.ejb.client.invocation] (default task-24) EJB discovery provider: attempting to connect to configured connection remote+http://10.8.246.90:8080
> 04:04:26,488 TRACE [org.jboss.ejb.client.invocation] (default task-24) EJB discovery provider: attempting to connect to cluster ejb connection remote+http://0.0.0.0:8080
> 04:04:26,492 TRACE [org.jboss.ejb.client.invocation] (default task-24) Performed cluster discovery (target affinity = Node "localhost", destination = remote+http://0.0.0.0:8080)
> 04:04:26,493 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:450))
> 04:04:26,495 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENT to WAITING (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:339))
> 04:04:26,497 TRACE [org.jboss.ejb.client] (default task-32) Invocation marked failed, state is currently: WAITING
> 04:04:26,498 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from WAITING to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.failed(EJBClientInvocationContext.java:975))
> 04:04:26,498 TRACE [org.jboss.ejb.client.invocation] (default task-32) Blacklisting destination (locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, missing target = remote+http://0.0.0.0:8080)
> 04:04:26,499 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from CONSUMING to SENDING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:600))
> 04:04:26,499 TRACE [org.jboss.ejb.client.invocation] (default task-32) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None)
> 04:04:26,499 TRACE [org.jboss.ejb.client.invocation] (default task-32) Performing cluster discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, filter spec = (&(cluster=ejb)))
> 04:04:26,501 TRACE [org.jboss.ejb.client.invocation] (default task-32) Performed cluster discovery, nodes is empty; trying an initial
> 04:04:26,502 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:442))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENT to READY (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:380))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from READY to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:546))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-24) Will not retry (requested = false, remaining = 0)
> 04:04:26,504 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from CONSUMING to DONE (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:613))
> 04:04:26,505 ERROR [org.jboss.as.ejb3.invocation] (default task-24) WFLYEJB0034: EJB Invocation failed on component Intermediate for method public abstract java.lang.String example.ejb.WhoAmIBeanRemote.whoAmI(): javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb"
> (... rest of the error omitted, but it is a "connection refused")
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11235) Server with HA profile bound to 0.0.0.0 sends cluster topology containing this address to client
by Dennis Reed (Jira)
[ https://issues.jboss.org/browse/WFLY-11235?page=com.atlassian.jira.plugin... ]
Dennis Reed commented on WFLY-11235:
------------------------------------
0.0.0.0 is not a valid IP to send to clients -- it's a major misconfiguration and should throw an error instead of trying to use it. Just picking an IP and hoping it's right is even worse, particularly from a stability and debugging standpoint.
Since everything shares the same ports, it's a little trickier, as 0.0.0.0 is a valid bind for other services. There should probably be a separate configuration for IP to send to clients that is required when binding to 0.0.0.0.
> Server with HA profile bound to 0.0.0.0 sends cluster topology containing this address to client
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-11235
> URL: https://issues.jboss.org/browse/WFLY-11235
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Minor
> Labels: downstream_dependency
> Attachments: WFLY-11235-reproducer.zip
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> Scenario:
> - server-1
> -- Doesn't matter which profile
> -- Doesn't matter which bind address
> -- Has a remote-outbound-connection pointing at server-2 through server-2's public IP address
> - server-2
> -- On a different machine than server-1
> -- Bound to 0.0.0.0 (important)
> -- Running standalone-ha profile (important)
> - Standalone EJB client invokes a bean server-1, which as a result invokes another bean on server-2. Repeat this multiple times.
> The first invocation goes through correctly, but it can be seen in the log of server-1 that server-2 (10.8.246.90) has sent a cluster topology containing 0.0.0.0:
> {noformat}
> 04:04:24,651 TRACE [org.jboss.ejb.client.remoting] (default task-5) Running callback org.jboss.ejb.protocol.remote.RemoteEJBService$1$1$$Lambda$876/915175573@68823b7b(org.jboss.ejb.protocol.remote.EJBServerChannel(a)707ad04e, org.jboss.as.ejb3.remote.AssociationImpl@3eb54e9a)
> 04:04:24,919 INFO [org.wildfly.naming] (default task-7) WildFly Naming version 1.0.7.Final-redhat-1
> 04:04:24,930 INFO [org.jboss.ejb.client] (default task-7) JBoss EJB Client version 4.0.9.Final-redhat-1
> 04:04:24,941 DEBUG [org.jboss.ejb.client.invocation] (default task-7) Calling invoke(module = /server-side/WhoAmIBean, strong affinity = None, weak affinity = None):
> 04:04:24,948 TRACE [org.jboss.ejb.client.invocation] (default task-7) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None, weak affinity = None)
> 04:04:24,949 TRACE [org.jboss.ejb.client.invocation] (default task-7) Performing any discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None, weak affinity = None, filter spec = (ejb-module=server-side))
> 04:04:24,952 TRACE [org.jboss.ejb.client.invocation] (default task-7) EJB discovery provider: attempting to connect to configured connection remote+http://10.8.246.90:8080
> 04:04:25,317 DEBUG [org.jboss.ejb.client.invocation] (default task-18) Received CLUSTER_TOPOLOGY(15) message, registering cluster ejb to node localhost
> 04:04:25,319 DEBUG [org.jboss.ejb.client.invocation] (default task-18) Received CLUSTER_TOPOLOGY(15) message block, registering block ::/0 to address /0.0.0.0:8080
> 04:04:25,321 DEBUG [org.jboss.ejb.client.invocation] (default task-19) Received MODULE_AVAILABLE(8) message for module /server-side
> 04:04:25,324 TRACE [org.jboss.ejb.client.invocation] (default task-7) Performed first-match discovery(target affinity(node) = localhost, destination = remote+http://10.8.246.90:8080)
> 04:04:25,325 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:450))
> 04:04:25,326 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from SENT to WAITING (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:339))
> 04:04:25,345 TRACE [org.jboss.ejb.client] (default task-22) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from WAITING to READY (org.jboss.ejb.client.EJBClientInvocationContext.resultReady(EJBClientInvocationContext.java:646))
> 04:04:25,345 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from READY to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:546))
> 04:04:25,346 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from CONSUMING to DONE (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:573))
> {noformat}
> After the first invocation, the bean proxy on server-1 sets it affinity to a ClusterAffinity, which means that the next invocation's destination is picked based on the cluster topology (which contains only 0.0.0.0). It will most likely fail, and after this, the affinity seems to be reset back to None, therefore we have a loop where always one invocation works correctly and the following one fails.
> The following is the log observed on server-1 when an invocation tries to go to 0.0.0.0 (so it either fails with connection refused, or server-1 tries to invoke itself in case that it's listening on 0.0.0.0 too)
> {noformat}
> 04:04:26,485 DEBUG [org.jboss.ejb.client.invocation] (default task-24) Calling invoke(module = /server-side/WhoAmIBean, strong affinity = Cluster "ejb", weak affinity = None):
> 04:04:26,485 TRACE [org.jboss.ejb.client.invocation] (default task-24) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None)
> 04:04:26,486 TRACE [org.jboss.ejb.client.invocation] (default task-24) Performing cluster discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, filter spec = (&(cluster=ejb)))
> 04:04:26,486 TRACE [org.jboss.ejb.client.invocation] (default task-24) EJB discovery provider: attempting to connect to configured connection remote+http://10.8.246.90:8080
> 04:04:26,488 TRACE [org.jboss.ejb.client.invocation] (default task-24) EJB discovery provider: attempting to connect to cluster ejb connection remote+http://0.0.0.0:8080
> 04:04:26,492 TRACE [org.jboss.ejb.client.invocation] (default task-24) Performed cluster discovery (target affinity = Node "localhost", destination = remote+http://0.0.0.0:8080)
> 04:04:26,493 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:450))
> 04:04:26,495 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENT to WAITING (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:339))
> 04:04:26,497 TRACE [org.jboss.ejb.client] (default task-32) Invocation marked failed, state is currently: WAITING
> 04:04:26,498 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from WAITING to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.failed(EJBClientInvocationContext.java:975))
> 04:04:26,498 TRACE [org.jboss.ejb.client.invocation] (default task-32) Blacklisting destination (locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, missing target = remote+http://0.0.0.0:8080)
> 04:04:26,499 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from CONSUMING to SENDING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:600))
> 04:04:26,499 TRACE [org.jboss.ejb.client.invocation] (default task-32) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None)
> 04:04:26,499 TRACE [org.jboss.ejb.client.invocation] (default task-32) Performing cluster discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, filter spec = (&(cluster=ejb)))
> 04:04:26,501 TRACE [org.jboss.ejb.client.invocation] (default task-32) Performed cluster discovery, nodes is empty; trying an initial
> 04:04:26,502 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:442))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENT to READY (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:380))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from READY to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:546))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-24) Will not retry (requested = false, remaining = 0)
> 04:04:26,504 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from CONSUMING to DONE (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:613))
> 04:04:26,505 ERROR [org.jboss.as.ejb3.invocation] (default task-24) WFLYEJB0034: EJB Invocation failed on component Intermediate for method public abstract java.lang.String example.ejb.WhoAmIBeanRemote.whoAmI(): javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb"
> (... rest of the error omitted, but it is a "connection refused")
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months