| Summary: | Problem to reconnect windows client to a linux server | ||
|---|---|---|---|
| Product: | JacORB | Reporter: | 78mtorres |
| Component: | ORB | Assignee: | Mailinglist to track bugs <jacorb-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | CC: | jacorb, jm.ais40 |
| Priority: | P5 | ||
| Version: | 3.2 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Attachments: | The jacorb log produces on the server side | ||
Without knowing what your interceptors / client / server interactions are its difficult to advise. Have you tried obtaining a wireshark trace? It looks like you might have a timeout set? Have you tried experimenting with a less complex setup to replicate the issue in a standalone testcase? If you could provide more details/test case etc it might help to diagnose the issue. For instance, why are you setting jacorb.ior_proxy* properties? I am closing this for now; please reopen if you have further details. |
Created attachment 417 [details] The jacorb log produces on the server side We connect a windows client to a linux server. When the client is connected, we kill it with a CTRL+C or we kill the DOS console. The exception COM_FAILURE is thrown. After 15s, we launch the client again. At this step impossible to connect the client to the server. The server tries to bind the client the "jacorb.retries" times and doesn't arrive. Server side, the exception "java.net.ConnectException: Connexion terminée par expiration du délai d'attente" is thrown. Client side the exception "org.omg.CORBA.TIMEOUT: client timeout reached vmcid: 0x0 minor code: 0 completed: No" is thrown. If we install and test the client on linux, we haven't this problem. Our environment is jacorb 3.2, windows 7 or XP, jdk 7. We use the naming service and the interceptors. The firewalls on the windows workstation and on the linux server are disabled The jacorb properties setted are: jacorb.implname, jacorb.ior_proxy_host, jacorb.ior_proxy_port, jacorb.dns.enable.