[jboss-jira] [JBoss JIRA] (WFLY-11664) EJB client is unable to discover EJB after WildFly crash during previous call and reboot

[Ivan Straka (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Straka updated WFLY-11664:
-------------------------------
    Steps to Reproduce: 
# Download & unzip reproducer
# unzip 2x WildFly distribution
# build server
# deploy server-side app as server-1.jar to the first server and run: 
{code:bash}
export JAVA_OPTS="-Djboss.modules.system.pkgs=path-to-byteman.jar=script:path-to-HelloBeanCrash.btm"
./bin/standalone.sh -c standalone-full.xml
{code}
# deploy server-side app as server-2.jar to the second server and run: 
{code:bash}
./bin/standalone.sh -c standalone-full.xml -Djboss.socket.binding.port-offset=100
{code}
# run client-side app side
{code:bash}
mvn package exec:exec
{code}
# during countdown (you have 30 seconds) run on the first:
{code:bash}
unset JAVA_OPTS
./bin/standalone.sh -c standalone-full.xml
{code}

  was:
# Download & unzip reproducer
# unzip 2x WildFly distribution
# build server
# run on the first : 
{code:bash}
export JAVA_OPTS="-Djboss.modules.system.pkgs=path-to-byteman.jar=script:path-to-HelloBeanCrash.btm"
./bin/standalone.sh -c standalone-full.xml
deploy server-side app as server-1.jar
{code}
# run on the second: 
{code:bash}
./bin/standalone.sh -c standalone-full.xml -Djboss.socket.binding.port-offset=100
deploy server-side app as server-2.jar
{code}
# run client-side app side using mvn package exec:exec
# during countdown (you have 30 seconds) run on the first:
{code:bash}
unset JAVA_OPTS
./bin/standalone.sh -c standalone-full.xml
{code}



> EJB client is unable to discover EJB after WildFly crash during previous call and reboot
> ----------------------------------------------------------------------------------------
>
>                 Key: WFLY-11664
>                 URL: https://issues.jboss.org/browse/WFLY-11664
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Remoting
>    Affects Versions: 14.0.0.Final, 15.0.0.Final
>            Reporter: Ivan Straka
>            Priority: Blocker
>         Attachments: reproducer.zip
>
>
> Lets have two WildFly servers and same EJB on both. They have nothing to do with each other.
> *Scenario*
> # client invoke method on both EJB and the first called server crash during invokation
> # after the server reboots, client is unable to discover EJB on the server
> {code:java}Exception in thread "main" java.lang.RuntimeException: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None
>         at client.Client.call(Client.java:41)
>         at client.Client.main(Client.java:21)
> Caused by: javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-1/HelloBean", view is interface ejb.HelloBeanRemote, affinity is None
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:592)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
>         at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:56)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
>         at org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleInvocationResult(TransactionPostDiscoveryInterceptor.java:133)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
>         at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocationResult(DiscoveryEJBClientInterceptor.java:115)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
>         at org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocationResult(NamingEJBClientInterceptor.java:79)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
>         at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:172)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:594)
>         at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528)
>         at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:938)
>         at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:177)
>         at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:112)
>         at com.sun.proxy.$Proxy0.hello(Unknown Source)
>         at client.Client.call(Client.java:35)
>         ... 1 more
> {code}
> I hit this issue with 15.0.0.Final, 14.0.0.Final but not with 12.0.0.Final.
> If client try to invoke bean on the first server before it reboots, there is no problem after.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)