[jboss-jira] [JBoss JIRA] (AS7-3828) EJB client tries to invoke EJBs after application was undeployed

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669237#comment-12669237 ] 

jaikiran pai edited comment on AS7-3828 at 2/20/12 11:20 AM:
-------------------------------------------------------------

How is the application undeployed from the server side? Server shutdown? After the application is undeployed from one node are there any other nodes in that client context which can handle this deployment's request?

                
      was (Author: jaikiran):
    How is the application undeployed from the server side? After the application is undeployed from one node are there any other nodes in that client context which can handle this deployment's request?

                  
> EJB client tries to invoke EJBs after application was undeployed
> ----------------------------------------------------------------
>
>                 Key: AS7-3828
>                 URL: https://issues.jboss.org/browse/AS7-3828
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 7.1.0.Final
>            Reporter: Radoslav Husar
>            Assignee: jaikiran pai
>            Priority: Critical
>              Labels: failover_testing
>             Fix For: 7.1.1.Final
>
>
> And this results in NoSuchEJBException.
> One more feature that was fully supported in previous version (AS 5.1).
> {noformat}
> 2012/02/20 10:59:11:336 EST [WARN ][Runner - 43] SFCORE_LOG - Error sampling data:  <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 43.>
>         org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 43.
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:79)
> 	at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
> 	at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> 	at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.ejb.NoSuchEJBException: No such EJB[appname=clusterbench-ee6,modulename=clusterbench-ee6-ejb,distinctname=,beanname=RemoteStatefulSBImpl]
> 	at org.jboss.ejb.client.remoting.GeneralInvocationFailureResponseHandler.processMessage(GeneralInvocationFailureResponseHandler.java:75)
> 	at org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver.handleMessage(ChannelAssociation.java:385)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:371)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	... 1 more
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira