compatibility-matrix remaining failures
by Dimitris Andreadis
The bulk of the compatibility-matrix failures is resolved.
What's left now is the appclient tests:
https://jira.jboss.org/jira/browse/JBAS-6208
The 4.2.x side uses AOP 1.5.6.GA while the 5.x server uses AOP 2.0.0.GA
The error on the client side is the own below, and on the server side at the bottom.
Is this supposed to work?
Client Side ---
*** DEPLOYMENTS IN ERROR: Name -> Error
ClassLoaderSystem -> java.lang.NoSuchMethodError:
org.jboss.aop.AspectManager.addArrayReplacement(Lorg/jboss/aop/array/ArrayReplacement;)V
ClientLauncherClassPath:0.0.0$MODULE -> java.lang.NoSuchMethodError:
org.jboss.aop.AspectManager.getManagerFQN()Ljava/lang/String;
ClassLoading -> java.lang.NoSuchMethodError:
org.jboss.aop.AspectManager.getManagerFQN()Ljava/lang/String;
ClientLauncherClassPath:0.0.0 -> java.lang.NoSuchMethodError:
org.jboss.aop.AspectManager.getManagerFQN()Ljava/lang/String;
*** DEPLOYMENTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
ClientContainer -> ClientLauncherClassPath:0.0.0{Installed:**ERROR**}, null{Installed:**
UNRESOLVED JndiDepends: 'test-client/metaData' **}
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:290)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174)
at org.jboss.ejb3.client.ClientLauncher.validate(ClientLauncher.java:471)
at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:269)
at org.jboss.ejb3.client.ClientLauncher.launch(ClientLauncher.java:174)
at
org.jboss.test.client.test.AppClientUnitTestCase.testClientLauncher(AppClientUnitTestCase.java:67)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at
org.jboss.test.compatibility.test.matrix.MatrixTestContainer$TestProxy.run(MatrixTestContainer.java:185)
at
org.jboss.test.compatibility.test.matrix.MatrixTestContainer$TestSuiteProxy.run(MatrixTestContainer.java:85)/
--- Server Side
Caused by: java.lang.ClassNotFoundException: org.jboss.resource.adapter.jms.infl
ow.JmsActivationSpec from BaseClassLoader@100b8b{VFSClassLoaderPolicy@1660e34{na
me=vfszip:/X:/cvs/jboss-public/jboss-head/build/output/jboss-5.0.0.GA/server/def
ault/deploy/jms-ra.rar domain=ClassLoaderDomain@951a0{name=DefaultDomain parentP
olicy=BEFORE parent=org.jboss.system.NoAnnotationURLClassLoader@fe64b9} roots=[M
emoryContextHandler@19832209[path= context=vfsmemory://5c4o0m-mfjij4-fnos5mto-1-
fnos61xx-1q real=vfsmemory://5c4o0m-mfjij4-fnos5mto-1-fnos61xx-1q], DelegatingHa
ndler(a)23773478[path=jms-ra.rar context=file:/X:/cvs/jboss-public/jboss-head/buil
d/output/jboss-5.0.0.GA/server/default/deploy/ real=file:/X:/cvs/jboss-public/jb
oss-head/build/output/jboss-5.0.0.GA/server/default/deploy/jms-ra.rar], Delegati
ngHandler(a)28235713[path=jms-ra.rar/jms-ra.jar context=file:/X:/cvs/jboss-public/
jboss-head/build/output/jboss-5.0.0.GA/server/default/deploy/ real=file:/X:/cvs/
jboss-public/jboss-head/build/output/jboss-5.0.0.GA/server/default/deploy/jms-ra
.rar/jms-ra.jar]] delegates=null exported=[org.jboss.resource.adapter.jms, META
-INF, org.jboss.resource.adapter.jms.inflow.dlq, org.jboss.resource.adapter.jms.
inflow] <IMPORT-ALL>NON_EMPTY}}
at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoa
der.java:385)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.resource.deployment.ActivationSpecFactory.createActivationS
pec(ActivationSpecFactory.java:107)
at org.jboss.resource.deployers.RARDeployment.createActivationSpec(RARDe
ployment.java:313)
at org.jboss.resource.deployers.RARDeployment.internalInvoke(RARDeployme
nt.java:276)
at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBea
nSupport.java:156)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:1
64)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory.createActiva
tionSpec(JBossMessageEndpointFactory.java:449)
17 years
AS testsuite server configs do not start
by Anil Saldhana
Has anyone able to get a decent run of "ant tests-jacc-security", "ant
tests-security-manager" or "ant tests-jacc-securitymgr"? I updated the
workspace today and none of the server configs are working. The AS in
the server config start and then immediately go on to the shutdown cycle.
Something wrong with the JBoss Server Manager update?
17 years
compatibility-matrix failures and org.jboss.invocation
by Dimitris Andreadis
Looking in the compatibility-matrix test failures:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Comp...
The majority of failures are caused by our Branch_4_2 having deviated a lot from trunk.
Most of the changes are related to the introduction of
org.jboss.invocation.unified.interfaces.JavaSerializationManager
There are also classes that are missing from trunk, like:
ByValueInvokerInterceptor
DataContainerMarshallingInvokerInterceptor
MarshalledValueEX
I've forward porteded the changes and they seems ok; at least locally.
Are there any concerns for not committing this?
17 years
minimal doesn't boot
by Dimitris Andreadis
Just updated to the latest and the minimal config doesn't boot:
10:40:18,593 INFO [JMXKernel] Legacy JMX core initialized
10:40:20,484 INFO [MetaDataAwareProfile] Using profile root:X:\cvs\jboss-public
\jboss-head\build\output\jboss-5.0.0.GA\server\minimal
Failed to boot JBoss:
java.lang.NullPointerException
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBo
otstrapMDs(ProfileServiceBootstrap.java:467)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(
ProfileServiceBootstrap.java:213)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
404)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:595)
10:40:20,609 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
10:40:21,265 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
17 years
Header update
by Dimitris Andreadis
I am changing the trunk copyright headers from "JBoss Inc" to "Red Hat Middleware LLC".
https://jira.jboss.org/jira/browse/JBAS-3916
As Ales points out that's my chance to score commit points ;)
If there are any problems with the eol characters let me know, as I see not all files are
marked as svn:eol native
Cheers
/D
/*
* JBoss, Home of Professional Open Source.
* Copyright 2008, Red Hat Middleware LLC, and individual contributors
* as indicated by the @author tags. See the copyright.txt file in the
* distribution for a full listing of individual contributors.
*
* This is free software; you can redistribute it and/or modify it
* under the terms of the GNU Lesser General Public License as
* published by the Free Software Foundation; either version 2.1 of
* the License, or (at your option) any later version.
*
* This software is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this software; if not, write to the Free
* Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
* 02110-1301 USA, or see the FSF site: http://www.fsf.org.
*/
17 years
new shared JBOSS_HOME/server/lib directory
by Dimitris Andreadis
The new JBOSS_HOME/server/lib directory pointed to at by the jboss.shared.lib.url property
currently contains the libraries shared by the default and all configurations.
So server/default/lib is now empty and server/all/lib contains only:
avalon-framework.jar
hibernate-jbosscache2.jar
jacorb.jar
jbosscache-core.jar
jbosscache-pojo.jar
jgroups.jar
The new directory is added to the classpath in conf/jboss-service.xml:
<classpath codebase="${jboss.server.lib.url}" archives="*"/>
<classpath codebase="${jboss.shared.lib.url}" archives="*"/>
The minimal config remains unchanged.
https://jira.jboss.org/jira/browse/JBAS-6158
You probably need to cleanup your build/output/** directory to pick up the change at your
next svn update.
17 years
