Hallo,
we've got a pretty strange behaviour with the communication from client to server.
When starting the client, a new communication channel is opened to the server. Here is te logging from the JacORB component:
12.06.13 07:05:21,484 [] [Thread-34] INFO  jacorb.orb.giop -
ClientConnectionManager: found ClientGIOPConnection to 10.173.204.22:0
(8eeaee)
12.06.13 07:05:21,484 [] [Thread-33] INFO  jacorb.orb.delegate - Adding new retry group for 10.173.204.22:0
12.06.13 07:05:21,484 [] [Thread-34] INFO  jacorb.orb.delegate - Adding new retry group for 10.173.204.22:0
12.06.13 07:05:23,875 [] [SwingWorker-pool-1-thread-3] INFO  jacorb.orb.giop
- ClientConnectionManager: found ClientGIOPConnection to 10.173.204.22:0
(8eeaee)
12.06.13 07:05:23,875 [] [SwingWorker-pool-1-thread-3] INFO jacorb.orb.delegate - Adding new retry group for 10.173.204.22:0
12.06.13 07:05:31,312 [] [SSLServerSocketListener] INFO  jacorb.orb.iiop - Opened new server-side TCP/IP transport to 10.173.204.22:53502

As you can see, a new connection is opened to 10.173.204.22, which is the IP adress of the application server. This behaviour is completly ok.

Now the part, what I don't understand:
12.06.13 12:35:44,953 [] [SwingWorker-pool-1-thread-5] INFO  jacorb.poa -
oid: 01 0A 1F 11 21 07 48 48 10 06 30 46 38 14 14 1B 48 4C 1B   
....!.HH..0F8...HL.object is activated
12.06.13 12:35:45,015 [] [SwingWorker-pool-1-thread-5] INFO  jacorb.orb.giop
- ClientConnectionManager: created new ClientGIOPConnection to 127.0.0.5:0
(8ebb95)
12.06.13 12:35:45,015 [] [SwingWorker-pool-1-thread-5] INFO jacorb.orb.delegate - Adding new retry group for 127.0.0.5:0
12.06.13 12:35:46,062 [] [SwingWorker-pool-1-thread-5] INFO  jacorb.orb.iiop
- Retrying to connect to 127.0.0.5:7621

As you can see at the logging, a new ClientGIOPConnection is opened to 127.0.0.5, meaning the localhost. But why does that happen? With this configuration, the communication to the server is finished. Why doesn't it take again the IP-Adress of the server?
Is that a bug in JaCORB?

If you need further information, please tell.  Unfortunately, the bug is not reproduceable.