[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1746) JBM test fails after upgrading to jgroups 2.6 on 64bit Linux

[Howard Gao (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12494769#action_12494769 ] 

Howard Gao commented on JBMESSAGING-1746:
-----------------------------------------

It's a false alarm. 

The failure was caused by default thread limit on the test system. In the test it creates up to 7 processes and each process will produce around 120 live threads. The test system (Fedora 11 64bit) default thread limit is 1024 (ulimit -u), which is two low for the test.

After changing the limit to above 10k, the test passed. 



> JBM test fails after upgrading to jgroups 2.6 on 64bit Linux
> ------------------------------------------------------------
>
>                 Key: JBMESSAGING-1746
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1746
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.6.GA
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>             Fix For: 1.4.6.GA.SP1
>
>
> After upgrading to jgroups 2.6.13, some JBM tests start to fail (LargeClusterTest). This test starts up 7 nodes on one machine before test, but some node will fail to startup as the code have some flaw and only showed up on 64 bit linux. JGroups team is helping on the proper fix.
> Note if we reduce the number of nodes the test passes. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira