You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Raman Gupta <ro...@fastmail.fm> on 2006/10/02 20:44:13 UTC
Build without backport for java5, freeze on DatagramConfigTest
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
Re: Build without backport for java5, freeze on DatagramConfigTest
Posted by Emmanuel Lecharny <el...@gmail.com>.
It would be cool to give some information avout the used JVM, the system
you are running the test on, the number of procs, etc...
( We experienced some strange problem lately with JRockit JVM on linux )
Thanks !
Emmanuel
Frédéric Brégier a écrit :
>I have made some tests with removing the backport
>dependencies with no problem using native java5.
>However I did not get deep in the tests so far, so I cannot
>say that there is no problem.
>For instance, I didn't run the program test you run.
>
>I agree with you the native java5 should be better
>(at least in theory). I need to advance a bit in my
>port to Mina 1.0 to say if there are other problems
>like the one you get.
>
>Also I plan to look inside Mina code and see where we can
>put "java5" functions, using both backport and native,
>and propose this to Mina. But it will take some time...
>and of course, as others, I have a job to do every day. ;-)
>
>Frederic
>
>Mark wrote:
>
>
>>On 10/2/06, Raman Gupta <ro...@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:
>>>
>>>
>>I build MINA using Java5, but use the backport libs. Not sure if this
>>is correct, but it works.
>>
>>
>>
>
>Yeah, I know that works but I'm trying to avoid including a dependency
>that I don't need. Also, the native java5 concurrent utilities are, in
>many cases, faster than the backport versions (though I doubt the
>difference is significant).
>
>Cheers,
>Raman
>
>
>
>
>
Re: Build without backport for java5, freeze on DatagramConfigTest
Posted by Emmanuel Lecharny <el...@gmail.com>.
Ok, it seems you found something.
Can one of you fill a JIRA with all the information ? (which version of
MINA are you using, JVM, system, etc ...)
Thanks a lot !
Frédéric Brégier a écrit :
>I tried both with and without backport
>on a Windows XP with java JDK 1.5.0.6.
>Bacport is ok.
>Without backport, mvn package is blocking in TESTS phase at :
>"Running org.apache.mina.transport.socket.nio.DatagramConfigTest".
>So I supposed (even if I don't get the message through mvn interface)
>that I got the same problem as you.
>
>So I confirm the problem for me too, at list for Datagram...
>
>Frederic
>
>----- Original Message -----
>
>Frédéric Brégier wrote:
>
>
>>I have made some tests with removing the backport
>>dependencies with no problem using native java5.
>>However I did not get deep in the tests so far, so I cannot
>>say that there is no problem.
>>For instance, I didn't run the program test you run.
>>
>>
>>
>
>If you get a chance, on your mina version without backport, run:
>
>mvn test
>
>I want to see if you have the same problem as I do. I tried it on
>Windows 2000
> Java 1.5.0_08 and Linux Java 1.5.0_07 and had the same problem on both.
>
>
>Cheers,
>Raman
>
>
>
>
>
Re: Build without backport for java5, freeze on DatagramConfigTest
Posted by Frédéric Brégier <fr...@free.fr>.
I tried both with and without backport
on a Windows XP with java JDK 1.5.0.6.
Bacport is ok.
Without backport, mvn package is blocking in TESTS phase at :
"Running org.apache.mina.transport.socket.nio.DatagramConfigTest".
So I supposed (even if I don't get the message through mvn interface)
that I got the same problem as you.
So I confirm the problem for me too, at list for Datagram...
Frederic
----- Original Message -----
Frédéric Brégier wrote:
> I have made some tests with removing the backport
> dependencies with no problem using native java5.
> However I did not get deep in the tests so far, so I cannot
> say that there is no problem.
> For instance, I didn't run the program test you run.
>
If you get a chance, on your mina version without backport, run:
mvn test
I want to see if you have the same problem as I do. I tried it on
Windows 2000
Java 1.5.0_08 and Linux Java 1.5.0_07 and had the same problem on both.
Cheers,
Raman
Re: Build without backport for java5, freeze on DatagramConfigTest
Posted by Raman Gupta <ro...@fastmail.fm>.
Frédéric Brégier wrote:
> I have made some tests with removing the backport
> dependencies with no problem using native java5.
> However I did not get deep in the tests so far, so I cannot
> say that there is no problem.
> For instance, I didn't run the program test you run.
>
If you get a chance, on your mina version without backport, run:
mvn test
I want to see if you have the same problem as I do. I tried it on
Windows 2000
Java 1.5.0_08 and Linux Java 1.5.0_07 and had the same problem on both.
Cheers,
Raman
Re: Build without backport for java5, freeze on DatagramConfigTest
Posted by Frédéric Brégier <fr...@free.fr>.
I have made some tests with removing the backport
dependencies with no problem using native java5.
However I did not get deep in the tests so far, so I cannot
say that there is no problem.
For instance, I didn't run the program test you run.
I agree with you the native java5 should be better
(at least in theory). I need to advance a bit in my
port to Mina 1.0 to say if there are other problems
like the one you get.
Also I plan to look inside Mina code and see where we can
put "java5" functions, using both backport and native,
and propose this to Mina. But it will take some time...
and of course, as others, I have a job to do every day. ;-)
Frederic
Mark wrote:
> On 10/2/06, Raman Gupta <ro...@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:
>
> I build MINA using Java5, but use the backport libs. Not sure if this
> is correct, but it works.
>
Yeah, I know that works but I'm trying to avoid including a dependency
that I don't need. Also, the native java5 concurrent utilities are, in
many cases, faster than the backport versions (though I doubt the
difference is significant).
Cheers,
Raman
Re: Build without backport for java5, freeze on DatagramConfigTest
Posted by Raman Gupta <ro...@fastmail.fm>.
Mark wrote:
> On 10/2/06, Raman Gupta <ro...@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:
>
> I build MINA using Java5, but use the backport libs. Not sure if this
> is correct, but it works.
>
Yeah, I know that works but I'm trying to avoid including a dependency
that I don't need. Also, the native java5 concurrent utilities are, in
many cases, faster than the backport versions (though I doubt the
difference is significant).
Cheers,
Raman
Re: Build without backport for java5, freeze on DatagramConfigTest
Posted by Mark <el...@gmail.com>.
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 <ro...@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
>
>