mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark <elihusma...@gmail.com>
Subject Re: Build without backport for java5, freeze on DatagramConfigTest
Date Mon, 02 Oct 2006 18:50:27 GMT
I build MINA using Java5, but use the backport libs.  Not sure if this
is correct, but it works.


On 10/2/06, Raman Gupta <rocketraman@fastmail.fm> wrote:
> I am building Mina for java5 -- I have removed all references to the
> concurrent backport package and have tried to rebuild.  I ran "mvn
> install". The build proceeds normally, but when:
>
> Running org.apache.mina.transport.socket.nio.DatagramConfigTest
>
> runs, the test never completes.
>
> A stack trace shows this:
>
> "main" prio=1 tid=0x082dedd0 nid=0x620d in Object.wait()
> [0xbfde4000..0xbfde6188]
>         at java.lang.Object.wait(Native Method)
>         - waiting on <0x88a07930> (a
> org.apache.mina.transport.socket.nio.support.DatagramConnectorDelegate$RegistrationRequest)
>         at java.lang.Object.wait(Object.java:474)
>         at
> org.apache.mina.common.support.DefaultIoFuture.join(DefaultIoFuture.java:86)
>         - locked <0x88a07930> (a
> org.apache.mina.transport.socket.nio.support.DatagramConnectorDelegate$RegistrationRequest)
>         at
> org.apache.mina.transport.socket.nio.DatagramConfigTest.testAcceptorFilterChain(DatagramConfigTest.java:73)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at junit.framework.TestCase.runTest(TestCase.java:154)
>         at junit.framework.TestCase.runBare(TestCase.java:127)
>         at junit.framework.TestResult$1.protect(TestResult.java:106)
>         at junit.framework.TestResult.runProtected(TestResult.java:124)
>         at junit.framework.TestResult.run(TestResult.java:109)
>         at junit.framework.TestCase.run(TestCase.java:118)
>         at junit.framework.TestSuite.runTest(TestSuite.java:208)
>         at junit.framework.TestSuite.run(TestSuite.java:203)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at
> org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
>         at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
>         at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
>         at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
>         at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
>
> It seems that the DefaultIoFuture is never being notified. Is this a
> problem with my environment or with some difference between the backport
> package and the standard java 5 packages?
>
> Has anyone else created a build for java5, and run into the same problem?
>
> Cheers,
> Raman
>
>

Mime
View raw message