10:19 a.m.
A quick reminder that before committing anything to AS trunk we are supposed to run the
smoke-tests-raw target against the 'all' configuration.
Currently I'm seeing 4 smoke tests failing:
...
[junit] Running org.jboss.test.classloader.test.ScopingUnitTestCase
[junit] Tests run: 8, Failures: 0, Errors: 1, Time elapsed: 6.141 sec
[junit] Test org.jboss.test.classloader.test.ScopingUnitTestCase FAILED
...
[junit] Running org.jboss.test.deployers.ear.test.EARAltDDConnectorDeploymentUnitTestCase
[junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.766 sec
[junit] Test org.jboss.test.deployers.ear.test.EARAltDDConnectorDeploymentUnitTestCase
FAILED
...
[junit] Running org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 13.875 sec
[junit] Test org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase FAILED
[junit] Running org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
[junit] Tests run: 5, Failures: 0, Errors: 3, Time elapsed: 9.532 sec
[junit] Test org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase FAILED
...
[junit] Running org.jboss.test.xml.DDValidatorUnitTestCase
[junit] Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 19.297 sec
[junit] Test org.jboss.test.xml.DDValidatorUnitTestCase FAILED
10:24 a.m.
On Tue, 2008-08-05 at 18:19 +0300, Dimitris Andreadis wrote:
A quick reminder that before committing anything to AS trunk we are
supposed to run the
smoke-tests-raw target against the 'all' configuration.
Currently I'm seeing 4 smoke tests failing:
...
[junit] Running org.jboss.test.classloader.test.ScopingUnitTestCase
[junit] Tests run: 8, Failures: 0, Errors: 1, Time elapsed: 6.141 sec
[junit] Test org.jboss.test.classloader.test.ScopingUnitTestCase FAILED
...
[junit] Running
org.jboss.test.deployers.ear.test.EARAltDDConnectorDeploymentUnitTestCase
[junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.766 sec
[junit] Test org.jboss.test.deployers.ear.test.EARAltDDConnectorDeploymentUnitTestCase
FAILED
...
The first two have been fixed for a while, but are waiting for updates
of classloader and deployers which Ales is doing tomorrow.
[junit] Running
org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 13.875 sec
[junit] Test org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
FAILED
[junit] Running org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
[junit] Tests run: 5, Failures: 0, Errors: 3, Time elapsed: 9.532 sec
[junit] Test org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase FAILED
...
These don't fail on Hudson?
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/lastBui...
[junit] Running org.jboss.test.xml.DDValidatorUnitTestCase
[junit] Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 19.297 sec
[junit] Test org.jboss.test.xml.DDValidatorUnitTestCase FAILED
This is a jboss-web.xml in the clustering tests that is failing
schema/dtd validation:
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/lastBui...
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
6:25 a.m.
It's due to huge serialization by
org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext.
See:
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext.readExternal(AbstractVFSDeploymentContext.java:390)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
It's the way we do VirtualFile serialization here - a direct
Serialization of VirtualFile root, meaning whole .ear structure gets
serializaed.
Where we could only need something like I did for VFSDeployment:
private void writeObject(ObjectOutputStream out) throws IOException,
URISyntaxException
{
URL url = rootUrl;
if (url == null)
{
VFS vfs = getRoot().getVFS();
url = vfs.getRoot().toURL();
}
String pathName = path;
if (pathName == null)
pathName = getRoot().getPathName();
out.defaultWriteObject();
ObjectOutputStream.PutField fields = out.putFields();
fields.put("rootUrl", url);
fields.put("path", pathName);
out.writeFields();
}
private void readObject(ObjectInputStream in) throws IOException,
ClassNotFoundException
{
in.defaultReadObject();
ObjectInputStream.GetField fields = in.readFields();
rootUrl = (URL) fields.get("rootUrl", null);
path = (String) fields.get("path", null);
}
It's on my todo list.
But the problem is, that in the case of VFSDeployment this is trivial,
since it's a single root.
In VFSDeploymentContext we need to change a few List<VirtualFile> to use
this.
But I think the real problem is, that tests are accessing server side
stuff - DeploymentContext - where they should really go over
ProfileService/DeploymentManager.
Scott Stark wrote:
I'm seeing these seam tests fail as well:
<testcase
classname="org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase"
name="testExample" time="8.563">
<error message="Java heap space"
type="java.lang.OutOfMemoryError">java.lang.OutOfMemoryError: Java heap
space
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.copyStreamAndClose(ZipEntryContext.java:1059)
at
org.jboss.virtual.plugins.context.zip.ZipBytesWrapper.<init>(ZipBytesWrapper.java:56)
at
org.jboss.virtual.plugins.context.zip.ZipStreamWrapper.<init>(ZipStreamWrapper.java:82)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.findEntry(ZipEntryContext.java:328)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.createZipSource(ZipEntryContext.java:284)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.init(ZipEntryContext.java:214)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.<init>(ZipEntryContext.java:145)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.<init>(ZipEntryContext.java:130)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContextFactory.getVFS(ZipEntryContextFactory.java:71)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContextFactory.getVFS(ZipEntryContextFactory.java:57)
at
org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.readObject(AbstractVirtualFileHandler.java:663)
at
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext.readExternal(AbstractVFSDeploymentContext.java:390)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
</error>
</testcase>
>> [junit] Running
org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
>> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 13.875 sec
>> [junit] Test
org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase FAILED
>> [junit] Running
org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
>> [junit] Tests run: 5, Failures: 0, Errors: 3, Time elapsed: 9.532 sec
>> [junit] Test org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
FAILED
>> ...
>>
>
> These don't fail on Hudson?
>
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/lastBui...
>
>
>
>> [junit] Running org.jboss.test.xml.DDValidatorUnitTestCase
>> [junit] Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 19.297 sec
>> [junit] Test org.jboss.test.xml.DDValidatorUnitTestCase FAILED
>>
>
>
> This is a jboss-web.xml in the clustering tests that is failing
> schema/dtd validation:
>
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/lastBui...
>
>
>> _______________________________________________
>> 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
7:35 a.m.
After Ales' upgrades and with a little tinkering with the other minor failures all the
smoke
test pass for me now.
Ales Justin wrote:
It's due to huge serialization by
org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext.
See:
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext.readExternal(AbstractVFSDeploymentContext.java:390)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
It's the way we do VirtualFile serialization here - a direct
Serialization of VirtualFile root, meaning whole .ear structure gets
serializaed.
Where we could only need something like I did for VFSDeployment:
private void writeObject(ObjectOutputStream out) throws IOException,
URISyntaxException
{
URL url = rootUrl;
if (url == null)
{
VFS vfs = getRoot().getVFS();
url = vfs.getRoot().toURL();
}
String pathName = path;
if (pathName == null)
pathName = getRoot().getPathName();
out.defaultWriteObject();
ObjectOutputStream.PutField fields = out.putFields();
fields.put("rootUrl", url);
fields.put("path", pathName);
out.writeFields();
}
private void readObject(ObjectInputStream in) throws IOException,
ClassNotFoundException
{
in.defaultReadObject();
ObjectInputStream.GetField fields = in.readFields();
rootUrl = (URL) fields.get("rootUrl", null);
path = (String) fields.get("path", null);
}
It's on my todo list.
But the problem is, that in the case of VFSDeployment this is trivial,
since it's a single root.
In VFSDeploymentContext we need to change a few List<VirtualFile> to use
this.
But I think the real problem is, that tests are accessing server side
stuff - DeploymentContext - where they should really go over
ProfileService/DeploymentManager.
Scott Stark wrote:
> I'm seeing these seam tests fail as well:
>
> <testcase
>
classname="org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase"
> name="testExample" time="8.563">
> <error message="Java heap space"
> type="java.lang.OutOfMemoryError">java.lang.OutOfMemoryError: Java
> heap space
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95)
> at
>
org.jboss.virtual.plugins.context.zip.ZipEntryContext.copyStreamAndClose(ZipEntryContext.java:1059)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipBytesWrapper.<init>(ZipBytesWrapper.java:56)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipStreamWrapper.<init>(ZipStreamWrapper.java:82)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipEntryContext.findEntry(ZipEntryContext.java:328)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipEntryContext.createZipSource(ZipEntryContext.java:284)
>
> at
> org.jboss.virtual.plugins.context.zip.ZipEntryContext.init(ZipEntryContext.java:214)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipEntryContext.<init>(ZipEntryContext.java:145)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipEntryContext.<init>(ZipEntryContext.java:130)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipEntryContextFactory.getVFS(ZipEntryContextFactory.java:71)
>
> at
>
org.jboss.virtual.plugins.context.zip.ZipEntryContextFactory.getVFS(ZipEntryContextFactory.java:57)
>
> at
>
org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.readObject(AbstractVirtualFileHandler.java:663)
>
> at
> java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
> at
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> at
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
> at
> java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> at
>
org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext.readExternal(AbstractVFSDeploymentContext.java:390)
>
> at
> java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
> </error>
> </testcase>
>
>>> [junit] Running
>>> org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
>>> [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 13.875 sec
>>> [junit] Test
>>> org.jboss.test.deployers.seam.test.SeamNumberguessExampleUnitTestCase
>>> FAILED
>>> [junit] Running
>>> org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
>>> [junit] Tests run: 5, Failures: 0, Errors: 3, Time elapsed: 9.532 sec
>>> [junit] Test
>>> org.jboss.test.deployers.seam.test.SeamVFSClassloadingUnitTestCase
>>> FAILED
>>> ...
>>>
>>
>> These don't fail on Hudson?
>>
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/lastBui...
>>
>>
>>
>>
>>> [junit] Running org.jboss.test.xml.DDValidatorUnitTestCase
>>> [junit] Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 19.297 sec
>>> [junit] Test org.jboss.test.xml.DDValidatorUnitTestCase FAILED
>>>
>>
>>
>> This is a jboss-web.xml in the clustering tests that is failing
>> schema/dtd validation:
>>
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/lastBui...
>>
>>
>>
>>> _______________________________________________
>>> 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
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
8:40 a.m.
I've removed deployers tests from smoke-tests,
as they were ported to use Managed API / ProfileService,
hence they must run in profileservice config (run -c profileservice).
Dimitris Andreadis wrote:
After Ales' upgrades and with a little tinkering with the other
minor
failures all the smoke test pass for me now.
1:17 p.m.
with the deployer test move we have +16 failures
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Ales Justin wrote:
I've removed deployers tests from smoke-tests,
as they were ported to use Managed API / ProfileService,
hence they must run in profileservice config (run -c profileservice).
Dimitris Andreadis wrote:
> After Ales' upgrades and with a little tinkering with the other minor
> failures all the smoke test pass for me now.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
2:45 p.m.
I've already fixed this two - where missing in profileservice config
includes:
org.jboss.test.deployers.jbas2904.test.EARDeploymentUnitTestCase.testEARDeployment
org.jboss.test.deployers.jbas2904.test.EARDeploymentUnitTestCase.unknown
I think these are failing due to previous DeployUnitTestCase failure.
At least that what happens to me locally.
Running PSUTC and JDUTC separately works OK.
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testWarDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEjb2xDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEarDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testMCBeansDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testSarDeployment
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testCreateQueue
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testRemoveQueue
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testCreateTopic
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testRemoveTopic
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddXADataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveXADataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddNoTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveNoTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddNoTxDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveNoTxDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testDeploymentNames
I need to check this one:
org.jboss.test.web.test.WebIntegrationUnitTestCase.unknown
Initial lookup doesn't tell me much:
vfszip:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/jbosstest-web.ear
-> LifecycleException: Pipeline has not been started
Dimitris Andreadis wrote:
with the deployer test move we have +16 failures
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Ales Justin wrote:
> I've removed deployers tests from smoke-tests,
> as they were ported to use Managed API / ProfileService,
> hence they must run in profileservice config (run -c profileservice).
>
> Dimitris Andreadis wrote:
>> After Ales' upgrades and with a little tinkering with the other minor
>> failures all the smoke test pass for me now.
> _______________________________________________
> 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
7:03 p.m.
I'm looking at the DeployUnitTestCase. None of its deployments are being
deleted as they should. The ProfileServiceUnitTestCase runs fine
otherwise, but I'm seeing the following CNFE for the
JmsDestinationUnitTestCase queue/topic creation. Looking into that as well.
java.lang.ClassNotFoundException:
org.jboss.profileservice.management.templates.JmsDestinationTemplateInfo
at
org.jboss.remoting.serialization.ClassLoaderUtility.loadClass(ClassLoaderUtility.java:103)
at
org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:86)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at
org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:176)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:119)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObjectVersion2_2(JavaSerializationManager.java:233)
at
org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:133)
at
org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:123)
at
org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:59)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1215)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:845)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:160)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.getTemplate(AOPProxy$1.java)
at
org.jboss.test.profileservice.test.AbstractProfileServiceTest.createComponentTest(AbstractProfileServiceTest.java:83)
at
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase.testCreateQueue(JmsDestinationUnitTestCase.java:78)
Ales Justin wrote:
I've already fixed this two - where missing in profileservice
config
includes:
org.jboss.test.deployers.jbas2904.test.EARDeploymentUnitTestCase.testEARDeployment
org.jboss.test.deployers.jbas2904.test.EARDeploymentUnitTestCase.unknown
I think these are failing due to previous DeployUnitTestCase failure.
At least that what happens to me locally.
Running PSUTC and JDUTC separately works OK.
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testWarDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEjb2xDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEarDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testMCBeansDeployment
org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testSarDeployment
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testCreateQueue
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testRemoveQueue
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testCreateTopic
org.jboss.test.profileservice.test.JmsDestinationUnitTestCase(profileservice).testRemoveTopic
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddXADataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveXADataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddNoTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveNoTxConnectionFactory
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testAddNoTxDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testRemoveNoTxDataSource
org.jboss.test.profileservice.test.ProfileServiceUnitTestCase(profileservice).testDeploymentNames
I need to check this one:
org.jboss.test.web.test.WebIntegrationUnitTestCase.unknown
Initial lookup doesn't tell me much:
vfszip:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/jbosstest-web.ear
-> LifecycleException: Pipeline has not been started
Dimitris Andreadis wrote:
> with the deployer test move we have +16 failures
>
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> Ales Justin wrote:
>> I've removed deployers tests from smoke-tests,
>> as they were ported to use Managed API / ProfileService,
>> hence they must run in profileservice config (run -c profileservice).
>>
>> Dimitris Andreadis wrote:
>>> After Ales' upgrades and with a little tinkering with the other
>>> minor failures all the smoke test pass for me now.
>> _______________________________________________
>> 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
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5:46 a.m.
This one also passes for me locally,
as a single test:
one-test:
[delete] Deleting: C:\DOCUME~1\Ales\LOCALS~1\Temp\test.log
[junit] Running org.jboss.test.web.test.WebIntegrationUnitTestCase
[junit] Tests run: 37, Failures: 0, Errors: 0, Time elapsed: 24,281 sec
BUILD SUCCESSFUL
It's probably some leftover from PS tests
that makes it fail.
> I need to check this one:
>
> org.jboss.test.web.test.WebIntegrationUnitTestCase.unknown
>
> Initial lookup doesn't tell me much:
>
>
vfszip:/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/jbosstest-web.ear
> -> LifecycleException: Pipeline has not been started
7:17 a.m.
This is due to inconsistency in how we handle deployment names in PS.
Sometimes we pass in simple name, some times full repository name.
What should it be?
Since ManagedAPI mostly works on simple name.
But Deployment's name is full repo name.
And SerializableDeploymentRepository mostly uses
File/VirtualFile root + child's name.
I'll see if I can unify the usage.
Scott Stark wrote:
I'm looking at the DeployUnitTestCase. None of its deployments
are being
deleted as they should.
7:28 a.m.
I'm back to just testEjb3xDeployment failing in DeployUTC.
Some jndi issue. EJB3 guys?
MC fixed your MDR, return the favor. :-)
Testcase: testWarDeployment took 3,641 sec
Testcase: testEjb3xDeployment took 4,078 sec
Caused an ERROR
remote not bound
javax.naming.NameNotFoundException: remote not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:564)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:572)
at org.jnp.server.NamingServer.getObject(NamingServer.java:578)
at org.jnp.server.NamingServer.lookup(NamingServer.java:317)
at org.jnp.server.NamingServer.lookup(NamingServer.java:291)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at
java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
at
java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
at $Proxy0.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
org.jboss.test.profileservice.test.DeployUnitTestCase$1.testManagedDeployment(DeployUnitTestCase.java:158)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testDeployment(DeployUnitTestCase.java:117)
at
org.jboss.test.profileservice.test.DeployUnitTestCase.testEjb3xDeployment(DeployUnitTestCase.java:163)
Testcase: testEjb2xDeployment took 1,453 sec
Testcase: testEarDeployment took 1,39 sec
Testcase: testMCBeansDeployment took 0,204 sec
Testcase: testSarDeployment took 0,203 sec
Scott Stark wrote:
I'm looking at the DeployUnitTestCase. None of its deployments
are being
deleted as they should.
5972
days inactive
5988
days old
jboss-development@lists.jboss.org
11 comments
4 participants
participants (4)
-
Adrian Brock -
Ales Justin -
Dimitris Andreadis -
Scott Stark