<html>
<head>
<base href="http://www.jacorb.org/bugzilla/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - JacORB hangs in endless connection retry loop"
href="http://www.jacorb.org/bugzilla/show_bug.cgi?id=1018">1018</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>JacORB hangs in endless connection retry loop
</td>
</tr>
<tr>
<th>Product</th>
<td>JacORB
</td>
</tr>
<tr>
<th>Version</th>
<td>3.6.1
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>critical
</td>
</tr>
<tr>
<th>Priority</th>
<td>P5
</td>
</tr>
<tr>
<th>Component</th>
<td>ORB
</td>
</tr>
<tr>
<th>Assignee</th>
<td>jacorb-bugs@lists.spline.inf.fu-berlin.de
</td>
</tr>
<tr>
<th>Reporter</th>
<td>fvbetteraey@web.de
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=469" name="attach_469" title="jacorb debug logfile">attachment 469</a> <a href="attachment.cgi?id=469&action=edit" title="jacorb debug logfile">[details]</a></span>
jacorb debug logfile
We try to connect to a not responding corba service using JacORB 3.6.1. We set
the properties jacorb.retries and
jacorb.connection.client.pending_reply_timeout and hoped to get a failure after
the number of specified retries.
Instead it seems that JacORB is ending in an endless loop, trying to connect to
the service
(1) connect to nameservice (success)
(2) connect to corba service (timeout failure); retry
(3) goto (1) - we did not expect this
We use JacORB together with Apache CXF to establish the connection. The address
we use there (in the JaxWsProxyFactoryBean) is something like
"corbaname::<NameService>:<NameServicePort>#<ServiceName>". Meanwhile we used
the "Ultra Corba Simulator" to connect to the service and the behaviour is as
expected (exception after unsuccessful retries).
When we use the SUN ORB we get an Exception as expected (even when using Apache
CXF)
Jun 25, 2015 9:07:12 PM
com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl <init>
WARNUNG: "IOP00410201: (COMM_FAILURE) Connection failure: socketType:
IIOP_CLEAR_TEXT; hostname: <server>; port: <port>"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at
com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2200)
at
com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2221)
at
com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:223)
Hint: In a private email conversation (after I reported the bug to the mailing
list -
<a href="http://lists.spline.inf.fu-berlin.de/pipermail/jacorb-developer/2015-June/000711.html">http://lists.spline.inf.fu-berlin.de/pipermail/jacorb-developer/2015-June/000711.html</a>)
Nick Cross narrowed the problem to:
<span class="quote">> Thanks for the log. As Phil and I suspected it is entering the
> getParsedIOR().useCorbaName() and looping continuously in there.
>
> Phil is also taking a look at a related case so we will try to come up
> with a solution.</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>