6 Replies Latest reply on May 15, 2008 3:25 AM by Shoeb Khan

    Worker thread initialization failure

    Mirko Steinicke Newbie

      hey guys

      my two-node cluster finally is running. load-balancing works just fine. failover isn't tested yet.

      The only thing that is annoying me is that from time to time the follwing Exception occurs. But it seems as if the application doesn't care when it's raised.

      10:45:35,359 ERROR [ServerThread] Worker thread initialization failure
      java.io.EOFException
       at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:526)
       at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:369)
       at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
      


      does anyone know how to solve this problem?

      thanks in advance.

      morki

        • 1. Re: Worker thread initialization failure
          Hari Sundharesan Newbie

          here is a thread discussing about the same problem
          http://lists.jboss.org/pipermail/jboss-development/2007-May/008622.html

          the thing is the jboss-remoting bundled with the 4.2.1 has this problem. try reverting the jboss-remoting.jar under server/all/lib with the previous version (from jboss-4.0.5/server/all/lib) and it will work fine

          Hari

          • 2. Re: Worker thread initialization failure
            Jim Williams Newbie

            I'm getting the same thing using 4.2.1 server, with JBoss Messaging 1.3GA . When my JMS clients try to connect to the JMS server, they are failing with the following:

            Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
             java.io.OptionalDataException
            event stack trace: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
             java.io.OptionalDataException
             at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306)
             at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
             at org.jboss.remoting.Client.invoke(Client.java:525)
             at org.jboss.remoting.Client.invoke(Client.java:488)
             at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:175)
             at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:331)
             at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:194)
             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 $Proxy0.create(Unknown Source)
            


            The clients are using the correct jboss-messaging-client.jar.

            Are these two compatible, or should I be using another version of jboss messaging?




            • 3. Re: Worker thread initialization failure
              Brian Stansberry Master

              Suggest you post on the message user forum; you're more likely to get a useful response there.

              • 4. Re: Worker thread initialization failure
                sarfaraz Mandal Newbie

                I am using 4.2.2 GA.
                I too am getting similar error
                Caused by: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
                java.io.OptionalDataException
                at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306)
                at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
                at org.jboss.remoting.Client.invoke(Client.java:525)
                at org.jboss.remoting.Client.invoke(Client.java:488)
                at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:175)
                at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java: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 $Proxy0.create(Unknown Source)
                at com.pcm.rules.service.blaze.BlazeEJBExecutor.getEJBHandle(BlazeEJBExecutor.java:82)
                ... 5 more
                Caused by: java.io.OptionalDataException
                at java.io.ObjectInputStream.readObject0(Unknown Source)
                at java.io.ObjectInputStream.readObject(Unknown Source)
                at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
                at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
                at org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:48)
                at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
                ... 17 more

                Plz assist

                • 5. Re: Worker thread initialization failure
                  Brian Stansberry Master

                  Sorry, this is not a clustering question (the EJB is not clustered). Try the EJB or Remoting forums.

                  • 6. Re: Worker thread initialization failure
                    Shoeb Khan Newbie

                    It appears, to me , that the jbossall-client jar that you are using at your client side is not same as the one you have in your server installation path.

                    Make sure you have same version for jar on both client and server, rather take the jar from the server_home/client/ location and put it into your client.