[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - All sorts of failures with JDK 1.6

[clebert.suconic@jboss.com]

If you use JDK 1.6 on the testsuite, you will get all sort of failures... with *lots* of failures.


A good example would be:

org.jboss.messaging.tests.integration.cluster.distribution.NettyFileStorageSymmetricClusterTest::testRoundRobinMultipleQueues



  | MessagingException[errorCode=2 message=Unable to connect to server using configuration org-jboss-messaging-integration-transports-netty-NettyConnectorFactory?jbm-remoting-netty-port=5447&jbm-remoting-invm-serverid=2]
  | 	at org.jboss.messaging.core.client.impl.ConnectionManagerImpl.createSession(ConnectionManagerImpl.java:278)
  | 	at org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:915)
  | 	at org.jboss.messaging.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:715)
  | 	at org.jboss.messaging.tests.integration.cluster.distribution.ClusterTestBase.addConsumer(ClusterTestBase.java:287)
  | 	at org.jboss.messaging.tests.integration.cluster.distribution.SymmetricClusterTest.testRoundRobinMultipleQueues(SymmetricClusterTest.java:238)
  | 	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:597)
  | 	at junit.framework.TestCase.runTest(TestCase.java:164)
  | 	at junit.framework.TestCase.runBare(TestCase.java:130)
  | 	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:120)
  | 	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
  | 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
  | 17:12:50,391 WARN  @New I/O server boss #5 (channelId: 660493198, /127.0.0.1:5449) [NioServerSocketPipelineSink] Failed to initialize an accepted socket.
  | org.jboss.netty.channel.ChannelException: Failed to create a selector.
  | 	at org.jboss.netty.channel.socket.nio.NioWorker.register(NioWorker.java:102)
  | 	at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.run(NioServerSocketPipelineSink.java:210)
  | 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  | 	at java.lang.Thread.run(Thread.java:619)
  | Caused by: java.io.IOException: Too many open files
  | 	at sun.nio.ch.EPollArrayWrapper.epollCreate(Native Method)
  | 	at sun.nio.ch.EPollArrayWrapper.<init>(EPollArrayWrapper.java:68)
  | 	at sun.nio.ch.EPollSelectorImpl.<init>(EPollSelectorImpl.java:52)
  | 	at sun.nio.ch.EPollSelectorProvider.openSelector(EPollSelectorProvider.java:18)
  | 	at java.nio.channels.Selector.open(Selector.java:209)
  | 	at org.jboss.netty.channel.socket.nio.NioWorker.register(NioWorker.java:100)
  | 	... 4 more
  | 
  | 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228784#4228784

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228784