The FIELD granularity web session replication tests are now all failing
in hudson
(
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...).
I updated my workspace today and now see the same thing. I *suspect*
it's related to the WarClassloaderDeployer change, just because that
looked like the main thing that came in during my svn update.
There's a problem instantiating an instance of a class that's been
AOP-prepared for use in PojoCache:
2008-02-02 12:53:02,190 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/http-field-pass].[jsp]]
Servlet.service() for servlet jsp threw exception
java.lang.RuntimeException: No MemoryContext exists for
ai028-q8bzp-fc6gnyco-1-fc6gqut5-26
at
org.jboss.virtual.plugins.context.memory.MemoryContextFactory.putFile(MemoryContextFactory.java:156)
at
org.jboss.aop.asintegration.jboss5.JBoss5ClassPool.toClass(JBoss5ClassPool.java:100)
at javassist.CtClass.toClass(CtClass.java:1089)
at
org.jboss.aop.instrument.TransformerCommon$ToClassAction$2.toClass(TransformerCommon.java:293)
at
org.jboss.aop.instrument.TransformerCommon.toClass(TransformerCommon.java:128)
at
org.jboss.aop.instrument.JoinPointGenerator.toClass(JoinPointGenerator.java:327)
at
org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:290)
at
org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:77)
at
org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$2.generateJoinPointClass(JoinPointGenerator.java:1672)
at
org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:251)
at
org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1031)
at
org.jboss.test.cluster.web.aop.Person$PersonAdvisor.Person$PersonAdvisor$name_w_$aop(Person$PersonAdvisor.java)
at org.jboss.test.cluster.web.aop.Person.name_w_$aop(Person.java)
at org.jboss.test.cluster.web.aop.Person.<init>(Person.java:38)
at org.apache.jsp.setSession_jsp._jspService(setSession_jsp.java:65)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
at
org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:89)
at
org.jboss.web.tomcat.service.session.BatchReplicationClusteredSessionValve.invoke(BatchReplicationClusteredSessionValve.java:102)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:309)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Dimitris Andreadis wrote:
That would be best because the two files are (and will get more and
more) out-of-sync.
Scott M Stark wrote:
> Yes, would need to switch the config around again. We had talked about
> breaking the bootstrap-beans.xml up to make it easier to change
> features without updating the bootstrap file.
>
> I'm just getting back online as I had to relocate due to power outage
> after yet another storm.
>
> Dimitris Andreadis wrote:
>> I switched the profileservice configuration in the testsuite, that
>> uses bootstrap-repo-beans.xml to use the new VFS classloader and it
>> now boots normally.
>>
>> That could mean however that we'll have problems switching back to
>> the old unified classloader, if needed?
>>
>> Dimitris Andreadis wrote:
>>> In that latest run, the profile service config didn't start properly.
>>>
>>> I guess it's because of WarClassLoaderDeployer changes not synched
>>> with the testsuite?
>>>
>>>
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>
>>>
>>> 2008-02-01 08:44:07,356 ERROR
>>> [org.jboss.system.server.profileservice.ProfileServiceBootstrap]
>>> Failed to load profile: Summary of incomplete deployments (SEE
>>> PREVIOUS ERRORS FOR DETAILS):
>>>
>>> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required
>>> State:Actual State}
>>>
>>> WarClassLoaderDeployer
>>> -> ClassLoading{Configured:** NOT FOUND **}
>>> -> ClassLoaderSystem{Configured:** NOT FOUND **}
>>>
>>>
>>> *** CONTEXTS IN ERROR: Name -> Error
>>>
>>> ClassLoaderSystem -> ** NOT FOUND **
>>>
>>> ClassLoading -> ** NOT FOUND **
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jboss-development
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com