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

Sun Jan 4 10:17:54 EST 2009

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

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

I found the problem. Version is taken from a file called "VERSION" in the classpath. So it turned out that jbossesb jars contain a file called the same but holds ESB rather than JBM version.
Isn't it better to have the file called JBM_VERSION or whatever more specific file name you like?

> 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: Tim Fox
>
> 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