java - Why JBoss EAP 6.4 fail to load the session using the http session replication mechanism? -


i have been using session replication in jboss eap 6.1 in windows. changed jboss eap 6.4 dev testing in ubuntu , same code stopped working.

there's not it, added <distributable/> tag , didn't added manual serialversionuid value serialized class logged.java (it stays annotated ignore warnings).

i store instance of class in http session, shutdown server using jboss-cli.sh --connect command=:shutdown (nopause=true environment variable), startup server again. after server started, when try access session again cannot retrieve class instance , following error occurs in console:

...  21:47:13,852 warn  [org.jboss.as.clustering.web.infinispan] (http-/0.0.0.0:80-1)  jbas010322: failed load session 9oqtrw3vgc-uf8w3dmrhd+pk: java.lang.runtimee xception: jbas010333: failed load session attributes session: 9oqtrw3vgc- uf8w3dmrhd+pk         @ org.jboss.as.clustering.web.infinispan.distributedcachemanager$2.invo ke(distributedcachemanager.java:229)         @ org.jboss.as.clustering.web.infinispan.distributedcachemanager$2.invoke(distributedcachemanager.java:212)         @ org.jboss.as.clustering.infinispan.invoker.simplecacheinvoker.invoke(simplecacheinvoker.java:34)         @ org.jboss.as.clustering.infinispan.invoker.batchcacheinvoker.invoke(batchcacheinvoker.java:48)         @ org.jboss.as.clustering.infinispan.invoker.retryingcacheinvoker.invoke(retryingcacheinvoker.java:85)         @ org.jboss.as.clustering.web.infinispan.distributedcachemanager$forcesynchronouscacheinvoker.invoke(distributedcachemanager.java:550)         @ org.jboss.as.clustering.web.infinispan.distributedcachemanager.getdata(distributedcachemanager.java:238)         @ org.jboss.as.clustering.web.infinispan.distributedcachemanager.getsessiondata(distributedcachemanager.java:196)         @ org.jboss.as.web.session.distributablesessionmanager.loadsession(distributablesessionmanager.java:1429) [jboss-as-web-7.5.0.final-redhat-21.jar:7.5.0.final-redhat-21]         @ org.jboss.as.web.session.distributablesessionmanager.findsession(distributablesessionmanager.java:688) [jboss-as-web-7.5.0.final-redhat-21.jar:7.5.0.final-redhat-21]  @ org.jboss.as.web.session.distributablesessionmanager.findsession(distributablesessionmanager.java:84) [jboss-as-web-7.5.0.final-redhat-21.jar:7.5.0.final-redhat-21]         @ org.apache.catalina.connector.request.dogetsession(request.java:2661) [jbossweb-7.5.7.final-redhat-1.jar:7.5.7.final-redhat-1]         @ org.apache.catalina.connector.request.getsession(request.java:2382) [jbossweb-7.5.7.final-redhat-1.jar:7.5.7.final-redhat-1]         @ org.apache.catalina.connector.requestfacade.getsession(requestfacade.java:791) [jbossweb-7.5.7.final-redhat-1.jar:7.5.7.final-redhat-1]         @ org.apache.catalina.connector.requestfacade.getsession(requestfacade.java:801) [jbossweb-7.5.7.final-redhat-1.jar:7.5.7.final-redhat-1]         @ org.webstories.core.auth.authsession.from(authsession.java:12) [classes:] ... 

i have no idea start looking because have no knowledge of jboss internals, except documented throughout web. in case documented need add <distributable/> web.xml , session replication "magically" start working. of course, need declare class instance serializable able serialized, besides see no reason why not working in jboss eap 6.4 in ubuntu.

lsb_release -a:

no lsb modules available. distributor id: ubuntu description:    ubuntu 14.04.2 lts release:        14.04 codename:       trusty 

java -version:

java version "1.8.0_45" java(tm) se runtime environment (build 1.8.0_45-b14) java hotspot(tm) client vm (build 25.45-b02, mixed mode) 

follow stack trace down. there should cause (nested exception) , suspect not serializable or null pointer. otherwise may able find exception earlier not-serializable

the cause of session persistence/replication issues trying store non-serializable object in session. causes storage of session fail , subsequent retrieval cannot proceed.

remember not class being stored must serializable non-static non-transient fields recursively. can difficult , tedious find.

with regard serialversionuid cause issues if have versions different compiles deployed in different servers within cluster compiler create 1 automatically if same compile match.


Comments

Popular posts from this blog

shopping cart - Page redirect not working PHP -

php - How to modify a menu to show sub-menus -

python - Installing PyDev in eclipse is failed -