Hi Matthias, that makes more sense, several times redeploying an application could cause this to happen if there's no proper cleanup of class references of previous deployment or if the class loader hierarchy through redeployments isn't sane. I don't think there's much I can do about this as it seems to be a Tomcat issue, sorry :-/
Take care, Geert On 21 Aug 2007, at 10:57, Matthias Barmeier wrote: > > Hi Geert, > > I have only one jar file on disk, but it could be that this effect is > created by the tomcat classloader. Tomcat seems to mess things up. The > exception comes up after several redeploys of my war file. An > undeploy, > restart tomcat, deploy sequence helps to avoid this exception. > > I dont know if further investigation is necessary. I can live with the > above mentioned work around. > If you need more information let me know. > > Thanks. > > Ciao > Matze > > Geert Bevin schrieb: >> Hi Matthias, >> >> this really sounds like a multiple jar issue where StateStoreSession >> is not loaded by the same classloader as ElementResultStateSession, >> hence causing package-level protection to fail. Are you 100% certain >> that you don't have several? >> >> Best regards, >> >> Geert >> >> On 20 Aug 2007, at 17:12, Matthias Barmeier wrote: >> >> >>> Hi Geert, >>> >>> sorry this was misleading, I meant that everything works fine for a >>> couple of weeks, but suddenly this error occurs when I build my >>> application. >>> >>> Multiple Jars in the classpath is impossibile, but maybe tomcat >>> stores >>> sessiondata on disk I will check this. >>> >>> Full stacktrace: >>> >>> java.lang.IllegalAccessError: tried to access class >>> com.uwyn.rife.engine.ElementResultStateSession from class >>> com.uwyn.rife.engine.StateStoreSession >>> at >>> com.uwyn.rife.engine.StateStoreSession.getResultStateType >>> (StateStoreSession.java:207) >>> at >>> com.uwyn.rife.engine.ResultStates.cloneForStateStore >>> (ResultStates.java:91) >>> at >>> com.uwyn.rife.engine.StateStoreSession.restoreResultStates >>> (StateStoreSession.java:160) >>> at com.uwyn.rife.engine.Gate.handleRequest(Gate.java:420) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>> Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke >>> (NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke >>> (DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:585) >>> at com.uwyn.rife.servlet.RifeFilter.doFilter >>> (RifeFilter.java:142) >>> at >>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter >>> (ApplicationFilterChain.java:202) >>> at >>> org.apache.catalina.core.ApplicationFilterChain.doFilter >>> (ApplicationFilterChain.java:173) >>> at >>> org.apache.catalina.core.StandardWrapperValve.invoke >>> (StandardWrapperValve.java:213) >>> at >>> org.apache.catalina.core.StandardContextValve.invoke >>> (StandardContextValve.java:178) >>> at >>> org.apache.catalina.core.StandardHostValve.invoke >>> (StandardHostValve.java:126) >>> at >>> org.apache.catalina.valves.ErrorReportValve.invoke >>> (ErrorReportValve.java:105) >>> at >>> org.apache.catalina.core.StandardEngineValve.invoke >>> (StandardEngineValve.java:107) >>> at >>> org.apache.catalina.connector.CoyoteAdapter.service >>> (CoyoteAdapter.java:148) >>> at >>> org.apache.coyote.http11.Http11Processor.process >>> (Http11Processor.java:869) >>> at >>> org.apache.coyote.http11.Http11BaseProtocol >>> $Http11ConnectionHandler.processConnection(Http11BaseProtocol.java: >>> 664) >>> at >>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket >>> (PoolTcpEndpoint.java:527) >>> at >>> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt >>> (LeaderFollowerWorkerThread.java:80) >>> at >>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run >>> (ThreadPool.java:684) >>> at java.lang.Thread.run(Thread.java:595) >>> >>> >>> Ciao >>> Matze >>> >>> Geert Bevin wrote: >>> >>>> Hi Matthias, >>>> >>>> can you please provide the entire stack trace? When you say several >>>> builds, is this nightly builds or releases? Also are you sure you >>>> don't have session information persisted on disc that is trying >>>> to be >>>> restored? Another possibility could be that you have several RIFE >>>> jars in your classpath. >>>> >>>> Best regards, >>>> >>>> Geert >>>> >>>> On 18 Aug 2007, at 11:31, Matthias Barmeier wrote: >>>> >>>> >>>>> Hi, >>>>> >>>>> since a few builds I got this exception when trying to load a page >>>>> from >>>>> a subsite that ist has the state session store. >>>>> >>>>> Error message: >>>>> >>>>> java.lang.IllegalAccessError >>>>> >>>>> tried to access class >>>>> com.uwyn.rife.engine.ElementResultStateSession >>>>> >>>>> from class com.uwyn.rife.engine.StateStoreSession >>>>> >>>> -- >>>> Geert Bevin >>>> Terracotta - http://www.terracotta.org >>>> Uwyn "Use what you need" - http://uwyn.com >>>> RIFE Java application framework - http://rifers.org >>>> Music and words - http://gbevin.com >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> -- >> Geert Bevin >> Terracotta - http://www.terracotta.org >> Uwyn "Use what you need" - http://uwyn.com >> RIFE Java application framework - http://rifers.org >> Music and words - http://gbevin.com >> >> >>> >> >> >> > > > -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
