[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1287) SOA-P test suite failures

Wed Jul 15 02:04:29 EDT 2009

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

Aleksandar Kostadinov commented on JBMESSAGING-1287:
----------------------------------------------------

Hallo, as I said in my previous comment the problem is that you have a file called VERSION and you use it to get your version string. So if any other library has such file, it can be read instead of yours and probably cause problems.

I'm not sure about what should be done. Two suggestions below:
1. Rename that file to JBM_VERSION or some other name that is less likely being used by some other project.
2. Verify that the deployment in SOA-P is such that this can never cause a problem. Given that JBM seems to be working in the other testing this is likely to be true. But I'm not sure if in any customer deployment scenarios this can't get them in trouble.

Hope this makes sense.

> SOA-P test suite failures
> -------------------------
>
>                 Key: JBMESSAGING-1287
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1287
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.SP3_CP01
>            Reporter: Aleksandar Kostadinov
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
>
>
> I'm running the JBM test suite against the binaries in the SOA-P Platform 4.2 CP01. I see 4 failures. 
>     * TEST-org.jboss.test.messaging.jms.bridge.BridgeTest-Remote-bisocket.xml.
>     * org.jboss.test.messaging.jms.clustering.MultipleFailoverTest(Clustering).testFailoverFloodTwoServers
>     * org.jboss.test.messaging.jms.clustering.NoFailoverTest(Clustering).testCrashNoFailover
>     * org.jboss.test.messaging.jms.ManifestTest.testManifestEntries
> Failure details in here http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-JBM-testsuite/73/testReport/
> 3 of the failures are timeout (see console log for BridgeTest). We are running on a 2 CPU DualCore physical machine so system speed should not be an issue. 

-- 
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