[
https://jira.jboss.org/jira/browse/JBESB-2755?page=com.atlassian.jira.plu...
]
murray armfield commented on JBESB-2755:
----------------------------------------
Hi Folks,
I've been testing JBossESB 4.6 with my above Ingres patch against an Ingres
patched JBoss server 5.1.0GA, and now the only tests that fails qhen running the qa test
suite is the JmsGatewayListenerUnit and the FTP test.
The FTP test fails I suspect because I have not set it up right and I am looking into
it.
The JmsGatewayListenerUnit test fails with..
Test failed to deliver files to build dir:
/opt/jbossesb-4.6-src/qa/build/TargetServiceAction-Service1-Received,
/opt/jbossesb-4.6-src/qa/build/TargetServiceAction-Service2-Received
[junit] junit.framework.AssertionFailedError: Test failed to deliver files to build
dir: /opt/jbossesb-4.6-src/qa/build/TargetServiceAction-Service1-Received,
/opt/jbossesb-4.6-src/qa/build/TargetServiceAction-Service2-Received
[junit] at
org.jboss.soa.esb.jms.JmsGatewayListenerUnitTest.test(JmsGatewayListenerUnitTest.java:57)
[junit] at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
[junit] at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
[junit] at junit.extensions.TestSetup.run(TestSetup.java:27)
So this is a good improvement over the 4.5 test results, with the BPMOrchestration2
and JmsSecured tests now working correctly.
Patch to add Ingres support to JBoss ESB
----------------------------------------
Key: JBESB-2755
URL:
https://jira.jboss.org/jira/browse/JBESB-2755
Project: JBoss ESB
Issue Type: Patch
Security Level: Public(Everyone can see)
Affects Versions: 4.5
Environment: N/A
Reporter: murray armfield
Attachments: jbossesb-4.5.GA-src-ingres.diff, jbossesb-4.6-src-ingres.diff
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
Hi Folks,
I've been working with getting JBoss ESB and its test suite(qa directory of src
tarball download) ported to use the Ingres database system.
Interested users should use the most recent Ingres release.
I am in a position where I am passing all the same tests as the hsqldb. The ones that
fail, fail in the same way as the hsqldb db fails.
The failing tests are
1/ JmsGatewayListenerUnit Test - I get 'the destination does not
exist' errors when it tries to create the topic used in the test.
2/ BPMOrchestration2Test - The last action, shipping, doesn't occur -
state seems to be the same as hslqdb upon inspection through jbpm web console.
3/ JMSecuredTest - No classloaders found for JDBCJMSUserManagerService.
If I need to revisit any of these or run any other test suites, please let me know
and I will get on top of it immediately.
Currently, Ingres 9.2 which is the current Ingres release, does not support object
names greater than 32 characters. This is being addressed in future versions of Ingres. In
the community version of Ingres, you can download and build the source code with an
appropriate flag switched which will turn on much bigger object names. Some of the drools
code in JBossESB uses objects with names greater than this limit, but it has not affected
any of the tests that run. I am looking at doing something with drools to work with Ingres
temporarily
Take care,
Murray
--
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