[
http://issues.apache.org/jira/browse/DIRMINA-278?page=comments#action_12440598
]
John Conlon commented on DIRMINA-278:
-------------------------------------
After changing all mina class imports from edu.emory.mathcs.backport.* to
java.util.concurrent.*,
building with Java version "1.5.0_06" causes the following test classes to hang
org.apache.mina.transport.socket.nio.DatagramConfigTest
org.apache.mina.transport.socket.nio.DatagramRecyclerTest
org.apache.mina.transport.socket.nio.DatagramTrafficControlTest
It appears that these tests all hang when attempting to connect to the server
port at the future.join():
In other words the client never connects to the test server port.
Athough changing the open ended blocking call of future.join() to
to a time constrained connection like:
boolean connected = future.join(5000);
assertTrue("Did not connect after 5 seconds",connected);
can prevent the test from hanging, the connect still timeouts and the test will
fail.
This still leaves the open question:
What is causing the connection failures?
> Provide Java 5 Build
> --------------------
>
> Key: DIRMINA-278
> URL: http://issues.apache.org/jira/browse/DIRMINA-278
> Project: Directory MINA
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0
> Reporter: Graham Miller
>
> Version 1.0 introduced a dependency on backport-util-concurrent. For those
> of us deploying to a Java 5 platform it is unnecessary to use that library.
> Could you please provide some way to build the library with the standard
> Java 5 libraries? Given that backport-util-concurrent is intended to be a
> drop-in replacement for the Java 5 libraries:
> "The purpose of this library is to enable gradual migration from Java 1.4 to
> 5.0: the library allows to develop concurrent applications for Java 1.4 that
> should work with Java 5.0 simply by changing package names." (from
> http://dcl.mathcs.emory.edu/util/backport-util-concurrent/), perhaps this
> shouldn't be too hard?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
