1 2 Previous Next 24 Replies Latest reply on Apr 11, 2007 4:13 AM by Ron Sigal

    Connection between servers through JNDI?

    Michael Voss Newbie

      using JNDI discovery and starting several servers:
      Why there are Socket connection tries(TIME_WAIT) between the servers???

      (using sslmultiplex the client can not connect to the servers and produces some exception )

        • 1. Re: Connection between servers through JNDI?
          Tom Elrod Master

          Can you be more specific? You mean the time the jndi detector waits before getting detection messages from a JNDI server?

          • 2. Re: Connection between servers through JNDI?
            Michael Voss Newbie

            If I start two servers on different computers and a JNDIServer on another separate system then there is a TCP connection between the servers (in state TIME_WAIT)

            I think this should not happen...

            If now a client tries to connect to one of the servers then performing client=new Client(...) throws an java.io.InterruptedException

            I am still using sslmultiplex from JBREM v1.4.1

            Don' t know if this bug is known and already fixed or not noticed yet

            • 3. Re: Connection between servers through JNDI?
              Tom Elrod Master

              I have been using SimpleDetectorClient, SimpleDetectorServer, and SimpleJNDIServer classes of the org.jboss.remoting.samples.detection.jndi package to help in discovering the problem you are seeing.

              First off, looks like one issue is the way the AbstractDetector does its connection validation when it thinks a server has gone down. Currently it uses a client invoker to send a ping invocation. The problem is that there are no constraints on the timeout of the invocation, so could wait as long as 30 mintues (default) for socket timeout. Obviously this is too long to wait for connection validation in most cases. I have the changes locally on my machine and will commit to cvs (after open a jira issue to tie it to).

              I have fixed this by wrapping the ping invocation so will timeout external to the call itself. This has fixed the problem where detection of dead servers is delayed by the transport timeout.

              However, I have found another issue that still needs looking into. If using multiplex transport and a server is killed and then re-started, it looks like the detector sees the server restarting, then tries to ping it, but can not, so discards it as being dead, then repeats this process. This does not happen when using socket transport, so looks like there is some issue where multiplex client is having trouble making invocations on a server after it has gone down and then come back up.

              • 4. Re: Connection between servers through JNDI?
                Michael Voss Newbie

                But why do the servers receive messages from other servers, thought they would only send their heartbeat messages to JNDI server...
                So could you please tell me why there are those connections between the servers? I think a server should not build up a connection to another server?!

                Because of this connection client can not connect to the servers

                Did you already open a jira issue, or shall I?

                • 5. Re: Connection between servers through JNDI?
                  Tom Elrod Master

                  Remoting detectors act as broadcasters of detection messages (containing info on remoting servers running within its jvm) AND monitor topology of other remoting servers on the network (thus require the heartbeat ping).

                  Have created jira issue for the connection check timeout problem - http://jira.jboss.com/jira/browse/JBREM-530

                  • 6. Re: Connection between servers through JNDI?
                    Michael Voss Newbie

                    There is no way to adjust, that servers must not connect to the other srevers? Or does this possibility exist?

                    • 7. Re: Connection between servers through JNDI?
                      Tom Elrod Master

                      Would require breaking out the behavior into two separate classes. So that one is the broadcaster and one would be the consumer. From a coding standpoint, this is not too difficult. However, just adds more complexity to doing detection.

                      Don't mind changing the code to allow for this, but am more concerned about not understanding the use case for this. Is it that you don't want the servers to have knowledge of other servers? By the way, the specific problem you are having seems to be directly related to the multiplex transport and not necessarily related to remoting detection (as I understand it).

                      • 8. Re: Connection between servers through JNDI?
                        Tom Elrod Master

                        Created jira issue for the multiplex client re-connect issue - http://jira.jboss.com/jira/browse/JBREM-534.

                        • 9. Re: Connection between servers through JNDI?
                          Claudia Richter Newbie

                          Hi,
                          I wonder why this jira issue (http://jira.jboss.com/jira/browse/JBREM-534) has been closed. Is it fixed already? I am using Remoting Versions 2.0.0 CR1 and 2.0.0 GA. And I have exactly the problem, that when killing a server and restarting it afterwards with another protocol (I tried socket, multiplex, sslsocket and sslmultiplex) it fails to receive an incoming connection (I guess it's a heartbeat from the JNDI trying to reach the old protocol) and after a while shuts down itself.

                          The method which I use to connect my Server with the JNDI looks as follows:

                          private JNDIDetector detector;
                          
                          public void setupConnection(int port, String host) throws Exception {
                          
                          MBeanServer server = MBeanServerFactory.createMBeanServer();
                          
                           detector = new JNDIDetector();
                           detector.setPort(port);
                           detector.setHost(host);
                           ObjectName name = new ObjectName("remoting:type=JNDIDetector");
                          
                           server.registerMBean(detector, name);
                           detector.start();
                          }
                          


                          Anyway, I found a workaround, that runs for my Application. But this requires to set the Clean Detection Number to zero:

                          private JNDIDetector detector;
                          
                          public void setupConnection(int port, String host) throws Exception {
                          MBeanServer server = MBeanServerFactory.createMBeanServer();
                          
                           detector = new JNDIDetector();
                           detector.setPort(port);
                           detector.setHost(host);
                           detector.setCleanDetectionNumber(0);
                           ObjectName name = new ObjectName("remoting:type=JNDIDetector");
                           detector.preRegister(server, name);
                          
                           detector.start();
                           server.registerMBean(detector, name);
                           detector.forceDetection();
                          }


                          I guess this is not the way a JNDI connection should be build up?! And if this is a Bug, shall I open a new jira issue?

                          • 10. Re: Connection between servers through JNDI?
                            Ron Sigal Master

                            Hi,

                            JBREM-534 was specific to multiplex, and it looks like the changes that led to the closing of JBREM-534 were included in the 2.0.0 CR1 and GA releases. I think, therefore, that you are seeing some other phenomenon.

                            I don't quite understand, yet, what you seeing. First of all, let me describe the difference between a "clean" detection and a "non-clean" detection (I don't think we have an official name for the latter). In the latter case, the detector believes whatever information it gets from the JNDI server and uses it to update its local information. In the case of a clean detection, it actually tried to ping each server to see for itself if the server is alive or not. The value of the Clean Detection Number indicates how many times to do a "non-clean" detection before doing a clean detection, so setting it to zero is not terrible; it just causes some additional network traffic, but gets you a more reliable picture of the state of the servers in the domain.

                            Anyway, it would be natural for the first clean detection after a server goes down to result in a failed attempt to contact the defunct server. However, it should also be the case that when the detector discovers a new server and informs your client of the new server's InvokerLocator, your client should be able to contact the new server. Are you saying that the latter is not happening? If so (or if not), could you elaborate on what you are trying to do and what is and is not happening? Thanks.

                            • 11. Re: Connection between servers through JNDI?
                              Claudia Richter Newbie

                              exactly. My Client is not able to access my Server after killing the Server and restarting it with a new Protocol. I need to restart the Server a second time, before my Client is able to connect to it. The funny thing is, that Detection works perfectly even after the first restart.

                              Here's a dump of what I see on the Server in different cases:

                              ******** start Server with multiplex protocol*********

                              reqistering with JNDI server
                              2007-03-02 09:11:33,325 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                              2007-03-02 09:11:33,325 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                              susseccfully reqistered with JNDI Server
                              2007-03-02 09:11:34,341 INFO [Remoting Detector - Heartbeat Thread: 1] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                              2007-03-02 09:11:39,340 WARN [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [socket://anotherhost:1101/]
                              


                              ******* restart same server with multiplex********

                              reqistering with JNDI server
                              2007-03-02 09:13:41,790 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                              2007-03-02 09:13:41,790 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                              successfully reqistered with JNDI Server
                              



                              ******* restart same Server with new protocol socket********

                              reqistering with JNDI server
                              2007-03-02 09:15:50,881 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                              2007-03-02 09:15:50,881 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                              susseccfully reqistered with JNDI Server
                              2007-03-02 09:15:56,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                              2007-03-02 09:15:56,130 ERROR [SocketServerInvoker#0-1101] 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(Unknown Source)
                               at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                               at java.lang.reflect.Constructor.newInstance(Unknown Source)
                               at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:198)
                               at org.jboss.remoting.transport.socket.ServerThread.<init>(ServerThread.java:95)
                               at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:492)
                               at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:444)
                               at java.lang.Thread.run(Unknown Source)
                              Caused by: java.io.StreamCorruptedException: invalid stream header
                               at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
                               at java.io.ObjectInputStream.<init>(Unknown Source)
                               at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
                               at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
                               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.<init>(ClientSocketWrapper.java:54)
                               at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
                               ... 9 more
                              2007-03-02 09:15:57,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
                              2007-03-02 09:15:57,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]: entering unRegisterSocket()
                              2007-03-02 09:15:57,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]starting ShutdownRequestThread: Thread[Thread-10:shutdownRequest:12948,5,main]
                              2007-03-02 09:16:02,051 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]: leaving unRegisterSocket()
                              2007-03-02 09:16:02,051 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264](1172823356052)
                              2007-03-02 09:16:02,051 INFO [Thread-10:shutdownRequest:12948] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
                              2007-03-02 09:16:02,051 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823356052): Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]
                              2007-03-02 09:16:02,067 WARN [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
                              2007-03-02 09:16:02,067 ERROR [SocketServerInvoker#0-1101] 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(Unknown Source)
                               at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                               at java.lang.reflect.Constructor.newInstance(Unknown Source)
                               at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:198)
                               at org.jboss.remoting.transport.socket.ServerThread.<init>(ServerThread.java:95)
                               at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:492)
                               at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:444)
                               at java.lang.Thread.run(Unknown Source)
                              Caused by: java.io.StreamCorruptedException: invalid stream header
                               at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
                               at java.io.ObjectInputStream.<init>(Unknown Source)
                               at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
                               at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
                               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.<init>(ClientSocketWrapper.java:54)
                               at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
                               ... 9 more
                              2007-03-02 09:16:02,067 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                              2007-03-02 09:16:03,067 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
                              2007-03-02 09:16:03,067 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]: entering unRegisterSocket()
                              2007-03-02 09:16:03,067 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]starting ShutdownRequestThread: Thread[Thread-12:shutdownRequest:12948,5,main]
                              2007-03-02 09:16:08,066 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]: leaving unRegisterSocket()
                              2007-03-02 09:16:08,066 WARN [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
                              2007-03-02 09:16:08,066 INFO [Thread-13:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267](1172823362067)
                              2007-03-02 09:16:08,066 INFO [Thread-12:shutdownRequest:12948] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
                              2007-03-02 09:16:08,066 INFO [Thread-13:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823362067): Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]
                              2007-03-02 09:16:16,127 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: entering shutdownThreads
                              2007-03-02 09:16:16,127 INFO [input:12948] org.jboss.remoting.transport.multiplex.InputMultiplexor: Selector is closed: shutting down input thread
                              2007-03-02 09:16:16,127 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: cancelling timer
                              2007-03-02 09:16:16,127 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: static threads shut down
                              
                              


                              ***** the Server now could be found by the JNDI, but could not be accessed by a Client anymore *********

                              ***** restarted Server with same protocol socket *******

                              reqistering with JNDI server
                              2007-03-02 09:22:55,291 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                              2007-03-02 09:22:55,291 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                              susseccfully reqistered with JNDI Server
                              2007-03-02 09:22:56,307 INFO [Remoting Detector - Heartbeat Thread: 1] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                              


                              ****** restarted Server with new protocol multiplex *******

                              reqistering with JNDI server
                              2007-03-02 09:24:11,015 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                              2007-03-02 09:24:11,015 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                              susseccfully reqistered with JNDI Server
                              2007-03-02 09:24:12,031 INFO [Remoting Detector - Heartbeat Thread: 1] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                              2007-03-02 09:24:13,296 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                              2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: entering unRegisterSocket()
                              2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: leaving unRegisterSocket()
                              2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: entering unRegisterSocket()
                              2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]starting ShutdownRequestThread: Thread[Thread-11:shutdownRequest:-14096,5,main]
                              2007-03-02 09:24:13,578 INFO [Thread-11:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: true
                              2007-03-02 09:24:13,578 INFO [Thread-11:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
                              2007-03-02 09:24:13,578 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: leaving unRegisterSocket()
                              2007-03-02 09:24:13,578 INFO [Thread-12:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=/127.0.0.1,port=1465,localport=1101](1172823853296)
                              2007-03-02 09:24:13,578 INFO [Thread-12:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823853296): Socket[addr=/127.0.0.1,port=1465,localport=1101]
                              2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: entering unRegisterSocket()
                              2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: leaving unRegisterSocket()
                              2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: entering unRegisterSocket()
                              2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]starting ShutdownRequestThread: Thread[Thread-14:shutdownRequest:-14096,5,main]
                              2007-03-02 09:24:15,390 INFO [Thread-14:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: true
                              2007-03-02 09:24:15,390 INFO [Thread-14:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
                              2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: leaving unRegisterSocket()
                              2007-03-02 09:24:15,390 INFO [Thread-15:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=/127.0.0.1,port=1470,localport=1101](1172823855218)
                              2007-03-02 09:24:15,390 INFO [Thread-15:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823855218): Socket[addr=/127.0.0.1,port=1470,localport=1101]
                              [...]
                              



                              ****** the Server could be found by the JNDI but not accessed by a Client anymore ******

                              The only difference between socket and multiplex protocol is that the socket protocol stops to print dumps, while the multiplex protocol prints always the same dump information.

                              • 12. Re: Connection between servers through JNDI?
                                Claudia Richter Newbie

                                I'm sorry for the previous reply. I tested my Server with the wrong Client. Could you please delete or (if not possible to delete) ignore this port? Thank you

                                • 13. Re: Connection between servers through JNDI?
                                  Claudia Richter Newbie

                                  A change from multiplex protocol to socket causes a lot of logging messages but does run.

                                  The other way round it does not. When killing a server that runs socket protocol and then restart it with multiplex protocol, it will not be detected by a JNDI and my Client is not able to connect to it. I need to restart the Server to be able to connect to it again.

                                  Here are the dumps I see:

                                  *****restarted server with same protocol multiplex ******

                                  reqistering with JNDI server
                                  2007-03-02 13:44:31,526 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                                  2007-03-02 13:44:31,526 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                                  susseccfully reqistered with JNDI Server
                                  


                                  ***** client test started ******

                                  ***** server dump after client start ****

                                  reqistering with JNDI server
                                  2007-03-02 13:44:31,526 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                                  2007-03-02 13:44:31,526 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                                  susseccfully reqistered with JNDI Server
                                  2007-03-02 13:44:58,057 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: leaving unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: leaving unRegisterSocket()
                                  2007-03-02 13:44:58,792 INFO [input:-32439] org.jboss.remoting.transport.multiplex.InputMultiplexor: java.io.IOException: An existing connection was forcibly closed by the remote host
                                  2007-03-02 13:44:58,792 INFO [input:-32439] org.jboss.remoting.transport.multiplex.InputMultiplexor: java.io.IOException: An existing connection was forcibly closed by the remote host
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: Failed to accept socket connection
                                  java.io.IOException: An existing connection was forcibly closed by the remote host
                                   at sun.nio.ch.SocketDispatcher.read0(Native Method)
                                   at sun.nio.ch.SocketDispatcher.read(Unknown Source)
                                   at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
                                   at sun.nio.ch.IOUtil.read(Unknown Source)
                                   at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread$GroupProcessor.processChannel(InputMultiplexor.java:332)
                                   at org.jboss.remoting.transport.multiplex.InputMultiplexor$MultiGroupInputThread.doRun(InputMultiplexor.java:293)
                                   at org.jboss.remoting.transport.multiplex.utility.StoppableThread.run(StoppableThread.java:54)
                                  2007-03-02 13:44:58,792 ERROR [MultiplexServerInvoker#0v-VirtualServerSocket[local address=/127.0.0.1:1101, remote address=/127.0.0.1:3697]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: maximum accept errors exceeded: stopping
                                  2007-03-02 13:44:58,792 INFO [output:-32439] org.jboss.remoting.transport.multiplex.OutputMultiplexor$OutputThread: java.nio.channels.ClosedChannelException
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]starting ShutdownRequestThread: Thread[Thread-12:shutdownRequest:-32439,5,main]
                                  2007-03-02 13:44:58,854 INFO [Thread-12:shutdownRequest:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:44:58,854 INFO [output:-32439] org.jboss.remoting.transport.multiplex.OutputMultiplexor$OutputThread: java.nio.channels.ClosedChannelException
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: scheduling ShutdownMonitorTask: shutdownRequest:-32439
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: leaving unRegisterSocket()
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3697,localport=1101]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3697,localport=1101]: leaving unRegisterSocket()
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3697,localport=1101]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3697,localport=1101]starting ShutdownRequestThread: Thread[Thread-13:shutdownRequest:-32439,5,main]
                                  2007-03-02 13:44:58,854 ERROR [Thread-13:shutdownRequest:-32439] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=/127.0.0.1,port=3697,localport=1101]
                                  2007-03-02 13:44:58,854 INFO [Thread-13:shutdownRequest:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3697,localport=1101]: scheduling ShutdownMonitorTask: shutdownRequest:-32439
                                  2007-03-02 13:44:58,854 INFO [pending actions:-32439] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3697,localport=1101]: leaving unRegisterSocket()
                                  2007-03-02 13:44:59,854 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3692,localport=1101]: ShutdownMonitorTimerTask: found requestShutdownFailed == true
                                  2007-03-02 13:44:59,870 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3697,localport=1101]: ShutdownMonitorTimerTask: found requestShutdownFailed == true
                                  2007-03-02 13:44:59,870 INFO [Thread-14:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=/127.0.0.1,port=3692,localport=1101](1172839498057)
                                  2007-03-02 13:44:59,870 INFO [Thread-14:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172839498057): Socket[addr=/127.0.0.1,port=3692,localport=1101]
                                  2007-03-02 13:44:59,870 INFO [Thread-15:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=/127.0.0.1,port=3697,localport=1101](1172839498370)
                                  2007-03-02 13:44:59,870 INFO [Thread-15:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172839498370): Socket[addr=/127.0.0.1,port=3697,localport=1101]
                                  2007-03-02 13:45:08,104 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: entering shutdownThreads
                                  2007-03-02 13:45:08,104 INFO [input:-32439] org.jboss.remoting.transport.multiplex.InputMultiplexor: Selector is closed: shutting down input thread
                                  2007-03-02 13:45:08,104 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: cancelling timer
                                  2007-03-02 13:45:08,104 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: static threads shut down
                                  


                                  ****** client dump ******

                                  connecting to JNDI Server
                                  2007-03-02 13:44:57,620 INFO [main] jndiClient.JNDIConnector: setting up connection to JNDI Server
                                  2007-03-02 13:44:57,651 INFO [main] jndiClient.JNDIConnector: register NetworkRegistry with MBean Server
                                  2007-03-02 13:44:57,917 INFO [main] jndiClient.JNDIConnector: getting available Servers from JNDI
                                  2007-03-02 13:44:58,042 INFO [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                                  multiplex://localhost:1101/
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]: leaving unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]: leaving unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]: leaving unRegisterSocket()
                                  2007-03-02 13:44:58,354 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]starting ShutdownRequestThread: Thread[Thread-10:shutdownRequest:-32454,5,main]
                                  2007-03-02 13:44:58,354 INFO [Thread-10:shutdownRequest:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:44:58,354 INFO [Thread-10:shutdownRequest:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:44:58,370 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3692]: scheduling ShutdownMonitorTask: shutdownRequest:-32454
                                  2007-03-02 13:44:58,573 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3697]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,573 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3697]: leaving unRegisterSocket()
                                  successfully handled this request
                                  2007-03-02 13:44:58,573 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3697]: entering unRegisterSocket()
                                  2007-03-02 13:44:58,573 INFO [pending actions:-32454] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3697]: leaving unRegisterSocket()
                                  


                                  ****** client test succeeded *******

                                  ****** restart Server with new protocol socket *******

                                  reqistering with JNDI server
                                  2007-03-02 13:48:27,885 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                                  2007-03-02 13:48:27,885 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                                  susseccfully reqistered with JNDI Server
                                  2007-03-02 13:48:32,964 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                                  2007-03-02 13:48:33,011 ERROR [SocketServerInvoker#0-1101] 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(Unknown Source)
                                   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                                   at java.lang.reflect.Constructor.newInstance(Unknown Source)
                                   at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:198)
                                   at org.jboss.remoting.transport.socket.ServerThread.<init>(ServerThread.java:95)
                                   at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:492)
                                   at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:444)
                                   at java.lang.Thread.run(Unknown Source)
                                  Caused by: java.io.StreamCorruptedException: invalid stream header
                                   at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
                                   at java.io.ObjectInputStream.<init>(Unknown Source)
                                   at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
                                   at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
                                   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.<init>(ClientSocketWrapper.java:54)
                                   at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
                                   ... 9 more
                                  2007-03-02 13:48:33,948 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
                                  2007-03-02 13:48:33,948 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3700]: entering unRegisterSocket()
                                  2007-03-02 13:48:33,948 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3700]starting ShutdownRequestThread: Thread[Thread-10:shutdownRequest:-14156,5,main]
                                  2007-03-02 13:48:38,949 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3700]: leaving unRegisterSocket()
                                  2007-03-02 13:48:38,949 WARN [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
                                  2007-03-02 13:48:38,949 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=3700](1172839712948)
                                  2007-03-02 13:48:38,949 INFO [Thread-10:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
                                  2007-03-02 13:48:38,949 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172839712948): Socket[addr=localhost/127.0.0.1,port=1101,localport=3700]
                                  2007-03-02 13:48:38,949 ERROR [SocketServerInvoker#0-1101] 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(Unknown Source)
                                   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                                   at java.lang.reflect.Constructor.newInstance(Unknown Source)
                                   at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:198)
                                   at org.jboss.remoting.transport.socket.ServerThread.<init>(ServerThread.java:95)
                                   at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:492)
                                   at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:444)
                                   at java.lang.Thread.run(Unknown Source)
                                  Caused by: java.io.StreamCorruptedException: invalid stream header
                                   at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
                                   at java.io.ObjectInputStream.<init>(Unknown Source)
                                   at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
                                   at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
                                   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.<init>(ClientSocketWrapper.java:54)
                                   at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
                                   ... 9 more
                                  2007-03-02 13:48:38,949 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                                  2007-03-02 13:48:39,949 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
                                  2007-03-02 13:48:39,949 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: entering unRegisterSocket()
                                  2007-03-02 13:48:39,949 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]starting ShutdownRequestThread: Thread[Thread-12:shutdownRequest:-14156,5,main]
                                  2007-03-02 13:48:40,949 INFO [Thread-12:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:48:40,949 INFO [Thread-12:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:48:40,965 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: scheduling ShutdownMonitorTask: shutdownRequest:-14156
                                  2007-03-02 13:48:40,965 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: leaving unRegisterSocket()
                                  2007-03-02 13:48:40,965 WARN [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
                                  2007-03-02 13:48:41,965 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: starting ShutdownRequestThread: Thread[Thread-13:shutdownRequest:-14156,5,main]
                                  2007-03-02 13:48:41,965 INFO [Thread-13:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:48:41,965 INFO [Thread-13:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:48:42,965 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: starting ShutdownRequestThread: Thread[Thread-14:shutdownRequest:-14156,5,main]
                                  2007-03-02 13:48:42,965 ERROR [Thread-14:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]
                                  2007-03-02 13:48:42,965 INFO [Thread-14:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:48:42,965 INFO [Thread-14:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:48:43,965 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: starting ShutdownRequestThread: Thread[Thread-15:shutdownRequest:-14156,5,main]
                                  2007-03-02 13:48:43,965 ERROR [Thread-15:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]
                                  2007-03-02 13:48:43,965 INFO [Thread-15:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:48:43,965 INFO [Thread-15:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:48:44,965 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: starting ShutdownRequestThread: Thread[Thread-16:shutdownRequest:-14156,5,main]
                                  2007-03-02 13:48:44,965 ERROR [Thread-16:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]
                                  2007-03-02 13:48:44,965 INFO [Thread-16:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:48:44,965 INFO [Thread-16:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:48:45,965 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: starting ShutdownRequestThread: Thread[Thread-17:shutdownRequest:-14156,5,main]
                                  2007-03-02 13:48:45,965 ERROR [Thread-17:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]
                                  2007-03-02 13:48:45,965 INFO [Thread-17:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:48:45,965 INFO [Thread-17:shutdownRequest:-14156] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:48:46,965 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]: ShutdownMonitorTimerTask: shutdown refusal count exceeded maximut: 5
                                  2007-03-02 13:48:46,965 INFO [Thread-18:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=3703](1172839718949)
                                  2007-03-02 13:48:46,965 INFO [Thread-18:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172839718949): Socket[addr=localhost/127.0.0.1,port=1101,localport=3703]
                                  2007-03-02 13:48:52,997 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: entering shutdownThreads
                                  2007-03-02 13:48:52,997 INFO [input:-14156] org.jboss.remoting.transport.multiplex.InputMultiplexor: Selector is closed: shutting down input thread
                                  2007-03-02 13:48:52,997 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: cancelling timer
                                  2007-03-02 13:48:52,997 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: static threads shut down
                                  


                                  ******* start client test ******
                                  ******* client test runs successfully *******

                                  ****** restart server with same protocol socket *******

                                  reqistering with JNDI server
                                  2007-03-02 13:50:32,834 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                                  2007-03-02 13:50:32,834 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                                  susseccfully reqistered with JNDI Server
                                  


                                  **** start client test *******
                                  ****** client test succeeds ******

                                  ****** restart server with new protocol multiplex *******

                                  reqistering with JNDI server
                                  2007-03-02 13:52:30,438 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                                  2007-03-02 13:52:30,438 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                                  susseccfully reqistered with JNDI Server
                                  2007-03-02 13:52:35,501 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                                  2007-03-02 13:52:36,486 WARN [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [socket://localhost:1101/]
                                  2007-03-02 13:52:36,501 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                                  


                                  ***** start client test ********
                                  ****** client test fails *****

                                  ****** server dump after client start ******

                                  reqistering with JNDI server
                                  2007-03-02 13:52:30,438 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
                                  2007-03-02 13:52:30,438 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
                                  susseccfully reqistered with JNDI Server
                                  2007-03-02 13:52:35,501 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                                  2007-03-02 13:52:36,486 WARN [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [socket://localhost:1101/]
                                  2007-03-02 13:52:36,501 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                                  2007-03-02 13:53:08,504 INFO [Remoting Detector - Heartbeat Thread: 38] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                                  2007-03-02 13:53:14,504 INFO [Remoting Detector - Heartbeat Thread: 44] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
                                  2007-03-02 13:53:30,427 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.Protocol: Protocol.acceptConnect(): end of file
                                  2007-03-02 13:53:30,427 ERROR [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MasterServerSocket: i/o exception in MasterServerSocket.accept()
                                  2007-03-02 13:53:30,427 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]starting ShutdownRequestThread: Thread[Thread-10:shutdownRequest:31774,5,main]
                                  2007-03-02 13:53:30,427 INFO [Thread-10:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:53:30,442 INFO [Thread-10:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:53:30,442 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]: scheduling ShutdownMonitorTask: shutdownRequest:31774
                                  2007-03-02 13:53:30,442 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: end of file exception: stopping thread
                                  2007-03-02 13:53:31,442 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]: starting ShutdownRequestThread: Thread[Thread-11:shutdownRequest:31774,5,main]
                                  2007-03-02 13:53:31,442 INFO [Thread-11:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:53:31,442 INFO [Thread-11:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:53:32,442 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]: starting ShutdownRequestThread: Thread[Thread-12:shutdownRequest:31774,5,main]
                                  2007-03-02 13:53:32,442 ERROR [Thread-12:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=/127.0.0.1,port=3724,localport=1101]
                                  2007-03-02 13:53:32,442 INFO [Thread-12:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:53:32,442 INFO [Thread-12:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:53:33,442 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]: starting ShutdownRequestThread: Thread[Thread-13:shutdownRequest:31774,5,main]
                                  2007-03-02 13:53:33,442 ERROR [Thread-13:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=/127.0.0.1,port=3724,localport=1101]
                                  2007-03-02 13:53:33,442 INFO [Thread-13:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:53:33,442 INFO [Thread-13:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:53:34,442 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]: starting ShutdownRequestThread: Thread[Thread-14:shutdownRequest:31774,5,main]
                                  2007-03-02 13:53:34,442 ERROR [Thread-14:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=/127.0.0.1,port=3724,localport=1101]
                                  2007-03-02 13:53:34,442 INFO [Thread-14:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:53:34,442 INFO [Thread-14:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:53:35,442 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]: starting ShutdownRequestThread: Thread[Thread-15:shutdownRequest:31774,5,main]
                                  2007-03-02 13:53:35,442 ERROR [Thread-15:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.OutputMultiplexor: unregistered client: Socket[addr=/127.0.0.1,port=3724,localport=1101]
                                  2007-03-02 13:53:35,442 INFO [Thread-15:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: false
                                  2007-03-02 13:53:35,442 INFO [Thread-15:shutdownRequest:31774] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: false
                                  2007-03-02 13:53:36,442 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=3724,localport=1101]: ShutdownMonitorTimerTask: shutdown refusal count exceeded maximut: 5
                                  2007-03-02 13:53:36,442 INFO [Thread-16:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=/127.0.0.1,port=3724,localport=1101](1172839955486)
                                  2007-03-02 13:53:36,442 INFO [Thread-16:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172839955486): Socket[addr=/127.0.0.1,port=3724,localport=1101]
                                  2007-03-02 13:53:45,537 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: entering shutdownThreads
                                  2007-03-02 13:53:45,537 INFO [input:31774] org.jboss.remoting.transport.multiplex.InputMultiplexor: Selector is closed: shutting down input thread
                                  2007-03-02 13:53:45,537 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: cancelling timer
                                  2007-03-02 13:53:45,537 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: static threads shut down
                                  


                                  ******* client dump ******

                                  connecting to JNDI Server
                                  2007-03-02 13:53:01,285 INFO [main] jndiClient.JNDIConnector: setting up connection to JNDI Server
                                  2007-03-02 13:53:01,332 INFO [main] jndiClient.JNDIConnector: register NetworkRegistry with MBean Server
                                  2007-03-02 13:53:01,660 INFO [main] jndiClient.JNDIConnector: getting available Servers from JNDI
                                  2007-03-02 13:53:01,879 INFO [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
                                  2007-03-02 13:53:02,863 INFO [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
                                  2007-03-02 13:53:02,863 INFO [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3734]: entering unRegisterSocket()
                                  2007-03-02 13:53:02,863 INFO [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3734]starting ShutdownRequestThread: Thread[Thread-10:shutdownRequest:-7401,5,main]
                                  2007-03-02 13:53:07,879 INFO [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3734]: leaving unRegisterSocket()
                                  2007-03-02 13:53:07,879 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=3734](1172839981863)
                                  2007-03-02 13:53:07,879 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172839981863): Socket[addr=localhost/127.0.0.1,port=1101,localport=3734]
                                  2007-03-02 13:53:07,879 INFO [Thread-10:shutdownRequest:-7401] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
                                  2007-03-02 13:53:07,879 WARN [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
                                  2007-03-02 13:53:08,879 INFO [main] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
                                  2007-03-02 13:53:08,879 INFO [main] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3737]: entering unRegisterSocket()
                                  2007-03-02 13:53:08,879 INFO [main] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3737]starting ShutdownRequestThread: Thread[Thread-13:shutdownRequest:-7401,5,main]
                                  2007-03-02 13:53:13,879 INFO [main] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=3737]: leaving unRegisterSocket()
                                  2007-03-02 13:53:13,879 WARN [main] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
                                  2007-03-02 13:53:13,879 INFO [Thread-13:shutdownRequest:-7401] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
                                  2007-03-02 13:53:13,879 INFO [Thread-14:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=3737](1172839987879)
                                  2007-03-02 13:53:13,879 INFO [Thread-14:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172839987879): Socket[addr=localhost/127.0.0.1,port=1101,localport=3737]
                                  




                                  • 14. Re: Connection between servers through JNDI?
                                    Ron Sigal Master

                                    I have a question. When your client (lower case) is notified that a new server has come online, are you creating a new org.jboss.remoting.Client with the new server's InvokerLocator? If not, a Client (upper case) would get confused switching between the two different protocols.

                                    If your answer is "Well, duh, of course I am", then I apologize for the question. :-)

                                    1 2 Previous Next