14 Replies Latest reply on Aug 24, 2011 7:06 AM by ronsen

could not find stateful bean - error

devinderpal Jun 10, 2011 7:49 PM

If I leave my browser idle for some time (around 3 mins), I get "Could not find stateful bean:" error.

javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

I grepped by bean id in logs and found below. Not sure but seems like bean is removed before it's attempted to read again.

Is there any configuration I can do to avoid this error.

[root@localhost log]# grep 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da *

server.log:2011-06-10 18:56:25,652 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (SFSB Passivation Thread - jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=LoginSessionBean,service=EJB3) Attempting to passivate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:56:25,660 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (SFSB Passivation Thread - jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=LoginSessionBean,service=EJB3) Saving session state to: /home/opt/jboss-6.0.0.Final/server/default/tmp/sessions/LoginSessionBean-gorq5pu2-d7/3j001-jr37lq-gorq3ofr-1-gorq6dxt-da.ser

server.log:2011-06-10 18:56:27,206 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (SFSB Passivation Thread - jboss.j2ee:ear=foliage.ear,jar=foliageEJB.jar,name=LoginSessionBean,service=EJB3) Passivation complete; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:16,744 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:16,744 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Reading session state from: /home/opt/jboss-6.0.0.Final/server/default/tmp/sessions/LoginSessionBean-gorq5pu2-d7/3j001-jr37lq-gorq3ofr-1-gorq6dxt-da.ser

server.log:2011-06-10 18:57:16,763 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Removing passivated state file: /home/opt/jboss-6.0.0.Final/server/default/tmp/sessions/LoginSessionBean-gorq5pu2-d7/3j001-jr37lq-gorq3ofr-1-gorq6dxt-da.ser

server.log:2011-06-10 18:57:16,979 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:16,985 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:16,987 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:16,989 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:27,893 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:27,894 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-127.0.0.1-80-1) Error Rendering View[/index.xhtml]: javax.el.ELException: /sections/leftSideBar.xhtml @14,46 rendered="#{! loginbacking.loggedIn}": javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:Caused by: javax.ejb.NoSuchEJBException: Could not find stateful bean: 3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

server.log:2011-06-10 18:57:27,998 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (http-127.0.0.1-80-1) Attempting to activate; id=3j001-jr37lq-gorq3ofr-1-gorq6dxt-da

1. Re: could not find stateful bean - error

devinderpal Jun 14, 2011 7:10 AM (in response to devinderpal)

anyone?
Actions
2. Re: could not find stateful bean - error

kirillica Jun 14, 2011 7:30 AM (in response to devinderpal)

EJB is a total pain in JBoss6, that's why I've dropped migrating to this platform
Actions
3. Re: could not find stateful bean - error

ronsen Jun 22, 2011 10:53 AM (in response to kirillica)

Discovered the same by trying to failover to another bean. (state replication doesnt work on failover for some reason) i'll just get this error if one of the nodes shuts down or crashes. Any idea?!
Actions
4. Re: could not find stateful bean - error

devinderpal Jun 26, 2011 10:23 PM (in response to ronsen)

created Bug
https://issues.jboss.org/browse/JBAS-9405
Actions
5. Re: could not find stateful bean - error

devinderpal Jul 7, 2011 7:45 AM (in response to devinderpal)

can someone please take a look at it
Actions
6. Re: could not find stateful bean - error

ronsen Jul 7, 2011 8:10 AM (in response to devinderpal)

Hi, can you post your config?
In my case its not time realted, but i played along with the configuration and it works now.
Actions
7. Re: could not find stateful bean - error

dima_ts Aug 18, 2011 10:40 PM (in response to devinderpal)

Ron, please post your solution.
It seems to me, i stumble this issue too.
Thanks in advance.
Actions

8. Re: could not find stateful bean - error

ronsen Aug 23, 2011 4:32 AM (in response to dima_ts)

Dmitry,

Server side annotations:

  
@Stateful (mappedName="FailoverFirst"
) @Clustered(loadBalancePolicy="FirstAvailable")   
@CacheConfig(name="sfsb/sync", maxSize=100000, idleTimeoutSeconds=300, removalTimeoutSeconds=0)

Client lookup:

  
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContectFactory");  
env.put(Context.URL_PKG_PREFIXES,"org.jboss.naming:org.jnp.interfaces");
String bindAddress = System.getProperty("jboss.bind.address", "jnp://" + txtIp.getText());
env.put(Context.PROVIDER_URL, bindAddress);


 ctx


 = new InitialContext(env);
 Failover f = (Failover) ctx.lookup(strat);

As easy as it is, and exactly this works well for me now. Seems that the problem was (and probably is due to an issue) in the lookup. I can't exactly remember about what it was, but I played around with it and this works for failover even though with state replication AND in cases in which a node crashs or disconnects.

Hope it helps,

Ron

9. Re: could not find stateful bean - error

dima_ts Aug 23, 2011 5:25 AM (in response to devinderpal)

Ron, thanks.
Actions
10. Re: could not find stateful bean - error

ronsen Aug 23, 2011 5:56 AM (in response to dima_ts)

Did it work?
Actions
11. Re: could not find stateful bean - error

dima_ts Aug 23, 2011 11:32 PM (in response to devinderpal)

Ron, sorry for my mess, i was wrong, i have another case.
I have problem when sfsb activating and can't deserialize instance of Logger (field in bean) fail with "Could not find stateful bean...".
keep trying ;-)
Sorry for my English
Actions
12. Re: could not find stateful bean - error

ronsen Aug 24, 2011 3:25 AM (in response to dima_ts)

Hi Dmitry,
no problem. You have a sfsb with activated state replication and you have a problem if you want to deserialize the logger instance? Means, that a failover occured previously and you dont get back the replicated values?
Actions
13. Re: could not find stateful bean - error

dima_ts Aug 24, 2011 4:03 AM (in response to devinderpal)

Hi Ron
It seems i fix my problem.
In sfsb, for logging i use org.apache.log4j.Logger, but it has't no argument constructor (needed for deserialization), bean activation process fail.
Change to org.jboss.logging.Logger solve problem.

Hope it helps somebody,
Dmitry
Actions
14. Re: could not find stateful bean - error

ronsen Aug 24, 2011 7:06 AM (in response to dima_ts)

Alright then ;-)
Actions

Go to original post