Re: [jboss-dev] JBoss-AS-5.0.x-TestSuite-sun15
I'm trying to get my env in place, and I'm seeing these exceptions I had
not seen in my home workspace. Are these showing up for others?
11:33:36,781 ERROR [AbstractKernelController] Error installing to
PreInstall: name=WSMemoryBufferRecorder state=Real
java.lang.ClassNotFoundException:
org.jboss.wsf.framework.management.recording.MemoryBufferRecorder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:204)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1006)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:584)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:234)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at
org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.resolveComplexTypeInfo(IntrospectionTypeInfoFactoryImpl.java:375)
at
org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getTypeInfo(IntrospectionTypeInfoFactoryImpl.java:344)
at
org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory.getTypeInfo(IntrospectionTypeInfoFactory.java:54)
at
org.jboss.classadapter.plugins.BasicClassAdapterFactory.getClassAdapter(BasicClassAdapterFactory.java:61)
at
org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:70)
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
>