RE: [jboss-dev] [Fwd: Re: jboss remoting 2.2.0.SPx update]
I will take a look at the compatibility matrix testsuite to get a valid run.
_____
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Ron Sigal
Sent: Wednesday, May 09, 2007 1:43 PM
To: jboss-development(a)lists.jboss.org
Subject: [jboss-dev] [Fwd: Re: jboss remoting 2.2.0.SPx update]
1. I'm confused about the NotSerializableException -
org.jboss.invocation.Invocation in trunk/server/src/main really *isn't*
serializable. ???
2. All of the errors in the compatibility testsuite seem to be
"unsupported classversion 49.0". But I created the Remoting 2.2.0.SP4
jar with jdk 1.4.2_14-b05. ???
3. Also, for the socket transport, pooled connection checking has to be
compatible - "socket.check_connection" attribute.
-Ron
Dimitris Andreadis wrote:
I updated Branch_4_2 to remoting 2.2.0.SP4 and added the
-Djboss.remoting.pre_2_0_compatible=true flag on the server side, but
that doesn't fix the compatibility testsuite.
http://jira.jboss.com/jira/browse/JBAS-4407
Also the latest jboss AS testsuite run is full of those exceptions:
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.2-testsuite-sun-1.5/2007
0509091300/results/index.html
Failed to communicate. Problem during marshalling/unmarshalling;
nested exception is: java.io.NotSerializableException:
org.jboss.invocation.Invocation
java.rmi.MarshalException: Failed to communicate. Problem during
marshalling/unmarshalling; nested exception is:
java.io.NotSerializableException: org.jboss.invocation.Invocation
at
org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(Sock
etClientInvoker.java:122)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(Micro
SocketClientInvoker.java:641)
at
org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.
java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at
org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedIn
vokerProxy.java:175)
at
org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.jav
a:365)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61
)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at
org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy1.findAll(Unknown Source)
at
org.jboss.test.bank.test.BankStressTestCase.setUp(BankStressTestCase.java:46
2)
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)
Caused by: java.io.NotSerializableException:
org.jboss.invocation.Invocation
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at
org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObje
ctVersion2_2(JavaSerializationManager.java:120)
at
org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObje
ct(JavaSerializationManager.java:95)
at
org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(Seriali
zableMarshaller.java:120)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(
MicroSocketClientInvoker.java:964)
at
org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(Micro
SocketClientInvoker.java:554)
... 28 more
Attachments:
- attachment.html (text/html — 18.9 KB)