JMS Integration Tests 'hang' periodically when run from maven [BATCH-30]

[spring-projects]

JMS Integration Tests 'hang' periodically when run from maven [BATCH-30]

[spring-projects-issues]

Dave Syer commented

I don't have this problem, but it's almost certainly caused by having to wait for Derby to shut down. I'm not sure why it's so slow. I was going to try an in-memory extension to Derby https://issues.apache.org/jira/browse/DERBY-646 (which looks like it might be in a future release, but isn't there yet).

More information about what is happening - like a thread dump maybe - might help. There is no sign of anything hanging for more than about 1/2 second in the log output above.

[spring-projects-issues]

Dave Syer commented

Tried to use HSQLDB instead of Derby for AMQ and couldn't quite get it to work. The BrokerService introduced in data-source.xml is set up so that AMQ uses the same derby instance as the other DB access, so it might not hang so badly (maybe?). But ideally we could use the HSQLDB (or MemoryPersistrenceAdapter which also seems to have no effect).

[spring-projects-issues]

Dave Syer commented

Since we moved to the in-memory persistence strategy nothing has failed or hung, so I'm going to resolve this one. The integration build on bamboo should alert us if there are any more problems.

[spring-projects-issues]

Dave Syer commented

Assume closed as resolved and released