|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I believe we have encountered this problem after a 4.1.9 upgrade and have had to fall back to 4.1.8. In our case it consistently fails on our proper dev/qa environments on Red Hat 4.5, Java 1.6.0_u37 64-bit; built by our RHEL 5 build server with Java 1.6.0_u33, but none of us can get it to fail in a local development environment (Windows, either XP or 7) with a handful of various JDK 6 point releases used for both compilation and runtime. Is there anything known about the nature of the problem that could explain this apparent platform/env difference or similar behaviour experienced by others?