-
1. Re: Socket error on start-up with 1.0.1.CR2 !
heat23 Jun 12, 2006 1:24 PM (in response to heat23)I installed the same things on a Windows server and I do not get that error. That error was from Solaris 10.
-
2. Re: Socket error on start-up with 1.0.1.CR2 !
timfox Jun 12, 2006 1:31 PM (in response to heat23)Are you sure there wasn't some firewall issue on your solaris setup, or port already in use.
The error happens when jboss remoting tries to create a server socket and this fails, this would be consistent with the port already being in use or some policy in place preventing you from creating server sockets. -
3. Re: Socket error on start-up with 1.0.1.CR2 !
heat23 Jun 12, 2006 1:35 PM (in response to heat23)This only happens in 1.0.1.CR2 on Solaris. With 1.0.0.GA I do not see this problem.
-
4. Re: Socket error on start-up with 1.0.1.CR2 !
timfox Jun 12, 2006 1:40 PM (in response to heat23)Can you post the full error from the logs?
-
5. Re: Socket error on start-up with 1.0.1.CR2 !
heat23 Jun 12, 2006 3:35 PM (in response to heat23)2006-06-12 14:33:46,299 ERROR [org.jboss.remoting.transport.socket.SocketServerInvoker] Failed to accept socket connection
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:194)
at org.jboss.remoting.transport.socket.ServerThread.(ServerThread.java:94)
at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:433)
at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:387)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: Mismatch version of JBossSerialization signature
at org.jboss.serial.io.JBossObjectInputStream.checkSignature(JBossObjectInputStream.java:113)
at org.jboss.serial.io.JBossObjectInputStream.(JBossObjectInputStream.java:94)
at org.jboss.remoting.serialization.impl.jboss.JBossSerializationManager.createInput(JBossSerializationManager.java:58)
at org.jboss.remoting.transport.socket.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:56)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
at org.jboss.remoting.transport.socket.ClientSocketWrapper.(ClientSocketWrapper.java:54)
at org.jboss.remoting.transport.socket.ServerSocketWrapper.(ServerSocketWrapper.java:50)
... 9 more -
6. Re: Socket error on start-up with 1.0.1.CR2 !
timfox Jun 13, 2006 12:51 AM (in response to heat23)This:
Caused by: java.io.IOException: Mismatch version of JBossSerialization signature
Tells me you have different versions of jboss serialization on the client and server side hence the incompatibility.
Most likely you are running a 1.0 client against a 1.0.1 server or vice versa.
This is the reason for your other problem too. -
7. Re: Socket error on start-up with 1.0.1.CR2 !
heat23 Jun 13, 2006 3:29 AM (in response to heat23)I get that error on server startup, so the client does not come into play yet. I've done clean installs of the AS and Messaging CR2 serveral times and I get that error on my Solaris box. If I do ./run.sh -c default, it works fine but ./run.sh -c messaging throws that error.
Is there any difference in what ports are used between 1.0 GA (which works fine) and CR2? -
8. Re: Socket error on start-up with 1.0.1.CR2 !
heat23 Jun 13, 2006 11:40 AM (in response to heat23)Anyone know?
This is very urgent.
Thanks -
9. Re: Socket error on start-up with 1.0.1.CR2 !
genman Jun 13, 2006 1:22 PM (in response to heat23)
It is likely that the two versions were released with different versions of JBoss serialization. You likely have a version mismatch between the two. -
10. Re: Socket error on start-up with 1.0.1.CR2 !
heat23 Jun 13, 2006 1:25 PM (in response to heat23)I did a clean install of Jboss AS 4.0.4 GA and of Messaging 1.0.1.CR2. What do I need to do to sych them up?
-
11. Re: Socket error on start-up with 1.0.1.CR2 !
timfox Jun 18, 2006 2:21 PM (in response to heat23)4.0.4GA has been tested against 1.0.1CR2 from a fresh install and passes the smoke tests fine.
I can only assume you haven't cleaned everything properly...
I spoke to Clebert (the JbossSerialization lead) and he informs me that the error you are getting "Mismatch version of JBossSerialization signature" can be caused by 2 issues:
1. Use of different serialization versions for serialization and deserialization
2. acking trove.jar or log4j on the client.