3 Replies Latest reply on Jun 10, 2008 8:36 AM by masterozz666

Repeatedly Connecting to port 3873 in swing client

masterozz666 May 14, 2008 5:45 AM

Hi,
i modifid my log4j settings for test reasons using debug at the root logger on client side. After starting my client swing application, which performs a lookup for a service (session bean in JBoss), i registered following: There are made connections/disconnections repeatedly.
The log output of my swing application looks like this (repeatedly infinte without doing any actions in my application):

<snippet>
[DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
[DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[883c86, socket://192.168.2.40:3873] from registry
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[883c86, socket://192.168.2.40:3873] disconnecting ...
[DEBUG] [14.05.2008 11:08:44] [SocketWrapper] : ClientSocketWrapper[Socket[addr=/192.168.2.40,port=3873,localport=1371].6822b0] closing
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] constructed
[DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] connecting
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] added new pool ([]) as ServerAddress[192.168.2.40:3873, NO enableTcpNoDelay timeout 0 ms]
[DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] connected
[DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
[DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] from registry
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[bd7d21, socket://192.168.2.40:3873] disconnecting ...
[DEBUG] [14.05.2008 11:08:44] [SocketWrapper] : ClientSocketWrapper[Socket[addr=/192.168.2.40,port=3873,localport=1372].10a7910] closing
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] constructed
[DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] connecting
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] added new pool ([]) as ServerAddress[192.168.2.40:3873, NO enableTcpNoDelay timeout 0 ms]
[DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] connected
[DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
[DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[923822, socket://192.168.2.40:3873] from registry
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[923822, socket://192.168.2.40:3873] disconnecting ...
[DEBUG] [14.05.2008 11:08:44] [SocketWrapper] : ClientSocketWrapper[Socket[addr=/192.168.2.40,port=3873,localport=1373].1f374e5] closing
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] constructed
[DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] connecting
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] added new pool ([]) as ServerAddress[192.168.2.40:3873, NO enableTcpNoDelay timeout 0 ms]
[DEBUG] [14.05.2008 11:08:44] [MicroRemoteClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] connected
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] got Exception java.net.BindException: Address already in use: connect, creation attempt took 15 ms
[DEBUG] [14.05.2008 11:08:44] [MicroSocketClientInvoker] : SocketClientInvoker[7f906b, socket://192.168.2.40:3873] got Exception java.net.BindException: Address already in use: connect, creation attempt took 0 ms
[DEBUG] [14.05.2008 11:08:44] [ClientSocketWrapper] : reset timeout: 0
[DEBUG] [14.05.2008 11:08:44] [InvokerRegistry] : removed SocketClientInvoker[7f906b, socket://192.168.2.40:3873] from registry
</snippet>

Is this normal. Why does the client connect to port 3873?

Thanks in advance, Markus

1. Re: Repeatedly Connecting to port 3873 in swing client

kahzoo May 14, 2008 11:08 PM (in response to masterozz666)

AFAIK, a jboss client connects to (jboss server's) port 3873 when it does EJB3 remote method invocation under JBoss 4.2.x default configuration.

Are you sure your client is not calling your session bean at all?
Actions
2. Re: Repeatedly Connecting to port 3873 in swing client

masterozz666 May 15, 2008 9:16 AM (in response to masterozz666)

Thanks for your quick answer.

I thought method invocation is done using the RMI port, or am i wrong?

It sounds like this shouldn't happen. And i'm almost sure that the client doesn't call my remote session bean all the time.

Is there any way to determine which session bean and which method is called?

Thanks in advance, Markus
Actions
3. Re: Repeatedly Connecting to port 3873 in swing client

masterozz666 Jun 10, 2008 8:36 AM (in response to masterozz666)

I resolved this problem. We had a helper class, writing the client logs to a remote server. So, for every log output, we open a connection. And for every opened connection, Jboss performs some log output, and this happens infinitely ;)
Never tested this class with level DEBUG, so this never occured.
Actions

Go to original post